[jira] [Created] (PHOENIX-3081) MIsleading exception on async stats update after major compaction

2016-07-17 Thread Josh Elser (JIRA)
Josh Elser created PHOENIX-3081: --- Summary: MIsleading exception on async stats update after major compaction Key: PHOENIX-3081 URL: https://issues.apache.org/jira/browse/PHOENIX-3081 Project: Phoenix

Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0

2016-07-17 Thread Josh Elser
Sure thing, James. Will resume in the morning when fresh. Exhausted most of my weekend motivations :) Honestly, fixing the tracing UI for the source release should be very simple. Pretty much need to copy the info from my first note into LICENSE. I'm still mulling over whether or not I want

Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0

2016-07-17 Thread James Taylor
Thanks for going through the release, Josh. One partial quick fix might be to exclude the trace app from both the source and binary distributions and move it to github as more of a community add-on (we have a few of these already). To be honest, I don't think it's had much community uptake - a UI

[jira] [Commented] (PHOENIX-3042) Using functional index expression in where statement for join query fails.

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

Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0

2016-07-17 Thread Andrew Purtell
A partial prescription: - Looks like no updates to LICENSE or NOTICE were done when the trace app GSoC project was merged, hence the issues with bootstrap and other bundled JavaScript. Time to do a top to bottom review? - Prune RAT exclusions to the minimum and fix reported issues. - Over

[jira] [Commented] (PHOENIX-3042) Using functional index expression in where statement for join query fails.

2016-07-17 Thread Thomas D'Silva (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381476#comment-15381476 ] Thomas D'Silva commented on PHOENIX-3042: - It looks like the select query that is constructed

[jira] [Commented] (PHOENIX-3042) Using functional index expression in where statement for join query fails.

2016-07-17 Thread Thomas D'Silva (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381477#comment-15381477 ] Thomas D'Silva commented on PHOENIX-3042: - Thanks [~maryannxue]! > Using functional index

[jira] [Updated] (PHOENIX-3042) Using functional index expression in where statement for join query fails.

2016-07-17 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated PHOENIX-3042: - Attachment: PHOENIX-3042-v3.patch Sorry, [~jamestaylor], [~tdsilva], I had misunderstood the

[jira] [Commented] (PHOENIX-3042) Using functional index expression in where statement for join query fails.

2016-07-17 Thread Thomas D'Silva (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381460#comment-15381460 ] Thomas D'Silva commented on PHOENIX-3042: - I didn't modify how aliases are handled in the join

[jira] [Commented] (PHOENIX-3078) Hive storage handler does not work if phoenix.table.name contains the schema name

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

[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=15381257#comment-15381257 ] James Taylor commented on PHOENIX-2900: --- Thanks for the patch and excellent analysis,

[jira] [Commented] (PHOENIX-3078) Hive storage handler does not work if phoenix.table.name contains the schema name

2016-07-17 Thread YoungWoo Kim (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381255#comment-15381255 ] YoungWoo Kim commented on PHOENIX-3078: --- I've tested Phoenix 4.8.0 RC0 with this patch manually

[jira] [Resolved] (PHOENIX-3080) How does phoenix maintenance metadata

2016-07-17 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3080. --- Resolution: Invalid Please ask questions on the mailings lists. > How does phoenix

[jira] [Created] (PHOENIX-3080) How does phoenix maintenance metadata

2016-07-17 Thread longgeligelong (JIRA)
longgeligelong created PHOENIX-3080: --- Summary: How does phoenix maintenance metadata Key: PHOENIX-3080 URL: https://issues.apache.org/jira/browse/PHOENIX-3080 Project: Phoenix Issue Type:

[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-07-17 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2900: -- Attachment: PHOENIX-2900.patch Attaching patch to get test run in. > Once a salted table 's

[jira] [Updated] (PHOENIX-3078) Hive storage handler does not work if phoenix.table.name contains the schema name

2016-07-17 Thread YoungWoo Kim (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YoungWoo Kim updated PHOENIX-3078: -- Attachment: PHOENIX-3078.1.patch Attached a patch for PHOENIX-3078 > Hive storage handler

[jira] [Commented] (PHOENIX-3079) Run point queries serially if the row count is below a configurable threshold

2016-07-17 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381242#comment-15381242 ] James Taylor commented on PHOENIX-3079: --- [~samarthjain] - maybe [~prakul] can do this one? > Run

[jira] [Updated] (PHOENIX-3079) Run point queries serially if the row count is below a configurable threshold

2016-07-17 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3079: -- Fix Version/s: 4.9.0 > Run point queries serially if the row count is below a configurable

[jira] [Created] (PHOENIX-3079) Run point queries serially if the row count is below a configurable threshold

2016-07-17 Thread James Taylor (JIRA)
James Taylor created PHOENIX-3079: - Summary: Run point queries serially if the row count is below a configurable threshold Key: PHOENIX-3079 URL: https://issues.apache.org/jira/browse/PHOENIX-3079

[jira] [Commented] (PHOENIX-3042) Using functional index expression in where statement for join query fails.

2016-07-17 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381237#comment-15381237 ] James Taylor commented on PHOENIX-3042: --- [~maryannxue] - It seems [~tdsilva]'s change didn't break

[jira] [Updated] (PHOENIX-3078) Hive storage handler does not work if phoenix.table.name contains the schema name

2016-07-17 Thread YoungWoo Kim (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YoungWoo Kim updated PHOENIX-3078: -- Summary: Hive storage handler does not work if phoenix.table.name contains the schema name

[jira] [Updated] (PHOENIX-3078) Hive storage handler does not work when phoenix.table.name contains the schema name

2016-07-17 Thread YoungWoo Kim (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YoungWoo Kim updated PHOENIX-3078: -- Summary: Hive storage handler does not work when phoenix.table.name contains the schema name

[jira] [Created] (PHOENIX-3078) Hive storage handler does not work when 'phoenix.table.name' contains the schema name

2016-07-17 Thread YoungWoo Kim (JIRA)
YoungWoo Kim created PHOENIX-3078: - Summary: Hive storage handler does not work when 'phoenix.table.name' contains the schema name Key: PHOENIX-3078 URL: https://issues.apache.org/jira/browse/PHOENIX-3078

[jira] [Resolved] (PHOENIX-3076) Incorrect work of function 'count'

2016-07-17 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3076. --- Resolution: Invalid For Phoenix secondary indexes to be maintained, you need to use Phoenix

[jira] [Commented] (PHOENIX-3070) Unnecessary use of UUID.randomUUID()

2016-07-17 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381230#comment-15381230 ] James Taylor commented on PHOENIX-3070: --- +1. Thanks, [~lhofhansl]! > Unnecessary use of