[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400377#comment-15400377 ] Enis Soztutar commented on PHOENIX-3111: Indeed. +1 from me for 4.8. However, we should make

[jira] [Commented] (PHOENIX-2084) Support loading json data using apache phoenix flume plugin

[ https://issues.apache.org/jira/browse/PHOENIX-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400327#comment-15400327 ] Kalyan commented on PHOENIX-2084: - Hi Josh Mahonin , i will work on Array Columns support .. i will

[jira] [Commented] (PHOENIX-3120) AsyncIndexRebuilderTask fails for transactional tables

[ https://issues.apache.org/jira/browse/PHOENIX-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400322#comment-15400322 ] Hudson commented on PHOENIX-3120: - FAILURE: Integrated in Phoenix-master #1347 (See

[jira] [Commented] (PHOENIX-3120) AsyncIndexRebuilderTask fails for transactional tables

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

[jira] [Commented] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index

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

[jira] [Commented] (PHOENIX-3120) AsyncIndexRebuilderTask fails for transactional tables

[ https://issues.apache.org/jira/browse/PHOENIX-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399976#comment-15399976 ] James Taylor commented on PHOENIX-3120: --- +1. Thanks, [~tdsilva] > AsyncIndexRebuilderTask fails

[jira] [Updated] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index

[ https://issues.apache.org/jira/browse/PHOENIX-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3128: -- Attachment: PHOENIX-3128_wip.patch Here's a partial patch. Still need to prevent the calls to

[jira] [Updated] (PHOENIX-3120) AsyncIndexRebuilderTask fails for transactional tables

[ https://issues.apache.org/jira/browse/PHOENIX-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3120: Attachment: PHOENIX-3120-v2.patch [~jamestaylor] Thanks for the review. I have attached

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399916#comment-15399916 ] James Taylor commented on PHOENIX-3111: --- So this JIRA helps, right, [~enis], by blocking a split

[jira] [Commented] (PHOENIX-3121) Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

[ https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399915#comment-15399915 ] James Taylor commented on PHOENIX-3121: --- How about the simple solutions of setting the scanner

[jira] [Commented] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399906#comment-15399906 ] Enis Soztutar commented on PHOENIX-3111: I think a similar thing like the one here is happening:

[jira] [Updated] (PHOENIX-3104) Enable Phoenix test cases with Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3104: -- Description: The following Jenkins job is run daily to track our progress:

[jira] [Created] (PHOENIX-3129) Use non-covering global index automatically without hint if the filter is selective enough

Maryann Xue created PHOENIX-3129: Summary: Use non-covering global index automatically without hint if the filter is selective enough Key: PHOENIX-3129 URL: https://issues.apache.org/jira/browse/PHOENIX-3129

[jira] [Comment Edited] (PHOENIX-3121) Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

[ https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399837#comment-15399837 ] Samarth Jain edited comment on PHOENIX-3121 at 7/29/16 6:46 PM: I was

[jira] [Commented] (PHOENIX-3121) Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

[ https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399837#comment-15399837 ] Samarth Jain commented on PHOENIX-3121: --- I was slightly wrong. The cache size matters even for the

[jira] [Commented] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index

[ https://issues.apache.org/jira/browse/PHOENIX-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399832#comment-15399832 ] James Taylor commented on PHOENIX-3128: --- Good catch, [~junegunn]. The first change in

[jira] [Commented] (PHOENIX-3121) Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

[ https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399770#comment-15399770 ] James Taylor commented on PHOENIX-3121: --- Agreed - in that case we need to consider offset + limit.

[jira] [Commented] (PHOENIX-3121) Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

[ https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399765#comment-15399765 ] Samarth Jain commented on PHOENIX-3121: --- I think when we are doing the offset on client, then the

[jira] [Commented] (PHOENIX-3121) Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

[ https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399735#comment-15399735 ] James Taylor commented on PHOENIX-3121: --- On second thought, I don't think this is an issue,

[jira] [Commented] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index

[ https://issues.apache.org/jira/browse/PHOENIX-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399723#comment-15399723 ] Rajeshbabu Chintaguntla commented on PHOENIX-3128: -- [~jamestaylor] bq. The idea with

[jira] [Updated] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index

[ https://issues.apache.org/jira/browse/PHOENIX-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-3128: - Fix Version/s: 4.8.0 > Remove extraneous operations during upsert with

[jira] [Commented] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index

[ https://issues.apache.org/jira/browse/PHOENIX-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399628#comment-15399628 ] James Taylor commented on PHOENIX-3128: --- The idea with that code is to not send local immutable

[jira] [Commented] (PHOENIX-3121) Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

[ https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399427#comment-15399427 ] James Taylor commented on PHOENIX-3121: --- Had the same nagging suspicion, [~samarthjain]. I think

[jira] [Commented] (PHOENIX-2785) Do not store NULLs for immutable tables

[ https://issues.apache.org/jira/browse/PHOENIX-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399244#comment-15399244 ] Ankit Singhal commented on PHOENIX-2785: Sorry [~lhofhansl], I don't know how I missed the above

Re: new 4.8.0 RC?

Following 4 branches have been created and are now available for commits targeted for 4.8.0 only. 4.8-HBase-0.98 (from 4.x-HBase-0.98) 4.8-HBase-1.0 (from 4.x-HBase-1.0) 4.8-HBase-1.1 (from 4.x-HBase-1.1) 4.8-HBase-1.2 (from master) Any commit targeted for 4.8.1 or 4.9+ along with 4.8.0 can go

[jira] [Commented] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index

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

[jira] [Updated] (PHOENIX-3111) Possible Deadlock/delay while building index, upsert select, delete rows at server

[ https://issues.apache.org/jira/browse/PHOENIX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3111: --- Fix Version/s: (was: 4.8.1) 4.8.0 > Possible Deadlock/delay while

[jira] [Updated] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index

[ https://issues.apache.org/jira/browse/PHOENIX-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junegunn Choi updated PHOENIX-3128: --- Attachment: PHOENIX-3128.patch > Remove extraneous operations during upsert with local

[jira] [Created] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index

Junegunn Choi created PHOENIX-3128: -- Summary: Remove extraneous operations during upsert with local immutable index Key: PHOENIX-3128 URL: https://issues.apache.org/jira/browse/PHOENIX-3128 Project:

[jira] [Commented] (PHOENIX-3121) Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

[ https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398964#comment-15398964 ] Ankit Singhal commented on PHOENIX-3121: [~samarthjain], related to first patch only. shouldn't

[jira] [Commented] (PHOENIX-3127) EmptyFamilyName uses the first family name instead of the default one.

[ https://issues.apache.org/jira/browse/PHOENIX-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398860#comment-15398860 ] Sergey Soldatov commented on PHOENIX-3127: -- I see. Actually code from SchemaUtil made me

[jira] [Commented] (PHOENIX-3127) EmptyFamilyName uses the first family name instead of the default one.

[ https://issues.apache.org/jira/browse/PHOENIX-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398832#comment-15398832 ] James Taylor commented on PHOENIX-3127: --- It's by design, but I can see your point (was confused

[jira] [Updated] (PHOENIX-3127) EmptyFamilyName uses the first family name instead of the default one.

[ https://issues.apache.org/jira/browse/PHOENIX-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-3127: - Description: The CF for dummy keys is unpredictable. When we create table like:

[jira] [Created] (PHOENIX-3127) EmptyFamilyName uses the first family name instead of the default one.

Sergey Soldatov created PHOENIX-3127: Summary: EmptyFamilyName uses the first family name instead of the default one. Key: PHOENIX-3127 URL: https://issues.apache.org/jira/browse/PHOENIX-3127