subject:"\[jira\] \[Commented\] \(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 c"

[jira] [Commented] (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 c

2016-07-17 Thread James Taylor (JIRA)

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381257#comment-15381257 ] James Taylor commented on PHOENIX-2900: --- Thanks for the patch and excellent analys

[jira] [Commented] (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 c

2016-07-15 Thread ASF GitHub Bot (JIRA)

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379617#comment-15379617 ] ASF GitHub Bot commented on PHOENIX-2900: - GitHub user comnetwork opened a pull

[jira] [Commented] (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 c

[jira] [Commented] (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 c

2 matches

Site Navigation

Mail list logo

Footer information