[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471487#comment-16471487 ] Hudson commented on PHOENIX-3163: - ABORTED: Integrated in Jenkins build PreCommit-PHOENI

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471389#comment-16471389 ] Hudson commented on PHOENIX-3163: - ABORTED: Integrated in Jenkins build Phoenix-4.x-HBas

[jira] [Commented] (PHOENIX-4701) Write client-side metrics asynchronously to SYSTEM.LOG

[ https://issues.apache.org/jira/browse/PHOENIX-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471363#comment-16471363 ] James Taylor commented on PHOENIX-4701: --- Nice, [~an...@apache.org]. This is fantas

[jira] [Commented] (PHOENIX-4701) Write client-side metrics asynchronously to SYSTEM.LOG

[ https://issues.apache.org/jira/browse/PHOENIX-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471344#comment-16471344 ] Ankit Singhal commented on PHOENIX-4701: [~jamestaylor], uploaded a wip3, as nee

[jira] [Updated] (PHOENIX-4701) Write client-side metrics asynchronously to SYSTEM.LOG

[ https://issues.apache.org/jira/browse/PHOENIX-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-4701: --- Attachment: PHOENIX-4701_wip3.patch > Write client-side metrics asynchronously to SYSTEM.LOG

[jira] [Commented] (PHOENIX-4701) Write client-side metrics asynchronously to SYSTEM.LOG

[ https://issues.apache.org/jira/browse/PHOENIX-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471325#comment-16471325 ] James Taylor commented on PHOENIX-4701: --- [~an...@apache.org] - I'd love it if this

[jira] [Updated] (PHOENIX-4701) Write client-side metrics asynchronously to SYSTEM.LOG

[ https://issues.apache.org/jira/browse/PHOENIX-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4701: -- Summary: Write client-side metrics asynchronously to SYSTEM.LOG (was: Store client-side metri

[jira] [Updated] (PHOENIX-4701) Store client-side metrics in SYSTEM.LOG

[ https://issues.apache.org/jira/browse/PHOENIX-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4701: -- Description: Rather than inventing a new, different set of client-side metrics to persist, we

[jira] [Updated] (PHOENIX-4701) Store client-side metrics in SYSTEM.LOG

[ https://issues.apache.org/jira/browse/PHOENIX-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4701: -- Summary: Store client-side metrics in SYSTEM.LOG (was: Improve schema of SYSTEM.LOG table) >

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471315#comment-16471315 ] James Taylor commented on PHOENIX-3655: --- For discussion on putting statement level

[jira] [Commented] (PHOENIX-4735) Improve defaults for out of the box configuration

[ https://issues.apache.org/jira/browse/PHOENIX-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471302#comment-16471302 ] Josh Elser commented on PHOENIX-4735: - I like all of the ideas you listed out. Let m

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471298#comment-16471298 ] Hudson commented on PHOENIX-3163: - ABORTED: Integrated in Jenkins build Phoenix-4.x-HBas

[jira] [Commented] (PHOENIX-4734) SQL Query with an RVC expression lexographically higher than all values in an OR clause causes query to blow up

[ https://issues.apache.org/jira/browse/PHOENIX-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471292#comment-16471292 ] James Taylor commented on PHOENIX-4734: --- +1. Nice work, [~tdsilva] & [~jfernando_s

[jira] [Updated] (PHOENIX-4734) SQL Query with an RVC expression lexographically higher than all values in an OR clause causes query to blow up

[ https://issues.apache.org/jira/browse/PHOENIX-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4734: Attachment: PHOENIX-4734.patch > SQL Query with an RVC expression lexographically higher t

[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471276#comment-16471276 ] Hudson commented on PHOENIX-4534: - ABORTED: Integrated in Jenkins build PreCommit-PHOENI

[jira] [Commented] (PHOENIX-4726) save index build timestamp -- for SYNC case only.

[ https://issues.apache.org/jira/browse/PHOENIX-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471250#comment-16471250 ] Xu Cang commented on PHOENIX-4726: -- [~tdsilva] > save index build timestamp -- for SYN

[jira] [Updated] (PHOENIX-4282) PhoenixMRJobSubmitter submits duplicate MR jobs for an index.

[ https://issues.apache.org/jira/browse/PHOENIX-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4282: Fix Version/s: 5.0.0 4.14.0 > PhoenixMRJobSubmitter submits duplicate M

[jira] [Commented] (PHOENIX-4282) PhoenixMRJobSubmitter submits duplicate MR jobs for an index.

[ https://issues.apache.org/jira/browse/PHOENIX-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471233#comment-16471233 ] Thomas D'Silva commented on PHOENIX-4282: - [~xucang] +1, Thanks for the contrib

[jira] [Commented] (PHOENIX-4736) PQS statement and connection metrics handling

[ https://issues.apache.org/jira/browse/PHOENIX-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471232#comment-16471232 ] Karan Mehta commented on PHOENIX-4736: -- Agreed, updated it. > PQS statement and co

[jira] [Updated] (PHOENIX-4736) PQS statement and connection metrics handling

[ https://issues.apache.org/jira/browse/PHOENIX-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-4736: - Summary: PQS statement and connection metrics handling (was: PQS Client side Metrics Handling )

[jira] [Commented] (PHOENIX-4736) PQS Client side Metrics Handling

[ https://issues.apache.org/jira/browse/PHOENIX-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471227#comment-16471227 ] Andrew Purtell commented on PHOENIX-4736: - Maybe the description of this issue i

[jira] [Created] (PHOENIX-4736) PQS Client side Metrics Handling

Karan Mehta created PHOENIX-4736: Summary: PQS Client side Metrics Handling Key: PHOENIX-4736 URL: https://issues.apache.org/jira/browse/PHOENIX-4736 Project: Phoenix Issue Type: Improvement

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471218#comment-16471218 ] Andrew Purtell commented on PHOENIX-3655: - > we can expose them via a servlet ju

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471214#comment-16471214 ] Andrew Purtell commented on PHOENIX-3655: - FWIW internally we brainstormed maybe

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471211#comment-16471211 ] Thomas D'Silva commented on PHOENIX-3655: - I agree it doesn't make sense to expo

[jira] [Commented] (PHOENIX-4735) Improve defaults for out of the box configuration

[ https://issues.apache.org/jira/browse/PHOENIX-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471208#comment-16471208 ] James Taylor commented on PHOENIX-4735: --- Any thoughts, [~elserj] or others? > Imp

[jira] [Created] (PHOENIX-4735) Improve defaults for out of the box configuration

James Taylor created PHOENIX-4735: - Summary: Improve defaults for out of the box configuration Key: PHOENIX-4735 URL: https://issues.apache.org/jira/browse/PHOENIX-4735 Project: Phoenix Issue

[jira] [Commented] (PHOENIX-4728) ARRAY_APPEND and ARRAY_REMOVE should work with null column value

[ https://issues.apache.org/jira/browse/PHOENIX-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471171#comment-16471171 ] Xavier Jodoin commented on PHOENIX-4728: yes next week I'm going to work on a pa

[jira] [Assigned] (PHOENIX-4734) SQL Query with an RVC expression lexographically higher than all values in an OR clause causes query to blow up

[ https://issues.apache.org/jira/browse/PHOENIX-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva reassigned PHOENIX-4734: --- Assignee: Thomas D'Silva > SQL Query with an RVC expression lexographically higher

[jira] [Created] (PHOENIX-4734) SQL Query with an RVC expression lexographically higher than all values in an OR clause causes query to blow up

Jan Fernando created PHOENIX-4734: - Summary: SQL Query with an RVC expression lexographically higher than all values in an OR clause causes query to blow up Key: PHOENIX-4734 URL: https://issues.apache.org/jira/br

[jira] [Updated] (PHOENIX-4734) SQL Query with an RVC expression lexographically higher than all values in an OR clause causes query to blow up

[ https://issues.apache.org/jira/browse/PHOENIX-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-4734: -- Attachment: SqlInClauseIssueIT.java > SQL Query with an RVC expression lexographically higher

[jira] [Commented] (PHOENIX-4725) Hint part in a query does not take into account the "schema" which is passed in the JDBC connection string

[ https://issues.apache.org/jira/browse/PHOENIX-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471122#comment-16471122 ] Shubham commented on PHOENIX-4725: -- Sure, Ankit. > Hint part in a query does not take

[jira] [Commented] (PHOENIX-4725) Hint part in a query does not take into account the "schema" which is passed in the JDBC connection string

[ https://issues.apache.org/jira/browse/PHOENIX-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471117#comment-16471117 ] Ankit Singhal commented on PHOENIX-4725: Assigned, Thanks for showing interest [

[jira] [Assigned] (PHOENIX-4725) Hint part in a query does not take into account the "schema" which is passed in the JDBC connection string

[ https://issues.apache.org/jira/browse/PHOENIX-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-4725: -- Assignee: Shubham > Hint part in a query does not take into account the "schema" whic

[jira] [Commented] (PHOENIX-4725) Hint part in a query does not take into account the "schema" which is passed in the JDBC connection string

[ https://issues.apache.org/jira/browse/PHOENIX-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471106#comment-16471106 ] Shubham commented on PHOENIX-4725: -- I would like to work on this jira, [~an...@apache.o

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471082#comment-16471082 ] Karan Mehta commented on PHOENIX-3655: -- Got some deeper insight today into what can

[jira] [Updated] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3163: -- Fix Version/s: 5.0.0 > Split during global index creation may cause ERROR 201 error >

[jira] [Updated] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3163: -- Fix Version/s: (was: 4.15.0) 4.14.0 > Split during global index creatio

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471003#comment-16471003 ] Sergey Soldatov commented on PHOENIX-3163: -- LGTM +1 > Split during global inde

[jira] [Updated] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3163: -- Summary: Split during global index creation may cause ERROR 201 error (was: Split during glob

[jira] [Comment Edited] (PHOENIX-4728) ARRAY_APPEND and ARRAY_REMOVE should work with null column value

[ https://issues.apache.org/jira/browse/PHOENIX-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470992#comment-16470992 ] James Taylor edited comment on PHOENIX-4728 at 5/10/18 7:27 PM: --

[jira] [Commented] (PHOENIX-4728) ARRAY_APPEND and ARRAY_REMOVE should work with null column value

[ https://issues.apache.org/jira/browse/PHOENIX-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470992#comment-16470992 ] James Taylor commented on PHOENIX-4728: --- [~xjodoin] - I can see your point with AR

[jira] [Commented] (PHOENIX-4685) Properly handle connection caching for Phoenix inside RegionServers

[ https://issues.apache.org/jira/browse/PHOENIX-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470990#comment-16470990 ] Rajeshbabu Chintaguntla commented on PHOENIX-4685: -- [~jamestaylor] Than

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error.

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470974#comment-16470974 ] James Taylor commented on PHOENIX-3163: --- Attached slightly revised patch. No need

[jira] [Updated] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error.

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3163: -- Attachment: PHOENIX-3163_v6.patch > Split during global index creation may cause ERROR 201 err

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error.

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470950#comment-16470950 ] James Taylor commented on PHOENIX-3163: --- Verified all unit tests pass (without PHO

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error.

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470812#comment-16470812 ] James Taylor commented on PHOENIX-3163: --- [~sergey.soldatov] - I'd like to get this

[jira] [Updated] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error.

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3163: -- Attachment: PHOENIX-3163_v5.patch > Split during global index creation may cause ERROR 201 err

[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470796#comment-16470796 ] Sergey Soldatov commented on PHOENIX-4534: -- [~jamestaylor] That's 1.4/2.0 HBase

[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470762#comment-16470762 ] James Taylor commented on PHOENIX-4534: --- Thanks, [~sergey.soldatov]! Is it require

[jira] [Commented] (PHOENIX-3534) Support multi region SYSTEM.CATALOG table

[ https://issues.apache.org/jira/browse/PHOENIX-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470759#comment-16470759 ] James Taylor commented on PHOENIX-3534: --- For mutable properties, can we use the ti

[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470757#comment-16470757 ] Sergey Soldatov commented on PHOENIX-4534: -- [~jamestaylor] cherry-picked to mas

[jira] [Commented] (PHOENIX-4666) Add a subquery cache that persists beyond the life of a query

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

[GitHub] phoenix pull request #298: PHOENIX-4666 Persistent subquery cache for hash j...

Github user JamesRTaylor commented on a diff in the pull request: https://github.com/apache/phoenix/pull/298#discussion_r187393698 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/cache/ServerCacheClient.java --- @@ -216,22 +234,146 @@ public void close() throws SQLException

[jira] [Commented] (PHOENIX-4534) upsert/delete/upsert for the same row corrupts the indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470696#comment-16470696 ] James Taylor commented on PHOENIX-4534: --- Was this committed, [~sergey.soldatov]? I

[jira] [Resolved] (PHOENIX-4589) Split up OrderByIT into multiple tests

[ https://issues.apache.org/jira/browse/PHOENIX-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4589. --- Resolution: Not A Problem The number of tests in OrderByIT is small enough already, so no ne

[jira] [Comment Edited] (PHOENIX-4685) Properly handle connection caching for Phoenix inside RegionServers

[ https://issues.apache.org/jira/browse/PHOENIX-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470621#comment-16470621 ] James Taylor edited comment on PHOENIX-4685 at 5/10/18 4:17 PM: --

[jira] [Commented] (PHOENIX-4685) Properly handle connection caching for Phoenix inside RegionServers

[ https://issues.apache.org/jira/browse/PHOENIX-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470621#comment-16470621 ] James Taylor commented on PHOENIX-4685: --- [~rajeshbabu] - your fix introduced a bun

[jira] [Commented] (PHOENIX-4646) The data exceeds the max capacity for the data type error for valid scenarios.

[ https://issues.apache.org/jira/browse/PHOENIX-4646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1646#comment-1646 ] Hudson commented on PHOENIX-4646: - ABORTED: Integrated in Jenkins build Phoenix-4.x-HBas

[jira] [Commented] (PHOENIX-4678) IndexScrutinyTool generates malformed query due to incorrect table name(s)

[ https://issues.apache.org/jira/browse/PHOENIX-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469998#comment-16469998 ] Hudson commented on PHOENIX-4678: - ABORTED: Integrated in Jenkins build Phoenix-4.x-HBas

[jira] [Commented] (PHOENIX-4733) NPE while running sql through file using psql

[ https://issues.apache.org/jira/browse/PHOENIX-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1647#comment-1647 ] Hudson commented on PHOENIX-4733: - ABORTED: Integrated in Jenkins build Phoenix-4.x-HBas