[jira] [Commented] (PHOENIX-4382) Upsert of some big values not correct for immutable tables

[ https://issues.apache.org/jira/browse/PHOENIX-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279515#comment-16279515 ] Thomas D'Silva commented on PHOENIX-4382: - [~vincentpoon]

[jira] [Commented] (PHOENIX-4382) Upsert of some big values not correct for immutable tables

[ https://issues.apache.org/jira/browse/PHOENIX-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279396#comment-16279396 ] Hadoop QA commented on PHOENIX-4382: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-4382) Upsert of some big values not correct for immutable tables

[ https://issues.apache.org/jira/browse/PHOENIX-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-4382: -- Attachment: PHOENIX-4382.v1.master.patch This turned out to be a column encoding bug. The

[jira] [Commented] (PHOENIX-4423) Phoenix-hive compilation broken on >=Hive 2.3

[ https://issues.apache.org/jira/browse/PHOENIX-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279365#comment-16279365 ] Josh Elser commented on PHOENIX-4423: - At first glance, I think that Hive 3 might only work with

Re: keep 2.x branch in sync with master branch?

If it's not too onerous, I think it would be good! The 5.x-HBase-2.0 branch has definitely been stabilized recently (thanks to the great work by Sergey, Ankit, and Rajeshbabu). If it is a pain (e.g. PreCommit broken, Tests broken, other), we can just plan to review it again later. On

[jira] [Commented] (PHOENIX-3050) Handle DESC columns in child/parent join optimization

[ https://issues.apache.org/jira/browse/PHOENIX-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279258#comment-16279258 ] Hadoop QA commented on PHOENIX-3050: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Created] (PHOENIX-4438) IT tests require additional configuration for HBase 2.0

Sergey Soldatov created PHOENIX-4438: Summary: IT tests require additional configuration for HBase 2.0 Key: PHOENIX-4438 URL: https://issues.apache.org/jira/browse/PHOENIX-4438 Project: Phoenix

[jira] [Commented] (PHOENIX-4322) DESC primary key column with variable length does not work in SkipScanFilter

[ https://issues.apache.org/jira/browse/PHOENIX-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279174#comment-16279174 ] Hudson commented on PHOENIX-4322: - FAILURE: Integrated in Jenkins build Phoenix-master #1885 (See

[jira] [Commented] (PHOENIX-4288) Indexes not used when ordering by primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279171#comment-16279171 ] Hudson commented on PHOENIX-4288: - FAILURE: Integrated in Jenkins build Phoenix-master #1884 (See

[jira] [Commented] (PHOENIX-672) Add GRANT and REVOKE commands using HBase AccessController

[ https://issues.apache.org/jira/browse/PHOENIX-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279137#comment-16279137 ] ASF GitHub Bot commented on PHOENIX-672: Github user karanmehta93 closed the pull request at:

[GitHub] phoenix pull request #283: PHOENIX-672 Add GRANT and REVOKE commands using H...

Github user karanmehta93 closed the pull request at: https://github.com/apache/phoenix/pull/283 ---

keep 2.x branch in sync with master branch?

Question for folks working on 2.x branch - would you like those of us committing patches to master to commit them to the 2.x branch as well? If so, probably best to back port as many changes as possible from 2.x back to 1.x. Please advise. Thanks, James

[jira] [Created] (PHOENIX-4437) Make QueryPlan.getEstimatedBytesToScan() independent of getExplainPlan() and pull optimize() out of getExplainPlan()

Maryann Xue created PHOENIX-4437: Summary: Make QueryPlan.getEstimatedBytesToScan() independent of getExplainPlan() and pull optimize() out of getExplainPlan() Key: PHOENIX-4437 URL:

[jira] [Commented] (PHOENIX-4436) Hive PhoenixStorageHandler doesn't work well with quoted namespace/table name.

[ https://issues.apache.org/jira/browse/PHOENIX-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16278430#comment-16278430 ] Hadoop QA commented on PHOENIX-4436: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Resolved] (PHOENIX-4420) org.apache.hive.service.cli.HiveSQLException: java.io.IOException: java.lang.RuntimeException: org.apache.phoenix.exception.PhoenixParserException: ERROR 601 (42P00):

[ https://issues.apache.org/jira/browse/PHOENIX-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov resolved PHOENIX-4420. -- Resolution: Duplicate > org.apache.hive.service.cli.HiveSQLException:

[jira] [Updated] (PHOENIX-4436) Hive PhoenixStorageHandler doesn't work well with quoted namespace/table name.

[ https://issues.apache.org/jira/browse/PHOENIX-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-4436: - Attachment: PHOENIX-4436.patch > Hive PhoenixStorageHandler doesn't work well with

[jira] [Updated] (PHOENIX-4436) Hive PhoenixStorageHandler doesn't work well with quoted namespace/table name.

[ https://issues.apache.org/jira/browse/PHOENIX-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-4436: - Labels: HivePhoenix (was: ) > Hive PhoenixStorageHandler doesn't work well with quoted

[jira] [Created] (PHOENIX-4436) Hive PhoenixStorageHandler doesn't work well with quoted namespace/table name.

Sergey Soldatov created PHOENIX-4436: Summary: Hive PhoenixStorageHandler doesn't work well with quoted namespace/table name. Key: PHOENIX-4436 URL: https://issues.apache.org/jira/browse/PHOENIX-4436