[jira] [Commented] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row

[ https://issues.apache.org/jira/browse/PHOENIX-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15994307#comment-15994307 ] Vincent Poon commented on PHOENIX-3824: --- [~lhofhansl] it turned out that the two are related.

[jira] [Updated] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

[ https://issues.apache.org/jira/browse/PHOENIX-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3823: -- Description: When UPDATE_CACHE_FREQUENCY is used, clients will cache metadata for a period

[jira] [Commented] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993469#comment-15993469 ] James Taylor commented on PHOENIX-2885: --- This JIRA can be broken down into the following steps: -

[jira] [Commented] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

[ https://issues.apache.org/jira/browse/PHOENIX-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993548#comment-15993548 ] James Taylor commented on PHOENIX-3823: --- This JIRA can be broken down into the following parts: -

[jira] [Updated] (PHOENIX-3209) Ensure scans run at specific server timestamp for UPSERT SELECT to same table

[ https://issues.apache.org/jira/browse/PHOENIX-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3209: -- Issue Type: Sub-task (was: Bug) Parent: PHOENIX-3819 > Ensure scans run at specific

[jira] [Assigned] (PHOENIX-3209) Ensure scans run at specific server timestamp for UPSERT SELECT to same table

[ https://issues.apache.org/jira/browse/PHOENIX-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-3209: - Assignee: Maddineni Sukumar > Ensure scans run at specific server timestamp for UPSERT

[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Issue Type: Sub-task (was: Bug) Parent: PHOENIX-3819 > Set default value for

[jira] [Updated] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

[ https://issues.apache.org/jira/browse/PHOENIX-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3823: -- Issue Type: Sub-task (was: Bug) Parent: PHOENIX-3819 > Force cache update on

[jira] [Updated] (PHOENIX-3209) Ensure scans run at specific server timestamp for UPSERT SELECT to same table

[ https://issues.apache.org/jira/browse/PHOENIX-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3209: -- Description: This is a corner case of specifying an UPDATE_CACHE_FREQUENCY on a table and

[jira] [Commented] (PHOENIX-3818) Add client setting to disable server side UPSERT SELECT work

[ https://issues.apache.org/jira/browse/PHOENIX-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993318#comment-15993318 ] Andrew Purtell commented on PHOENIX-3818: - I was hoping a configuration toggle would turn this

[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Summary: Set default value for UPDATE_CACHE_FREQUENCY (was: Set default value for

[jira] [Commented] (PHOENIX-3818) Add client setting to disable server side UPSERT SELECT work

[ https://issues.apache.org/jira/browse/PHOENIX-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993355#comment-15993355 ] James Taylor commented on PHOENIX-3818: --- The run on server side code I mentioned above has been in

[jira] [Created] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

James Taylor created PHOENIX-3823: - Summary: Force cache update on MetaDataEntityNotFoundException Key: PHOENIX-3823 URL: https://issues.apache.org/jira/browse/PHOENIX-3823 Project: Phoenix

[jira] [Commented] (PHOENIX-3814) Unable to connect to Phoenix via Spark

[ https://issues.apache.org/jira/browse/PHOENIX-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993446#comment-15993446 ] Josh Mahonin commented on PHOENIX-3814: --- Sorry for the delay, in responding, was out of town and

[jira] [Comment Edited] (PHOENIX-3814) Unable to connect to Phoenix via Spark

[ https://issues.apache.org/jira/browse/PHOENIX-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993446#comment-15993446 ] Josh Mahonin edited comment on PHOENIX-3814 at 5/2/17 6:23 PM: --- Sorry for

[jira] [Assigned] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY and handle not found exceptions

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-2885: - Assignee: Maddineni Sukumar > Set default value for UPDATE_CACHE_FREQUENCY and handle

[jira] [Commented] (PHOENIX-3818) Add client setting to disable server side UPSERT SELECT work

[ https://issues.apache.org/jira/browse/PHOENIX-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993418#comment-15993418 ] Andrew Purtell commented on PHOENIX-3818: - Ok I am not advocating a regression. What I think we

[jira] [Commented] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993417#comment-15993417 ] James Taylor commented on PHOENIX-2885: --- [~sukuna...@gmail.com] - I've created a separate JIRA for

[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Description: We have the ability currently to tell Phoenix how stale we're will to have the

[jira] [Commented] (PHOENIX-3823) Force cache update on MetaDataEntityNotFoundException

[ https://issues.apache.org/jira/browse/PHOENIX-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993556#comment-15993556 ] Maddineni Sukumar commented on PHOENIX-3823: Sure James, I cant expect more detailed info

[jira] [Commented] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY

[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993363#comment-15993363 ] Maddineni Sukumar commented on PHOENIX-2885: I am thinking below are the scenarios we need

[jira] [Commented] (PHOENIX-3818) Add client setting to disable server side UPSERT SELECT work

[ https://issues.apache.org/jira/browse/PHOENIX-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15992451#comment-15992451 ] James Taylor commented on PHOENIX-3818: --- Thanks for the patch, [~alexaraujo]. Please see my

[jira] [Resolved] (PHOENIX-3821) Provide config to disable distributing upsert/select across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3821. --- Resolution: Duplicate Duplicate of PHOENIX-3818 > Provide config to disable distributing

[jira] [Resolved] (PHOENIX-3809) CURRENT_DATE() (with parentheses) is illegal in Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3809. Resolution: Fixed > CURRENT_DATE() (with parentheses) is illegal in Calcite >

[jira] [Commented] (PHOENIX-3809) CURRENT_DATE() (with parentheses) is illegal in Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15992461#comment-15992461 ] Ankit Singhal commented on PHOENIX-3809: Thanks [~julianhyde] and [~jamestaylor]. >

Re: [ANNOUNCE] PhoenixCon 2017 is a go!

Thanks, James! On Mon, May 1, 2017 at 10:32 AM, James Taylor wrote: > Deadline for PhoenixCon abstract/talk proposal is this Friday, May 5th @ > 5pm. > > Thanks, > James > > On Sun, Apr 30, 2017 at 11:19 PM, anil gupta > wrote: > > > HI James, > >

[jira] [Resolved] (PHOENIX-3816) Implement SET_OPTION for consistency in phoenix-calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3816. Resolution: Fixed > Implement SET_OPTION for consistency in phoenix-calcite >

[jira] [Updated] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

[ https://issues.apache.org/jira/browse/PHOENIX-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3822: -- Attachment: PHOENIX-3822_4.x-HBase-0.98.patch WIP patch. Need to add some tests. Parking here

[jira] [Commented] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

[ https://issues.apache.org/jira/browse/PHOENIX-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15992767#comment-15992767 ] Hadoop QA commented on PHOENIX-3822: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

[ https://issues.apache.org/jira/browse/PHOENIX-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3822: -- Attachment: (was: PHOENIX-3822_4.x-HBase-0.98.patch) > Surface byte and row estimates in

[jira] [Updated] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

[ https://issues.apache.org/jira/browse/PHOENIX-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3822: -- Attachment: PHOENIX-3822.patch > Surface byte and row estimates in a machine readable way

[jira] [Updated] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

[ https://issues.apache.org/jira/browse/PHOENIX-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3822: -- Attachment: PHOENIX-3822.patch > Surface byte and row estimates in a machine readable way

[jira] [Commented] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

[ https://issues.apache.org/jira/browse/PHOENIX-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15992847#comment-15992847 ] Hadoop QA commented on PHOENIX-3822: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Created] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

Samarth Jain created PHOENIX-3822: - Summary: Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN Key: PHOENIX-3822 URL: https://issues.apache.org/jira/browse/PHOENIX-3822

[jira] [Commented] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

[ https://issues.apache.org/jira/browse/PHOENIX-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15992862#comment-15992862 ] Hadoop QA commented on PHOENIX-3822: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-3814) Unable to connect to Phoenix via Spark

[ https://issues.apache.org/jira/browse/PHOENIX-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993642#comment-15993642 ] Wajid Khattak commented on PHOENIX-3814: [~jmahonin] Thanks for getting back to me. I hope the

[jira] [Created] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row

Vincent Poon created PHOENIX-3824: - Summary: Mutable Index partial rebuild adds more than one index row for updated data row Key: PHOENIX-3824 URL: https://issues.apache.org/jira/browse/PHOENIX-3824

[jira] [Created] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

Vincent Poon created PHOENIX-3825: - Summary: Mutable Index rebuild does not write an index version for each data row version Key: PHOENIX-3825 URL: https://issues.apache.org/jira/browse/PHOENIX-3825

[jira] [Commented] (PHOENIX-3772) Local Index - table split fails and OOM

[ https://issues.apache.org/jira/browse/PHOENIX-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15994298#comment-15994298 ] Lars Hofhansl commented on PHOENIX-3772: OK to close this one? Or keep it open just in case? >

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15994297#comment-15994297 ] Lars Hofhansl commented on PHOENIX-3797: Whoa. [~rajeshbabu], any hints? > Local Index -

[jira] [Commented] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row

[ https://issues.apache.org/jira/browse/PHOENIX-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15994299#comment-15994299 ] Lars Hofhansl commented on PHOENIX-3824: Is this what causes PHOENIX-3806? > Mutable Index