[jira] [Resolved] (PHOENIX-3040) Don't use guideposts for executing queries serially

[ https://issues.apache.org/jira/browse/PHOENIX-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-3040. --- Resolution: Fixed > Don't use guideposts for executing queries serially >

Re: where are we at with the RC?

PHOENIX-2724 has a workaround in PHOENIX-3040 that I have checked in. I think we can fix PHOENIX-2724 in a patch release, if needed. The remaining outstanding JIRAs that I know of are: https://issues.apache.org/jira/browse/PHOENIX-2902 https://issues.apache.org/jira/browse/PHOENIX-29

[jira] [Updated] (PHOENIX-3040) Don't use guideposts for executing queries serially

[ https://issues.apache.org/jira/browse/PHOENIX-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3040: -- Attachment: PHOENIX-3040_v2.patch Final patch. > Don't use guideposts for executing queries

[jira] [Updated] (PHOENIX-3040) Don't use guideposts for executing queries serially

[ https://issues.apache.org/jira/browse/PHOENIX-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3040: -- Summary: Don't use guideposts for executing queries serially (was: Use serial mode of query

Re: where are we at with the RC?

PHOENIX-3037 (Andy just committed) needs to get in. -- Lars From: Samarth Jain To: dev Cc: Ankit Singhal Sent: Tuesday, June 28, 2016 9:58 AM Subject: Re: where are we at with the RC? PHOENIX-3028 is in. PHOENIX-2724 is

[jira] [Commented] (PHOENIX-3037) Setup proper security context in compaction/split coprocessor hooks

[ https://issues.apache.org/jira/browse/PHOENIX-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358294#comment-15358294 ] Lars Hofhansl commented on PHOENIX-3037: Nice. > Setup proper security context in

[jira] [Commented] (PHOENIX-3040) Use serial mode of query execution when amount of data to scan is below a threshold

[ https://issues.apache.org/jira/browse/PHOENIX-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358109#comment-15358109 ] Mujtaba Chohan commented on PHOENIX-3040: - No perf regression via test suite as well. > Use

Re: URIException with PhoenixHBaseLoader

Yes if we go down the marker interface approach. PhoenixLoader will have to be updated to use the same. I will create a phoenix jira also once I have the pig patch ready On Wed, Jun 29, 2016 at 11:58 PM, James Taylor wrote: > Do we need a PHOENIX JIRA for this, Siddhi? >

[jira] [Commented] (PHOENIX-3040) Use serial mode of query execution when amount of data to scan is below a threshold

[ https://issues.apache.org/jira/browse/PHOENIX-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358031#comment-15358031 ] Mujtaba Chohan commented on PHOENIX-3040: - Runnings test suite now. I'll update soon. > Use

[jira] [Commented] (PHOENIX-3037) Setup proper security context in compaction/split coprocessor hooks

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

[jira] [Commented] (PHOENIX-2999) Upgrading Multi-tenant table to map with namespace using upgradeUtil

[ https://issues.apache.org/jira/browse/PHOENIX-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357981#comment-15357981 ] Samarth Jain commented on PHOENIX-2999: --- +1 to what James said. Otherwise, LGTM! > Upgrading

[jira] [Commented] (PHOENIX-3040) Use serial mode of query execution when amount of data to scan is below a threshold

[ https://issues.apache.org/jira/browse/PHOENIX-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357968#comment-15357968 ] Samarth Jain commented on PHOENIX-3040: --- Thanks for the quick turn around, [~mujtabachohan]. Do

[jira] [Commented] (PHOENIX-3040) Use serial mode of query execution when amount of data to scan is below a threshold

[ https://issues.apache.org/jira/browse/PHOENIX-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357917#comment-15357917 ] Mujtaba Chohan commented on PHOENIX-3040: - Works great. Thanks [~samarthjain] > Use serial mode

[jira] [Updated] (PHOENIX-3040) Use serial mode of query execution when amount of data to scan is below a threshold

[ https://issues.apache.org/jira/browse/PHOENIX-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3040: -- Attachment: PHOENIX-3040.patch [~jamestaylor] - I created this new JIRA to track the work

[jira] [Created] (PHOENIX-3040) Use serial mode of query execution when amount of data to scan is below a threshold

Samarth Jain created PHOENIX-3040: - Summary: Use serial mode of query execution when amount of data to scan is below a threshold Key: PHOENIX-3040 URL: https://issues.apache.org/jira/browse/PHOENIX-3040

[jira] [Updated] (PHOENIX-3036) Modify phoenix IT tests to extend BaseHBaseManagedTimeTableReuseIT

[ https://issues.apache.org/jira/browse/PHOENIX-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3036: -- Assignee: prakul agarwal > Modify phoenix IT tests to extend BaseHBaseManagedTimeTableReuseIT

[jira] [Commented] (PHOENIX-2724) Query with large number of guideposts is slower compared to no stats

[ https://issues.apache.org/jira/browse/PHOENIX-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357755#comment-15357755 ] James Taylor commented on PHOENIX-2724: --- I'd default to 20%. > Query with large number of

[jira] [Commented] (PHOENIX-2724) Query with large number of guideposts is slower compared to no stats

[ https://issues.apache.org/jira/browse/PHOENIX-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357750#comment-15357750 ] Samarth Jain commented on PHOENIX-2724: --- [~jamestaylor] bq. I'd suggest making the configuration

[jira] [Commented] (PHOENIX-3036) Modify phoenix IT tests to extend BaseHBaseManagedTimeTableReuseIT

[ https://issues.apache.org/jira/browse/PHOENIX-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357748#comment-15357748 ] prakul agarwal commented on PHOENIX-3036: - I will be submitting a patch soon. > Modify phoenix

[jira] [Commented] (PHOENIX-3037) Setup proper security context in compaction/split coprocessor hooks

[ https://issues.apache.org/jira/browse/PHOENIX-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357692#comment-15357692 ] Andrew Purtell commented on PHOENIX-3037: - Great, I will commit this change to all active

[jira] [Commented] (PHOENIX-3037) Setup proper security context in compaction/split coprocessor hooks

[ https://issues.apache.org/jira/browse/PHOENIX-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357665#comment-15357665 ] Enis Soztutar commented on PHOENIX-3037: Looks good to me. > Setup proper security context in

[jira] [Comment Edited] (PHOENIX-2970) SpoolingResultIterator using memory too conservatively , which leads to using temp file unnecessaryly

[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356733#comment-15356733 ] chenglei edited comment on PHOENIX-2970 at 6/30/16 8:35 AM:

[jira] [Comment Edited] (PHOENIX-2970) SpoolingResultIterator using memory too conservatively , which leads to using temp file unnecessaryly

[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356733#comment-15356733 ] chenglei edited comment on PHOENIX-2970 at 6/30/16 8:35 AM:

[jira] [Comment Edited] (PHOENIX-2970) SpoolingResultIterator using memory too conservatively , which leads to using temp file unnecessaryly

[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356733#comment-15356733 ] chenglei edited comment on PHOENIX-2970 at 6/30/16 8:31 AM:

[jira] [Comment Edited] (PHOENIX-2970) SpoolingResultIterator using memory too conservatively , which leads to using temp file unnecessaryly

[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356733#comment-15356733 ] chenglei edited comment on PHOENIX-2970 at 6/30/16 8:30 AM:

[jira] [Comment Edited] (PHOENIX-2970) SpoolingResultIterator using memory too conservatively , which leads to using temp file unnecessaryly

[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356733#comment-15356733 ] chenglei edited comment on PHOENIX-2970 at 6/30/16 8:29 AM:

[jira] [Comment Edited] (PHOENIX-2970) SpoolingResultIterator using memory too conservatively , which leads to using temp file unnecessaryly

[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356733#comment-15356733 ] chenglei edited comment on PHOENIX-2970 at 6/30/16 8:29 AM: Yes,@James in

[jira] [Commented] (PHOENIX-2970) SpoolingResultIterator using memory too conservatively , which leads to using temp file unnecessaryly

[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356733#comment-15356733 ] chenglei commented on PHOENIX-2970: --- Yes,in our business system, we had already set the

[jira] [Commented] (PHOENIX-2999) Upgrading Multi-tenant table to map with namespace using upgradeUtil

[ https://issues.apache.org/jira/browse/PHOENIX-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356702#comment-15356702 ] James Taylor commented on PHOENIX-2999: --- To go this route, just update this code in

[jira] [Comment Edited] (PHOENIX-2999) Upgrading Multi-tenant table to map with namespace using upgradeUtil

[ https://issues.apache.org/jira/browse/PHOENIX-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356667#comment-15356667 ] James Taylor edited comment on PHOENIX-2999 at 6/30/16 7:31 AM: Also,

[jira] [Commented] (PHOENIX-2999) Upgrading Multi-tenant table to map with namespace using upgradeUtil

[ https://issues.apache.org/jira/browse/PHOENIX-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356667#comment-15356667 ] James Taylor commented on PHOENIX-2999: --- Also, please file another JIRA to set the TABLE_TYPE on

Re: URIException with PhoenixHBaseLoader

Do we need a PHOENIX JIRA for this, Siddhi? On Wed, Jun 29, 2016 at 6:25 PM, Siddhi Mehta wrote: > jira filed > https://issues.apache.org/jira/browse/PIG-4939 > > I will work on the patch today and have it out for review > > Thanks, > Siddhi > > On Tue, Jun 28, 2016 at 3:40

[jira] [Created] (PHOENIX-3039) rpcTimetout

fl8012 created PHOENIX-3039: --- Summary: rpcTimetout Key: PHOENIX-3039 URL: https://issues.apache.org/jira/browse/PHOENIX-3039 Project: Phoenix Issue Type: Bug Affects Versions: 4.2.2

[jira] [Commented] (PHOENIX-2999) Upgrading Multi-tenant table to map with namespace using upgradeUtil

[ https://issues.apache.org/jira/browse/PHOENIX-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356604#comment-15356604 ] Thomas D'Silva commented on PHOENIX-2999: - [~an...@apache.org] Do we need to file a separate

[jira] [Commented] (PHOENIX-2995) Write performance severely degrades with large number of views

[ https://issues.apache.org/jira/browse/PHOENIX-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356585#comment-15356585 ] James Taylor commented on PHOENIX-2995: --- We really only need to copy the Map the first time the

[jira] [Commented] (PHOENIX-3037) Setup proper security context in compaction/split coprocessor hooks

[ https://issues.apache.org/jira/browse/PHOENIX-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356583#comment-15356583 ] Samarth Jain commented on PHOENIX-3037: --- +1 > Setup proper security context in compaction/split