[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=16390851#comment-16390851 ] Abhishek Singh Chouhan commented on PHOENIX-1267: - Have attached the rebased patch.

[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 ] Abhishek Singh Chouhan updated PHOENIX-1267: Attachment: PHOENIX-1267.master.patch > Set scan.setSmall(true) when

[jira] [Commented] (PHOENIX-4424) Allow users to create "DEFAULT" and "HBASE" Schema (Uppercase Schema Names)

[ https://issues.apache.org/jira/browse/PHOENIX-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390839#comment-16390839 ] Rajeshbabu Chintaguntla commented on PHOENIX-4424: -- [~karanmehta93] Thanks.

[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=16390795#comment-16390795 ] Maryann Xue commented on PHOENIX-4616: -- Thank you very much for the review, [~jamestaylor]! # The

[jira] [Updated] (PHOENIX-4645) PhoenixStorageHandler doesn't handle correctly data/timestamp in push down predicate when engine is tez.

[ https://issues.apache.org/jira/browse/PHOENIX-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-4645: - Attachment: PHOENIX-4645-wip.patch > PhoenixStorageHandler doesn't handle correctly

[jira] [Created] (PHOENIX-4645) PhoenixStorageHandler doesn't handle correctly data/timestamp in push down predicate when engine is tez.

Sergey Soldatov created PHOENIX-4645: Summary: PhoenixStorageHandler doesn't handle correctly data/timestamp in push down predicate when engine is tez. Key: PHOENIX-4645 URL:

[jira] [Comment Edited] (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=16390387#comment-16390387 ] James Taylor edited comment on PHOENIX-4634 at 3/7/18 10:49 PM: Thanks

[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=16390387#comment-16390387 ] James Taylor commented on PHOENIX-4634: --- Thanks for the patch, [~tdsilva]. Do you think it'd be

[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: -- Fix Version/s: 4.14.0 > Looking up a parent index table of a tenant child view fails in >

[jira] [Commented] (PHOENIX-4642) Select from local index in backward direction returns only from last region.

[ https://issues.apache.org/jira/browse/PHOENIX-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390356#comment-16390356 ] James Taylor commented on PHOENIX-4642: --- [~chrajeshbab...@gmail.com] - WDYT? Will this have been

[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=16390289#comment-16390289 ] James Taylor commented on PHOENIX-4148: --- Attached final patch with test and specific error code

[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: -- Attachment: PHOENIX-4148_v2.patch > COUNT(DISTINCT(...)) should have a memory size limit >

[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=16389861#comment-16389861 ] James Taylor commented on PHOENIX-1267: --- +1 on the patch. Nice work, [~abhishek.chouhan]. Would

[jira] [Commented] (PHOENIX-4639) Udf's don't run execute method when using null as a parameter.

[ https://issues.apache.org/jira/browse/PHOENIX-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389807#comment-16389807 ] James Taylor commented on PHOENIX-4639: --- I'm curious why you can't just use the built-in {{IS

[jira] [Resolved] (PHOENIX-4638) string length function returns null for empty string.

[ https://issues.apache.org/jira/browse/PHOENIX-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4638. --- Resolution: Not A Bug Phoenix treats an empty string as null (like Oracle) and the string

[jira] [Updated] (PHOENIX-4638) string length function returns null for empty string.

[ https://issues.apache.org/jira/browse/PHOENIX-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clive Stellings updated PHOENIX-4638: - Description: When you execute length('') at the prompt it returns null when it should

[jira] [Updated] (PHOENIX-4638) string length function returns null for empty string.

[ https://issues.apache.org/jira/browse/PHOENIX-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clive Stellings updated PHOENIX-4638: - Description: When you execute length('') at the prompt it returns null when it should

[jira] [Updated] (PHOENIX-4639) Udf's don't run execute method when using null as a parameter.

[ https://issues.apache.org/jira/browse/PHOENIX-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clive Stellings updated PHOENIX-4639: - Description: When attempting to use a UDF the code for evaluate never runs if the

[jira] [Updated] (PHOENIX-4639) Udf's don't run execute method when using null as a parameter.

[ https://issues.apache.org/jira/browse/PHOENIX-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clive Stellings updated PHOENIX-4639: - Description: When attempting to use a UDF the code for evaluate never runs if the

[jira] [Commented] (PHOENIX-4528) PhoenixAccessController checks permissions only at table level when creating views

[ https://issues.apache.org/jira/browse/PHOENIX-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389584#comment-16389584 ] Ankit Singhal commented on PHOENIX-4528: FYI [~rajeshbabu] , PHOENIX-4198 is now in 5.0 branch

[jira] [Updated] (PHOENIX-4198) Remove the need for users to have access to the Phoenix SYSTEM tables to create tables

[ https://issues.apache.org/jira/browse/PHOENIX-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4198: --- Attachment: PHOENIX-4198_v7_5.x_ported.patch > Remove the need for users to have access to

[jira] [Updated] (PHOENIX-4198) Remove the need for users to have access to the Phoenix SYSTEM tables to create tables

[ https://issues.apache.org/jira/browse/PHOENIX-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4198: --- Fix Version/s: 5.0.0 > Remove the need for users to have access to the Phoenix SYSTEM

[jira] [Commented] (PHOENIX-3506) Phoenix-Spark plug in cannot select by column family name

[ https://issues.apache.org/jira/browse/PHOENIX-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389512#comment-16389512 ] Rene Castberg commented on PHOENIX-3506: I am facing the same issue, i have tried the jdbc