[jira] [Updated] (PHOENIX-2970) SpoolingResultIterator using memory too conservative,and it lead to use temp file unnecessaryly

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Summary: SpoolingResultIterator using memory too conservative,and it lead to use temp file

[jira] [Updated] (PHOENIX-2970) SpoolingResultIterator using memory too conservative ,and it leads to use temp file unnecessaryly

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Summary: SpoolingResultIterator using memory too conservative ,and it leads to use temp file

[jira] [Updated] (PHOENIX-2970) SpoolingResultIterator using memory too conservative , which leads to use temp file unnecessaryly

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Summary: SpoolingResultIterator using memory too conservative , which leads to use temp file

[jira] [Created] (PHOENIX-2970) SpoolingResultIterator using memory too conservative

2016-06-07 Thread chenglei (JIRA)
chenglei created PHOENIX-2970: - Summary: SpoolingResultIterator using memory too conservative Key: PHOENIX-2970 URL: https://issues.apache.org/jira/browse/PHOENIX-2970 Project: Phoenix Issue

[jira] [Updated] (PHOENIX-2970) SpoolingResultIterator using memory too conservative

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Description: Even if SpoolingResultIterator will be deprecated, but HBase older than than

[jira] [Updated] (PHOENIX-2970) SpoolingResultIterator using memory too conservative

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Description: Even if SpoolingResultIterator will be deprecated, but HBase older than than 0.98.17

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

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Description: Even if SpoolingResultIterator will be deprecated, but HBase older than than 0.98.17

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

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Summary: SpoolingResultIterator using memory too conservatively , which leads to using temp file

[jira] [Updated] (PHOENIX-2970) SpoolingResultIterator using memory too conservative

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Description: Even if SpoolingResultIterator will be deprecated, but HBase older than than 0.98.17

[jira] [Updated] (PHOENIX-2970) SpoolingResultIterator using memory too conservative

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Description: Even if SpoolingResultIterator will be deprecated, but HBase older than than 0.98.17

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

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Summary: SpoolingResultIterator using memory too conservatively , which leads to use temp file

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

2016-06-07 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2970: -- Description: Even if SpoolingResultIterator will be deprecated, but HBase older than 0.98.17 would

[jira] [Commented] (PHOENIX-2876) Using aggregation function in ORDER BY

2016-06-14 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331089#comment-15331089 ] chenglei commented on PHOENIX-2876: --- I think the AggregationManager's compile method should be static

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-26 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which has been split after creation) with another table in

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error,

2016-05-26 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Summary: Once a salted table 's first region has been split, the join SQL which the salted table as

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error,even though we cle

2016-05-26 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Summary: Once a salted table 's first region has been split, the join SQL which the salted table as

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error,even though the sa

2016-05-26 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Summary: Once a salted table 's first region has been split, the join SQL which the salted table as

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Commented] (PHOENIX-2613) Infinite loop in SkipScan when seeking past null value in non leading primary key column

2016-01-21 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15111984#comment-15111984 ] chenglei commented on PHOENIX-2613: --- I agree the cause of this issue is the following if condition in

[jira] [Comment Edited] (PHOENIX-2613) Infinite loop in SkipScan when seeking past null value in non leading primary key column

2016-01-21 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15111984#comment-15111984 ] chenglei edited comment on PHOENIX-2613 at 1/22/16 6:16 AM: I agree the

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2613) if any column of multi-part primary key is null, the Skip Scan may cause RegionServer scan indefinite loop

2016-01-20 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2613: -- Description: In pheonix 4.6,any column of multi-part primary key can be null.If a table has one row

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregation may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Summary: ClientAggregatePlan incorrectly using limit in aggregation may cause sql with limit clause

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Summary: ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Fix Version/s: (was: 4.7.0) > ClientAggregatePlan incorrectly uses limit in aggregation may cause

[jira] [Comment Edited] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185116#comment-15185116 ] chenglei edited comment on PHOENIX-2753 at 3/8/16 3:59 PM: --- Sorry,I found the

[jira] [Created] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
chenglei created PHOENIX-2753: - Summary: ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave Key: PHOENIX-2753 URL: https://issues.apache.org/jira/browse/PHOENIX-2753

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Fix Version/s: 4.7.0 > ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Resolved] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei resolved PHOENIX-2753. --- Resolution: Fixed sorry,I found the 2279 fixed this problem > ClientAggregatePlan incorrectly uses

[jira] [Comment Edited] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

2016-03-08 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185116#comment-15185116 ] chenglei edited comment on PHOENIX-2753 at 3/8/16 3:52 PM: --- sorry,I found the

[jira] [Created] (PHOENIX-2748) CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autocommit to false explicitly

2016-03-04 Thread chenglei (JIRA)
chenglei created PHOENIX-2748: - Summary: CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autocommit to false explicitly Key: PHOENIX-2748 URL:

[jira] [Updated] (PHOENIX-2748) CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autoCommit to false explicitly

2016-03-04 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2748: -- Summary: CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autoCommit to

[jira] [Updated] (PHOENIX-2748) CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autoCommit to false explicitly

2016-03-04 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2748: -- Description: CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues which

[jira] [Updated] (PHOENIX-2748) CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autoCommit to false explicitly

2016-03-04 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2748: -- Description: CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues which

[jira] [Updated] (PHOENIX-2748) CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autoCommit to false explicitly

2016-03-04 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2748: -- Description: CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues which

[jira] [Updated] (PHOENIX-2748) CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autoCommit to false explicitly

2016-03-04 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2748: -- Description: CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues which

[jira] [Updated] (PHOENIX-2748) CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autoCommit to false explicitly

2016-03-04 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2748: -- Description: CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues

[jira] [Updated] (PHOENIX-2748) CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autoCommit to false explicitly

2016-03-04 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2748: -- Description: CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues which

[jira] [Updated] (PHOENIX-2748) CsvToKeyValueMapper used by CsvBulkLoadTool should set inner PhoenixConnection autoCommit to false explicitly

2016-03-04 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2748: -- Description: CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues which

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-17 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which has been split after creation) with another table in

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-19 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Priority: Major (was: Critical) > Once a salted table 's first region has been split, the join SQL

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-22 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Priority: Critical (was: Major) > Once a salted table 's first region has been split, the join SQL

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the Join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the Join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the Join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the Join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Summary: Once a salted table 's first region has been split, the Join SQL which the salted table as

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the Join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the Join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the Join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the Join SQL which the salted table as LHS may cause "Could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2900: -- Description: When I join a salted table (which is split after creation) with another table in my

  1   2   3   4   5   6   7   >