[jira] [Comment Edited] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817308#comment-15817308 ] Lars Hofhansl edited comment on PHOENIX-3560 at 1/11/17 6:03 AM: -

[jira] [Comment Edited] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814497#comment-15814497 ] Lars Hofhansl edited comment on PHOENIX-3560 at 1/11/17 6:03 AM: -

[jira] [Comment Edited] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15806107#comment-15806107 ] Lars Hofhansl edited comment on PHOENIX-3560 at 1/11/17 6:03 AM: -

[jira] [Commented] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817308#comment-15817308 ] Lars Hofhansl commented on PHOENIX-3560: The FirstKeyOnlyFilter would still work

[jira] [Updated] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Thomas D'Silva (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3560: Assignee: Samarth Jain (was: Thomas D'Silva) > Aggregate query performance is worse with

[jira] [Commented] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816963#comment-15816963 ] Hudson commented on PHOENIX-3584: - SUCCESS: Integrated in Jenkins build Phoenix-master #

[jira] [Commented] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Samarth Jain (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816912#comment-15816912 ] Samarth Jain commented on PHOENIX-3560: --- [~mujtabachohan], it would be interesting

[jira] [Commented] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Samarth Jain (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816914#comment-15816914 ] Samarth Jain commented on PHOENIX-3560: --- [~mujtabachohan], it would be interesting

[jira] [Commented] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Samarth Jain (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816901#comment-15816901 ] Samarth Jain commented on PHOENIX-3560: --- We use a SINGLE_KEYVALUE_COLUMN_QUALIFIER

[jira] [Resolved] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread Samarth Jain (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-3584. --- Resolution: Fixed Fix Version/s: 4.10.0 4.9.1 > Expose metrics for

[jira] [Commented] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

2017-01-10 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816786#comment-15816786 ] Maryann Xue commented on PHOENIX-3579: -- Thank you, [~kliew], for the update! You ca

[jira] [Commented] (PHOENIX-3555) Building async local index by IndexTool generate wrong data

2017-01-10 Thread chenzhiming (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816756#comment-15816756 ] chenzhiming commented on PHOENIX-3555: -- Thanks,get it! > Building async local inde

[jira] [Resolved] (PHOENIX-3581) Class-cast exceptions caused by TestUtil.getSplits() and TestUtil.getGuidePostsList()

2017-01-10 Thread Maryann Xue (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-3581. -- Resolution: Fixed > Class-cast exceptions caused by TestUtil.getSplits() and > TestUtil.getGu

[jira] [Updated] (PHOENIX-3519) Add COLUMN_ENCODED_BYTES table property

2017-01-10 Thread Thomas D'Silva (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3519: Summary: Add COLUMN_ENCODED_BYTES table property (was: Specify QualifierEncodingScheme in

[jira] [Assigned] (PHOENIX-3586) Add StorageScheme table property to allow users to specify their custom storage schemes

2017-01-10 Thread Thomas D'Silva (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva reassigned PHOENIX-3586: --- Assignee: Thomas D'Silva > Add StorageScheme table property to allow users to speci

[jira] [Updated] (PHOENIX-3519) Specify QualifierEncodingScheme in CREATE TABLE statement

2017-01-10 Thread Thomas D'Silva (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3519: Attachment: PHOENIX-3519.patch [~jamestaylor] Can you please review? I had to make the fo

[jira] [Commented] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816520#comment-15816520 ] James Taylor commented on PHOENIX-3584: --- +1. Looks good, [~samarthjain]. > Expose

[jira] [Updated] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread Samarth Jain (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3584: -- Attachment: PHOENIX-3584.patch Patch that adds two new global metrics for HConnections and Co

[jira] [Updated] (PHOENIX-3586) Add StorageScheme table property to allow users to specify their custom storage schemes

2017-01-10 Thread Thomas D'Silva (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3586: Issue Type: Sub-task (was: Task) Parent: PHOENIX-2565 > Add StorageScheme table p

[jira] [Created] (PHOENIX-3586) Add StorageScheme table property to allow users to specify their custom storage schemes

2017-01-10 Thread Thomas D'Silva (JIRA)
Thomas D'Silva created PHOENIX-3586: --- Summary: Add StorageScheme table property to allow users to specify their custom storage schemes Key: PHOENIX-3586 URL: https://issues.apache.org/jira/browse/PHOENIX-3586

[jira] [Created] (PHOENIX-3585) MutableIndexIT testSplitDuringIndexScan and testIndexHalfStoreFileReader fail for transactional tables and local indexes

2017-01-10 Thread Thomas D'Silva (JIRA)
Thomas D'Silva created PHOENIX-3585: --- Summary: MutableIndexIT testSplitDuringIndexScan and testIndexHalfStoreFileReader fail for transactional tables and local indexes Key: PHOENIX-3585 URL: https://issues.apach

Phoenix Tuning Guide

2017-01-10 Thread Peter Conrad
The Phoenix Tuning Guide has been through several reviews and revisions. The latest version is attached to PHOENIX-3218: https://issues.apache.org/jira/browse/PHOENIX-3218 Please take a look and comment with any final feedback. Thanks, Peter Peter Conrad Lead Technical Writer: Infrastructu

[jira] [Updated] (PHOENIX-3218) First draft of Phoenix Tuning Guide

2017-01-10 Thread Peter Conrad (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Conrad updated PHOENIX-3218: -- Attachment: Phoenix-Tuning-Guide-20170110.md Made significant format edits, cleaned up a few

[jira] [Commented] (PHOENIX-3572) Support FETCH NEXT| n ROWS from Cursor

2017-01-10 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816002#comment-15816002 ] ASF GitHub Bot commented on PHOENIX-3572: - GitHub user bijugs opened a pull requ

[GitHub] phoenix pull request #229: PHOENIX-3572 Support FETCH NEXT|n ROWS query on c...

2017-01-10 Thread bijugs
GitHub user bijugs opened a pull request: https://github.com/apache/phoenix/pull/229 PHOENIX-3572 Support FETCH NEXT|n ROWS query on cursor Refer PR #192 for earlier discussion on cursor implementation. As mentioned in the title, this PR implements a sub set of ``cursor`` feature ta

[jira] [Comment Edited] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread Andrew Purtell (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815937#comment-15815937 ] Andrew Purtell edited comment on PHOENIX-3584 at 1/10/17 7:35 PM:

[jira] [Comment Edited] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread Andrew Purtell (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815942#comment-15815942 ] Andrew Purtell edited comment on PHOENIX-3584 at 1/10/17 7:33 PM:

[jira] [Commented] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread Andrew Purtell (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815942#comment-15815942 ] Andrew Purtell commented on PHOENIX-3584: - Personally I think we need to track a

[jira] [Commented] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread Andrew Purtell (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815937#comment-15815937 ] Andrew Purtell commented on PHOENIX-3584: - [~lhofhansl] points out we also need

Re: Optimisation for times series

2017-01-10 Thread James Taylor
Nicolas, FYI, the description provided by Thomas is how we support Argus[1] on top of Phoenix. This Phoenix-based time series implementation will be open sourced soon in Argus. In our performance measurements[2], we've found Phoenix to be on par or faster than OpenTSDB with approximately the same a

[jira] [Commented] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread Samarth Jain (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815802#comment-15815802 ] Samarth Jain commented on PHOENIX-3584: --- On it. > Expose metrics for ConnectionQu

Re: Optimisation for times series

2017-01-10 Thread Thomas D'Silva
Nicolas, If you want to implement the OpenTSDB datamodel you can define a base table and define views for each metric. For example the base table DDL could be CREATE SEQUENCE metric_id_seq CACHE 100 CREATE TABLE metric_table ( metricid INTEGER NOT NULL, eventTime TIMESTAMP NOT NULL

[jira] [Commented] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815634#comment-15815634 ] James Taylor commented on PHOENIX-3584: --- [~samarthjain] - we're seeing many zookee

[jira] [Updated] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread James Taylor (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3584: -- Assignee: Samarth Jain > Expose metrics for ConnectionQueryServices instances and their alloca

[jira] [Created] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

2017-01-10 Thread Andrew Purtell (JIRA)
Andrew Purtell created PHOENIX-3584: --- Summary: Expose metrics for ConnectionQueryServices instances and their allocators in the JVM Key: PHOENIX-3584 URL: https://issues.apache.org/jira/browse/PHOENIX-3584

Re: Why SkipScanFilter can not support OrderBy.REV_ROW_KEY_ORDER_BY?

2017-01-10 Thread James Taylor
Because no one has implemented it. It would be a welcome addition and probably not too difficult. Thanks, James On Tue, Jan 10, 2017 at 7:00 AM 程磊 wrote: > Hi,when I read the following code in OrderBy.complie method, in line > 160,it seems that SkipScanFilter can not support > OrderBy.REV_ROW_K

[jira] [Commented] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

2017-01-10 Thread Rajeshbabu Chintaguntla (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815332#comment-15815332 ] Rajeshbabu Chintaguntla commented on PHOENIX-3579: -- As part of PHOENIX-

[jira] [Commented] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

2017-01-10 Thread Kevin Liew (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815317#comment-15815317 ] Kevin Liew commented on PHOENIX-3579: - Hi [~maryannxue], the test cases did fail on

Why SkipScanFilter can not support OrderBy.REV_ROW_KEY_ORDER_BY?

2017-01-10 Thread 程磊
Hi,when I read the following code in OrderBy.complie method, in line 160,it seems that SkipScanFilter can not support OrderBy.REV_ROW_KEY_ORDER_BY, SkipScanFilter still could not support OrderBy.REV_ROW_KEY_ORDER_BY now? and why? : 155 if (isInRowKeyOrder && tracker.isOrderPreserving()) {

[jira] [Commented] (PHOENIX-3555) Building async local index by IndexTool generate wrong data

2017-01-10 Thread Josh Elser (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815040#comment-15815040 ] Josh Elser commented on PHOENIX-3555: - No worries! Just doing some cleanup :) >

[jira] [Commented] (PHOENIX-3214) Kafka Phoenix Consumer

2017-01-10 Thread Josh Mahonin (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814968#comment-15814968 ] Josh Mahonin commented on PHOENIX-3214: --- Hi [~kalyanhadoop] this is definitely on

[jira] [Updated] (PHOENIX-3523) Secondary index on case sensitive table breaks all queries

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3523: --- Attachment: PHOENIX-3523_wip.patch parking a wip patch here .. it fixes the above issue. But

[jira] [Assigned] (PHOENIX-3523) Secondary index on case sensitive table breaks all queries

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3523: -- Assignee: Ankit Singhal > Secondary index on case sensitive table breaks all queries

[jira] [Updated] (PHOENIX-3572) Support FETCH NEXT| n ROWS from Cursor

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3572: --- Assignee: Biju Nair > Support FETCH NEXT| n ROWS from Cursor > -

[jira] [Commented] (PHOENIX-3572) Support FETCH NEXT| n ROWS from Cursor

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814812#comment-15814812 ] Ankit Singhal commented on PHOENIX-3572: I have already reviewed it offline, [~j

[jira] [Commented] (PHOENIX-3112) Partial row scan not handled correctly

2017-01-10 Thread Venkata Mohan (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814579#comment-15814579 ] Venkata Mohan commented on PHOENIX-3112: I am also encountering the same issue.

[jira] [Commented] (PHOENIX-3582) No significant space saving with immutable encoded column with large number of dense columns

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814561#comment-15814561 ] Ankit Singhal commented on PHOENIX-3582: For test #1, It could be possible if va

[jira] [Commented] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

2017-01-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814517#comment-15814517 ] Hadoop QA commented on PHOENIX-3271: {color:red}-1 overall{color}. Here are the res

[jira] [Issue Comment Deleted] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3560: --- Comment: was deleted (was: I think , if we set this to _1(greater than _0 EMPTY_COLUMN_NAME)

[jira] [Commented] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814497#comment-15814497 ] Ankit Singhal commented on PHOENIX-3560: I think , if we set this to _1(greater

[jira] [Commented] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814499#comment-15814499 ] Ankit Singhal commented on PHOENIX-3560: I think , if we set this to _1(greater

[jira] [Updated] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3271: --- Attachment: (was: PHOENIX-3271_v3.patch) > Distribute UPSERT SELECT across cluster > ---

[jira] [Updated] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

2017-01-10 Thread Ankit Singhal (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3271: --- Attachment: PHOENIX-3271_v3.patch > Distribute UPSERT SELECT across cluster > --

[jira] [Commented] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

2017-01-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814313#comment-15814313 ] Hadoop QA commented on PHOENIX-3271: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

2017-01-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814278#comment-15814278 ] Hadoop QA commented on PHOENIX-3271: {color:red}-1 overall{color}. Here are the res