[jira] [Commented] (PHOENIX-2892) Scan for pre-warming the block cache for 2ndary index should be removed

2016-05-16 Thread Jesse Yates (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286053#comment-15286053 ] Jesse Yates commented on PHOENIX-2892: -- We need the locks when the edits are updating rows to

[jira] [Commented] (PHOENIX-1734) Local index improvements

2016-05-16 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286031#comment-15286031 ] ASF GitHub Bot commented on PHOENIX-1734: - Github user chrajeshbabu commented on the pull

[GitHub] phoenix pull request: PHOENIX-1734 Local index improvements(Rajesh...

2016-05-16 Thread chrajeshbabu
Github user chrajeshbabu commented on the pull request: https://github.com/apache/phoenix/pull/168#issuecomment-219617896 James as we discussed I have made a patch working with older versions of HBase first and handled review comments here. Will create new pull request with that

[GitHub] phoenix pull request: PHOENIX-1734 Local index improvements(Rajesh...

2016-05-16 Thread chrajeshbabu
Github user chrajeshbabu commented on a diff in the pull request: https://github.com/apache/phoenix/pull/168#discussion_r63463623 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/index/PhoenixTransactionalIndexer.java --- @@ -160,6 +163,9 @@ public void

[jira] [Commented] (PHOENIX-1734) Local index improvements

2016-05-16 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286029#comment-15286029 ] ASF GitHub Bot commented on PHOENIX-1734: - Github user chrajeshbabu commented on a diff in the

[GitHub] phoenix pull request: PHOENIX-1734 Local index improvements(Rajesh...

2016-05-16 Thread chrajeshbabu
Github user chrajeshbabu commented on a diff in the pull request: https://github.com/apache/phoenix/pull/168#discussion_r63463618 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/hbase/index/write/ParallelWriterIndexCommitter.java --- @@ -116,7 +117,10 @@ public void

[jira] [Commented] (PHOENIX-1734) Local index improvements

2016-05-16 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286030#comment-15286030 ] ASF GitHub Bot commented on PHOENIX-1734: - Github user chrajeshbabu commented on a diff in the

[GitHub] phoenix pull request: PHOENIX-1734 Local index improvements(Rajesh...

2016-05-16 Thread chrajeshbabu
Github user chrajeshbabu commented on a diff in the pull request: https://github.com/apache/phoenix/pull/168#discussion_r63463584 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java --- @@ -1016,7 +1016,7 @@ private MutationState

[jira] [Commented] (PHOENIX-1734) Local index improvements

2016-05-16 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286027#comment-15286027 ] ASF GitHub Bot commented on PHOENIX-1734: - Github user chrajeshbabu commented on a diff in the

[jira] [Commented] (PHOENIX-1734) Local index improvements

2016-05-16 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286025#comment-15286025 ] ASF GitHub Bot commented on PHOENIX-1734: - Github user chrajeshbabu commented on a diff in the

[GitHub] phoenix pull request: PHOENIX-1734 Local index improvements(Rajesh...

2016-05-16 Thread chrajeshbabu
Github user chrajeshbabu commented on a diff in the pull request: https://github.com/apache/phoenix/pull/168#discussion_r63463462 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/execute/DelegateHTable.java --- @@ -297,4 +297,28 @@ public boolean checkAndDelete(byte[] row,

[GitHub] phoenix pull request: PHOENIX-1734 Local index improvements(Rajesh...

2016-05-16 Thread chrajeshbabu
Github user chrajeshbabu commented on a diff in the pull request: https://github.com/apache/phoenix/pull/168#discussion_r63463482 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/index/IndexMaintainer.java --- @@ -861,7 +871,12 @@ public Put

[jira] [Commented] (PHOENIX-1734) Local index improvements

2016-05-16 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286023#comment-15286023 ] ASF GitHub Bot commented on PHOENIX-1734: - Github user chrajeshbabu commented on a diff in the

[GitHub] phoenix pull request: PHOENIX-1734 Local index improvements(Rajesh...

2016-05-16 Thread chrajeshbabu
Github user chrajeshbabu commented on a diff in the pull request: https://github.com/apache/phoenix/pull/168#discussion_r63463350 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java --- @@ -202,7 +207,10 @@ protected

[jira] [Commented] (PHOENIX-1734) Local index improvements

2016-05-16 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286020#comment-15286020 ] ASF GitHub Bot commented on PHOENIX-1734: - Github user chrajeshbabu commented on a diff in the

[jira] [Commented] (PHOENIX-1734) Local index improvements

2016-05-16 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286018#comment-15286018 ] ASF GitHub Bot commented on PHOENIX-1734: - Github user chrajeshbabu commented on a diff in the

[GitHub] phoenix pull request: PHOENIX-1734 Local index improvements(Rajesh...

2016-05-16 Thread chrajeshbabu
Github user chrajeshbabu commented on a diff in the pull request: https://github.com/apache/phoenix/pull/168#discussion_r63463302 --- Diff: phoenix-core/src/it/java/org/apache/phoenix/end2end/SortMergeJoinIT.java --- @@ -187,13 +186,13 @@ public void initTable() throws Exception {

[jira] [Updated] (PHOENIX-2894) Join return incomplete results in some cases

2016-05-16 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated PHOENIX-2894: - Attachment: PHOENIX-2894.patch Exactly as [~pierre.lacave] had guessed, it was related to the

[jira] [Commented] (PHOENIX-2892) Scan for pre-warming the block cache for 2ndary index should be removed

2016-05-16 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285866#comment-15285866 ] Hadoop QA commented on PHOENIX-2892: {color:red}-1 overall{color}. Here are the results of testing

Antlr dependency issue

2016-05-16 Thread William
Hi all I found a weird problem when executing 'mvn dependency:tree -pl=phoenix-core'. It shows that we depends on both antlr-3.5.jar and antlr-2.7.7.jar. [INFO] org.apache.phoenix:phoenix-core:jar:4.6-adh6u-SNAPSHOT [INFO] +- org.antlr:antlr:jar:3.5:compile [INFO] | \-

[jira] [Commented] (PHOENIX-2892) Scan for pre-warming the block cache for 2ndary index should be removed

2016-05-16 Thread Enis Soztutar (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285859#comment-15285859 ] Enis Soztutar commented on PHOENIX-2892: bq. The initial scan makes the overall operation

[jira] [Commented] (PHOENIX-2898) HTable not closed in ConnectionQueryServicesImpl

2016-05-16 Thread Alex Araujo (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285826#comment-15285826 ] Alex Araujo commented on PHOENIX-2898: -- PhoenixSparkIT failures look unrelated. They have been

[jira] [Updated] (PHOENIX-2905) hadoop-2.5.1 artifacts are in the dependency tree

2016-05-16 Thread Enis Soztutar (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated PHOENIX-2905: --- Attachment: phoenix-2905_v1.patch This should do the trick. [~sergey.soldatov] FYI. >

[jira] [Updated] (PHOENIX-2905) hadoop-2.5.1 artifacts are in the dependency tree

2016-05-16 Thread Enis Soztutar (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated PHOENIX-2905: --- Attachment: dep This is causing problems in eclipse since all UT runs fail with

[jira] [Created] (PHOENIX-2906) Modify pom to use the use the 0.8.0-incubating apache tephra

2016-05-16 Thread Thomas D'Silva (JIRA)
Thomas D'Silva created PHOENIX-2906: --- Summary: Modify pom to use the use the 0.8.0-incubating apache tephra Key: PHOENIX-2906 URL: https://issues.apache.org/jira/browse/PHOENIX-2906 Project:

[jira] [Commented] (PHOENIX-2892) Scan for pre-warming the block cache for 2ndary index should be removed

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285794#comment-15285794 ] James Taylor commented on PHOENIX-2892: --- The batch size should really be byte-based instead of

[jira] [Commented] (PHOENIX-2898) HTable not closed in ConnectionQueryServicesImpl

2016-05-16 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285788#comment-15285788 ] Hadoop QA commented on PHOENIX-2898: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Created] (PHOENIX-2905) hadoop-2.5.1 artifacts are in the dependency tree

2016-05-16 Thread Enis Soztutar (JIRA)
Enis Soztutar created PHOENIX-2905: -- Summary: hadoop-2.5.1 artifacts are in the dependency tree Key: PHOENIX-2905 URL: https://issues.apache.org/jira/browse/PHOENIX-2905 Project: Phoenix

[jira] [Commented] (PHOENIX-541) Make mutable batch size bytes-based instead of row-based

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285779#comment-15285779 ] James Taylor commented on PHOENIX-541: -- [~sergey.soldatov] - any interest in this one? > Make

[jira] [Commented] (PHOENIX-542) Batch size calculations should take into account secondary indexes

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285780#comment-15285780 ] James Taylor commented on PHOENIX-542: -- [~sergey.soldatov] - any interest in this one? > Batch size

[jira] [Comment Edited] (PHOENIX-2892) Scan for pre-warming the block cache for 2ndary index should be removed

2016-05-16 Thread Enis Soztutar (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285753#comment-15285753 ] Enis Soztutar edited comment on PHOENIX-2892 at 5/17/16 12:51 AM: -- bq.

[jira] [Commented] (PHOENIX-2892) Scan for pre-warming the block cache for 2ndary index should be removed

2016-05-16 Thread Enis Soztutar (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285753#comment-15285753 ] Enis Soztutar commented on PHOENIX-2892: bq. One thing to try would be to lower this and confirm

[jira] [Updated] (PHOENIX-2898) HTable not closed in ConnectionQueryServicesImpl

2016-05-16 Thread Alex Araujo (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Araujo updated PHOENIX-2898: - Attachment: PHOENIX-2898-4.x-HBase.patch Thanks for the review [~jamestaylor]. Attaching patch

[jira] [Updated] (PHOENIX-2904) Fix UPDATE STATISTICS documentation

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2904: -- Fix Version/s: 4.8.0 > Fix UPDATE STATISTICS documentation >

[jira] [Assigned] (PHOENIX-2904) Fix UPDATE STATISTICS documentation

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-2904: - Assignee: James Taylor > Fix UPDATE STATISTICS documentation >

[jira] [Created] (PHOENIX-2904) Fix UPDATE STATISTICS documentation

2016-05-16 Thread James Taylor (JIRA)
James Taylor created PHOENIX-2904: - Summary: Fix UPDATE STATISTICS documentation Key: PHOENIX-2904 URL: https://issues.apache.org/jira/browse/PHOENIX-2904 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2903: -- Attachment: PHOENIX-2903_wip.patch WIP patch. > Handle split during scan for row key

[jira] [Created] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

2016-05-16 Thread James Taylor (JIRA)
James Taylor created PHOENIX-2903: - Summary: Handle split during scan for row key ordered aggregations Key: PHOENIX-2903 URL: https://issues.apache.org/jira/browse/PHOENIX-2903 Project: Phoenix

[jira] [Resolved] (PHOENIX-2883) Region close during automatic disabling of index for rebuilding can lead to RS abort

2016-05-16 Thread Josh Elser (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-2883. - Resolution: Incomplete > Region close during automatic disabling of index for rebuilding can

[jira] [Commented] (PHOENIX-2883) Region close during automatic disabling of index for rebuilding can lead to RS abort

2016-05-16 Thread Josh Elser (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285098#comment-15285098 ] Josh Elser commented on PHOENIX-2883: - Linked over to HBASE-15837 a bit ago for a little patch which

[jira] [Created] (PHOENIX-2902) Adjust PhoenixDatabaseMetadata#getSchemas query if namespaces are enabled

2016-05-16 Thread James Taylor (JIRA)
James Taylor created PHOENIX-2902: - Summary: Adjust PhoenixDatabaseMetadata#getSchemas query if namespaces are enabled Key: PHOENIX-2902 URL: https://issues.apache.org/jira/browse/PHOENIX-2902

[jira] [Created] (PHOENIX-2901) If namespaces are enabled, check for existence of schema when sequence created

2016-05-16 Thread James Taylor (JIRA)
James Taylor created PHOENIX-2901: - Summary: If namespaces are enabled, check for existence of schema when sequence created Key: PHOENIX-2901 URL: https://issues.apache.org/jira/browse/PHOENIX-2901

[jira] [Updated] (PHOENIX-2489) Support sequence metadata access through DatabaseMetaData interface

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2489: -- Assignee: (was: Maryann Xue) > Support sequence metadata access through DatabaseMetaData

[jira] [Updated] (PHOENIX-2489) Support sequence metadata access through DatabaseMetaData interface

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2489: -- Fix Version/s: 4.8.0 > Support sequence metadata access through DatabaseMetaData interface >

[jira] [Resolved] (PHOENIX-2784) phoenix-spark: Allow coercion of DATE fields to TIMESTAMP when loading DataFrames

2016-05-16 Thread Josh Mahonin (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Mahonin resolved PHOENIX-2784. --- Resolution: Fixed > phoenix-spark: Allow coercion of DATE fields to TIMESTAMP when loading

[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-2880) Switch to the new RegionObserver#preStoreScannerOpen() method which accepts read point parameter

2016-05-16 Thread Ted Yu (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated PHOENIX-2880: Description: Over in HBASE-15759, the following method is added to RegionObserver : {code} public

[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

[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-2894) Join return incomplete results in some cases

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2894: -- Fix Version/s: 4.8.0 > Join return incomplete results in some cases >

[jira] [Commented] (PHOENIX-2894) Join return incomplete results in some cases

2016-05-16 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284652#comment-15284652 ] James Taylor commented on PHOENIX-2894: --- bq. Looks to me that this "CLIENT SORTED BY [BUCKET,

[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: -- 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 salted table jo 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 salted table jo may cause "could not

[jira] [Updated] (PHOENIX-2900) Once a salted table 's first region has been split, the Join sql which 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 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] [Created] (PHOENIX-2900) Once a salted table 's first region has been split, the Join sql which salted table as lhs may cause "could not find hash cache for joinId" error

2016-05-16 Thread chenglei (JIRA)
chenglei created PHOENIX-2900: - Summary: Once a salted table 's first region has been split, the Join sql which salted table as lhs may cause "could not find hash cache for joinId" error Key: PHOENIX-2900 URL:

[jira] [Commented] (PHOENIX-2862) Do client server compatibility checks before upgrading system tables

2016-05-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284258#comment-15284258 ] Hudson commented on PHOENIX-2862: - FAILURE: Integrated in Phoenix-master #1225 (See

[jira] [Commented] (PHOENIX-2884) Fix EXPLAIN plan for offset on salted table

2016-05-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284260#comment-15284260 ] Hudson commented on PHOENIX-2884: - FAILURE: Integrated in Phoenix-master #1225 (See

[jira] [Commented] (PHOENIX-2887) Uberjar application fail with "IllegalAccessError: class com.google.protobuf.ZeroCopyLiteralByteString cannot access its superclass com.google.protobuf.LiteralByteStr

2016-05-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284259#comment-15284259 ] Hudson commented on PHOENIX-2887: - FAILURE: Integrated in Phoenix-master #1225 (See

[jira] [Commented] (PHOENIX-423) Support DISTINCT for AVG

2016-05-16 Thread ramkrishna.s.vasudevan (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284193#comment-15284193 ] ramkrishna.s.vasudevan commented on PHOENIX-423: [~Alexander Boruchinkin] Have you

[jira] [Commented] (PHOENIX-424) Support DISTINCT for SUM

2016-05-16 Thread ramkrishna.s.vasudevan (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284192#comment-15284192 ] ramkrishna.s.vasudevan commented on PHOENIX-424: [~Alexander Boruchinkin] Let me know how