[jira] [Comment Edited] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394062#comment-16394062 ] Ihor Krysenko edited comment on PHOENIX-4553 at 3/10/18 6:25 AM: -

[jira] [Commented] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394062#comment-16394062 ] Ihor Krysenko commented on PHOENIX-4553: [~pboado] I can check only in Monday, btw, I see, it

[jira] [Commented] (PHOENIX-4418) UPPER() and LOWER() functions should be locale-aware

[ https://issues.apache.org/jira/browse/PHOENIX-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394059#comment-16394059 ] Shehzaad Nakhoda commented on PHOENIX-4418: --- [~tdsilva] I've rebased the patch

[jira] [Updated] (PHOENIX-4418) UPPER() and LOWER() functions should be locale-aware

[ https://issues.apache.org/jira/browse/PHOENIX-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shehzaad Nakhoda updated PHOENIX-4418: -- Attachment: PHOENIX-4418_v3.patch > UPPER() and LOWER() functions should be

[jira] [Commented] (PHOENIX-4643) Implement ARRAY_REMOVE built in function

[ https://issues.apache.org/jira/browse/PHOENIX-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394040#comment-16394040 ] ASF GitHub Bot commented on PHOENIX-4643: - Github user JamesRTaylor commented on the issue:

[GitHub] phoenix issue #294: PHOENIX-4643 Implement ARRAY_REMOVE built in function

Github user JamesRTaylor commented on the issue: https://github.com/apache/phoenix/pull/294 Changes look good. I've committed PHOENIX-4644, so can you make sure everything works without specify a default value for the second argument for ARRAY_REMOVE? ---

[GitHub] phoenix pull request #294: PHOENIX-4643 Implement ARRAY_REMOVE built in func...

Github user JamesRTaylor commented on a diff in the pull request: https://github.com/apache/phoenix/pull/294#discussion_r173612840 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/expression/function/ArrayRemoveFunction.java --- @@ -0,0 +1,79 @@ +/* + * Licensed to

[jira] [Commented] (PHOENIX-4643) Implement ARRAY_REMOVE built in function

[ https://issues.apache.org/jira/browse/PHOENIX-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394039#comment-16394039 ] ASF GitHub Bot commented on PHOENIX-4643: - Github user JamesRTaylor commented on a diff in the

Re: Expanding Phoenix support to additional versions of CDH

If you're willing to sign up to keep the CDH branches in sync with the 4.x-HBase-1.2 branches, then that seems fine. Should we look into some kind of automation for syncing all the branches? Another approach is a shim layer, but we've been reluctant to set that up as there's a fair amount of

[jira] [Updated] (PHOENIX-4139) Incorrect query result for trailing duplicate GROUP BY expression

[ https://issues.apache.org/jira/browse/PHOENIX-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4139: -- Summary: Incorrect query result for trailing duplicate GROUP BY expression (was: select

[jira] [Resolved] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Boado resolved PHOENIX-4553. -- Resolution: Fixed Solved in commit #0aba3a9a > HBase Master could not start with activated

[jira] [Updated] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Boado updated PHOENIX-4553: - Attachment: PHOENIX-4553-00.patch > HBase Master could not start with activated APACHE_PHOENIX

[jira] [Commented] (PHOENIX-1267) Set scan.setSmall(true) when appropriate

[ https://issues.apache.org/jira/browse/PHOENIX-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393897#comment-16393897 ] Hudson commented on PHOENIX-1267: - SUCCESS: Integrated in Jenkins build PreCommit-PHOENIX-Build #1797

[jira] [Commented] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit

[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393896#comment-16393896 ] Hudson commented on PHOENIX-4148: - SUCCESS: Integrated in Jenkins build PreCommit-PHOENIX-Build #1797

[jira] [Commented] (PHOENIX-4644) Array modification functions should require two arguments

[ https://issues.apache.org/jira/browse/PHOENIX-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393898#comment-16393898 ] Hudson commented on PHOENIX-4644: - SUCCESS: Integrated in Jenkins build PreCommit-PHOENIX-Build #1797

[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

[ https://issues.apache.org/jira/browse/PHOENIX-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393895#comment-16393895 ] Hudson commented on PHOENIX-4640: - SUCCESS: Integrated in Jenkins build PreCommit-PHOENIX-Build #1797

[jira] [Commented] (PHOENIX-4644) Array modification functions should require two arguments

[ https://issues.apache.org/jira/browse/PHOENIX-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393886#comment-16393886 ] Hudson commented on PHOENIX-4644: - FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #55 (See

[jira] [Commented] (PHOENIX-1267) Set scan.setSmall(true) when appropriate

[ https://issues.apache.org/jira/browse/PHOENIX-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393885#comment-16393885 ] Hudson commented on PHOENIX-1267: - FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #55 (See

[jira] [Commented] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit

[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393884#comment-16393884 ] Hudson commented on PHOENIX-4148: - FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #55 (See

[jira] [Comment Edited] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393874#comment-16393874 ] Pedro Boado edited comment on PHOENIX-4553 at 3/10/18 12:43 AM:

[jira] [Comment Edited] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393874#comment-16393874 ] Pedro Boado edited comment on PHOENIX-4553 at 3/10/18 12:42 AM:

[jira] [Commented] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393874#comment-16393874 ] Pedro Boado commented on PHOENIX-4553: -- [~neospyk] I've come across this issue again and noticed

[jira] [Assigned] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Boado reassigned PHOENIX-4553: Assignee: Pedro Boado > HBase Master could not start with activated APACHE_PHOENIX

[jira] [Resolved] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

[ https://issues.apache.org/jira/browse/PHOENIX-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4640. --- Resolution: Fixed > Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

[jira] [Updated] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit

[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4148: -- Fix Version/s: 5.0.0 > COUNT(DISTINCT(...)) should have a memory size limit >

[jira] [Resolved] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit

[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4148. --- Resolution: Fixed > COUNT(DISTINCT(...)) should have a memory size limit >

[jira] [Updated] (PHOENIX-1267) Set scan.setSmall(true) when appropriate

[ https://issues.apache.org/jira/browse/PHOENIX-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1267: -- Fix Version/s: 5.0.0 > Set scan.setSmall(true) when appropriate >

[jira] [Updated] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

[ https://issues.apache.org/jira/browse/PHOENIX-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4640: -- Fix Version/s: 5.0.0 > Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side

[jira] [Updated] (PHOENIX-4644) Array modification functions should require two arguments

[ https://issues.apache.org/jira/browse/PHOENIX-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4644: -- Fix Version/s: 5.0.0 > Array modification functions should require two arguments >

[jira] [Commented] (PHOENIX-1556) Base hash versus sort merge join decision on cost

[ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393819#comment-16393819 ] James Taylor commented on PHOENIX-1556: --- Looks like this wasn't committed to some of the active

[jira] [Commented] (PHOENIX-4585) Prune local index regions used for join queries

[ https://issues.apache.org/jira/browse/PHOENIX-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393817#comment-16393817 ] James Taylor commented on PHOENIX-4585: --- Looks like this wasn't committed to some of the active

[jira] [Commented] (PHOENIX-4611) Not nullable column impact on join query plans

[ https://issues.apache.org/jira/browse/PHOENIX-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393813#comment-16393813 ] James Taylor commented on PHOENIX-4611: --- Looks like this wasn't committed to some of the active

[jira] [Commented] (PHOENIX-4616) Move join query optimization out from QueryCompiler into QueryOptimizer

[ https://issues.apache.org/jira/browse/PHOENIX-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393747#comment-16393747 ] James Taylor commented on PHOENIX-4616: --- bq. I thought it would be better to keep the optimization

[jira] [Commented] (PHOENIX-4644) Array modification functions should require two arguments

[ https://issues.apache.org/jira/browse/PHOENIX-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393732#comment-16393732 ] James Taylor commented on PHOENIX-4644: --- Thanks for the review, [~tdsilva]. I attached a v2 patch

[jira] [Updated] (PHOENIX-4644) Array modification functions should require two arguments

[ https://issues.apache.org/jira/browse/PHOENIX-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4644: -- Attachment: PHOENIX-4644_v2.patch > Array modification functions should require two arguments

[jira] [Assigned] (PHOENIX-4648) Allow Add jar "path" support hdfs

[ https://issues.apache.org/jira/browse/PHOENIX-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni reassigned PHOENIX-4648: - Assignee: Chinmay Kulkarni > Allow Add jar "path" support hdfs >

[jira] [Created] (PHOENIX-4648) Allow Add jar "path" support hdfs

Ethan Wang created PHOENIX-4648: --- Summary: Allow Add jar "path" support hdfs Key: PHOENIX-4648 URL: https://issues.apache.org/jira/browse/PHOENIX-4648 Project: Phoenix Issue Type: New Feature

[jira] [Commented] (PHOENIX-4648) Allow Add jar "path" support hdfs

[ https://issues.apache.org/jira/browse/PHOENIX-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393527#comment-16393527 ] Ethan Wang commented on PHOENIX-4648: - [~ckulkarni] [~chrajeshbab...@gmail.com] > Allow Add jar

[jira] [Commented] (PHOENIX-4231) Support restriction of remote UDF load sources

[ https://issues.apache.org/jira/browse/PHOENIX-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393524#comment-16393524 ] Ethan Wang commented on PHOENIX-4231: - [~ckulkarni] thanks. done with Phoenix-4231-v2.patch. >

[jira] [Updated] (PHOENIX-4231) Support restriction of remote UDF load sources

[ https://issues.apache.org/jira/browse/PHOENIX-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Wang updated PHOENIX-4231: Attachment: PHOENIX-4231-v2.patch > Support restriction of remote UDF load sources >

[jira] [Commented] (PHOENIX-4231) Support restriction of remote UDF load sources

[ https://issues.apache.org/jira/browse/PHOENIX-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393489#comment-16393489 ] Chinmay Kulkarni commented on PHOENIX-4231: --- [~aertoria] please remove unnecessary changes to

[jira] [Commented] (PHOENIX-4231) Support restriction of remote UDF load sources

[ https://issues.apache.org/jira/browse/PHOENIX-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393477#comment-16393477 ] Ethan Wang commented on PHOENIX-4231: - Thanks [~apurtell] > Support restriction of remote UDF load

[jira] [Commented] (PHOENIX-4231) Support restriction of remote UDF load sources

[ https://issues.apache.org/jira/browse/PHOENIX-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393458#comment-16393458 ] Andrew Purtell commented on PHOENIX-4231: - +1 Any concerns about commit? If not I will do so

[jira] [Commented] (PHOENIX-4634) Looking up a parent index table of a tenant child view fails in BaseColumnResolver createTableRef()

[ https://issues.apache.org/jira/browse/PHOENIX-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393285#comment-16393285 ] James Taylor commented on PHOENIX-4634: --- bq. I didn't reset it at the start of updataCache,

[jira] [Commented] (PHOENIX-4634) Looking up a parent index table of a tenant child view fails in BaseColumnResolver createTableRef()

[ https://issues.apache.org/jira/browse/PHOENIX-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393238#comment-16393238 ] Thomas D'Silva commented on PHOENIX-4634: - [~jamestaylor] Thanks for the review. I didn't reset

Re: [VOTE] Include python-phoenixdb into Phoenix

+1 On March 9, 2018 at 4:42:50 AM, rajeshb...@apache.org (chrajeshbab...@gmail.com) wrote: +1 On Thu, Mar 8, 2018 at 9:36 PM, Josh Elser wrote: > +1 > > > On 3/8/18 7:02 AM, Ankit Singhal wrote: > >> Lukas Lalinsky has graciously agreed to contribute his work on

[jira] [Updated] (PHOENIX-4634) Looking up a parent index table of a tenant child view fails in BaseColumnResolver createTableRef()

[ https://issues.apache.org/jira/browse/PHOENIX-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4634: -- Attachment: PHOENIX-4634-v4.patch > Looking up a parent index table of a tenant child view

[jira] [Commented] (PHOENIX-4634) Looking up a parent index table of a tenant child view fails in BaseColumnResolver createTableRef()

[ https://issues.apache.org/jira/browse/PHOENIX-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393164#comment-16393164 ] James Taylor commented on PHOENIX-4634: --- Thanks for the revised patch, [~tdsilva]. Couple of

[jira] [Commented] (PHOENIX-4579) Add a config to conditionally create Phoenix meta tables on first client connection

[ https://issues.apache.org/jira/browse/PHOENIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393088#comment-16393088 ] James Taylor commented on PHOENIX-4579: --- Can I assign this one to you, [~tdsilva] as it doesn't

Re: [VOTE] Include python-phoenixdb into Phoenix

+1 On Thu, Mar 8, 2018 at 9:36 PM, Josh Elser wrote: > +1 > > > On 3/8/18 7:02 AM, Ankit Singhal wrote: > >> Lukas Lalinsky has graciously agreed to contribute his work on python >> library for accessing Phoenix to Apache Phoenix project. >> >> >> The details of the project

[jira] [Updated] (PHOENIX-4647) Column header doesn't handle optional arguments correctly

[ https://issues.apache.org/jira/browse/PHOENIX-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shehzaad Nakhoda updated PHOENIX-4647: -- Description: SUBSTR(NAME, 1) being rendered as SUBSTR(NAME, 1, ) in things like

[jira] [Commented] (PHOENIX-4418) UPPER() and LOWER() functions should be locale-aware

[ https://issues.apache.org/jira/browse/PHOENIX-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392673#comment-16392673 ] Shehzaad Nakhoda commented on PHOENIX-4418: --- [~tdsilva] thanks. I've attached a patch file

[jira] [Updated] (PHOENIX-4418) UPPER() and LOWER() functions should be locale-aware

[ https://issues.apache.org/jira/browse/PHOENIX-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shehzaad Nakhoda updated PHOENIX-4418: -- Attachment: upper_lower_locale_doc.patch > UPPER() and LOWER() functions should be

[jira] [Commented] (PHOENIX-4647) Column header doesn't handle optional arguments correctly

[ https://issues.apache.org/jira/browse/PHOENIX-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392580#comment-16392580 ] Shehzaad Nakhoda commented on PHOENIX-4647: --- [~jamestaylor] - the jira you requested. >

[jira] [Created] (PHOENIX-4647) Column header doesn't handle optional arguments correctly

Shehzaad Nakhoda created PHOENIX-4647: - Summary: Column header doesn't handle optional arguments correctly Key: PHOENIX-4647 URL: https://issues.apache.org/jira/browse/PHOENIX-4647 Project: