[jira] [Updated] (PHOENIX-4900) Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED exception message to recommend turning autocommit off for deletes

[ https://issues.apache.org/jira/browse/PHOENIX-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-4900: --- Attachment: PHOENIX-4900-4.x-HBase-1.4.patch > Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_S

[jira] [Resolved] (PHOENIX-5063) Create a new repo for the phoenix query server

[ https://issues.apache.org/jira/browse/PHOENIX-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta resolved PHOENIX-5063. -- Resolution: Fixed Thanks [~tdsilva] and [~elserj] for the review. Your inputs were really hel

[jira] [Created] (PHOENIX-5177) Update PQS documentation for PhoenixCanaryTool

Swaroopa Kadam created PHOENIX-5177: --- Summary: Update PQS documentation for PhoenixCanaryTool Key: PHOENIX-5177 URL: https://issues.apache.org/jira/browse/PHOENIX-5177 Project: Phoenix Issu

[jira] [Updated] (PHOENIX-5172) Harden queryserver canary tool with retries and effective logging

[ https://issues.apache.org/jira/browse/PHOENIX-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-5172: Fix Version/s: 4.15.0 > Harden queryserver canary tool with retries and effective logging

[jira] [Updated] (PHOENIX-4900) Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED exception message to recommend turning autocommit off for deletes

[ https://issues.apache.org/jira/browse/PHOENIX-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-4900: --- Attachment: (was: PHOENIX-4900.patch) > Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE

[jira] [Updated] (PHOENIX-4900) Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED exception message to recommend turning autocommit off for deletes

[ https://issues.apache.org/jira/browse/PHOENIX-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-4900: --- Attachment: PHOENIX-4900.patch > Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCE

[jira] [Updated] (PHOENIX-4900) Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED exception message to recommend turning autocommit off for deletes

[ https://issues.apache.org/jira/browse/PHOENIX-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-4900: --- Attachment: (was: PHOENIX-4900.patch) > Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE

[jira] [Updated] (PHOENIX-5176) KeyRange.compareUpperRange(KeyRang 1, KeyRang 2) returns wrong result when two key ranges have the same upper bound values but one is inclusive and another is exclusive

[ https://issues.apache.org/jira/browse/PHOENIX-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5176: Priority: Blocker (was: Major) > KeyRange.compareUpperRange(KeyRang 1, KeyRang 2) return

[jira] [Updated] (PHOENIX-5176) KeyRange.compareUpperRange(KeyRang 1, KeyRang 2) returns wrong result when two key ranges have the same upper bound values but one is inclusive and another is exclusive

[ https://issues.apache.org/jira/browse/PHOENIX-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bin Shi updated PHOENIX-5176: - Fix Version/s: (was: 4.14.2) (was: 5.1.0) > KeyRange.compareUpperRange(KeyRa

[jira] [Created] (PHOENIX-5176) KeyRange.compareUpperRange(KeyRang 1, KeyRang 2) returns wrong result when two key ranges have the same upper bound values but one is inclusive and another is exclusive

Bin Shi created PHOENIX-5176: Summary: KeyRange.compareUpperRange(KeyRang 1, KeyRang 2) returns wrong result when two key ranges have the same upper bound values but one is inclusive and another is exclusive Key: PHOENIX-5176

[jira] [Updated] (PHOENIX-5176) KeyRange.compareUpperRange(KeyRang 1, KeyRang 2) returns wrong result when two key ranges have the same upper bound values but one is inclusive and another is exclusive

[ https://issues.apache.org/jira/browse/PHOENIX-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5176: Fix Version/s: 4.14.2 5.1.0 4.15.0 > KeyRange.compa

[jira] [Assigned] (PHOENIX-5176) KeyRange.compareUpperRange(KeyRang 1, KeyRang 2) returns wrong result when two key ranges have the same upper bound values but one is inclusive and another is exclusiv

[ https://issues.apache.org/jira/browse/PHOENIX-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bin Shi reassigned PHOENIX-5176: Assignee: Bin Shi > KeyRange.compareUpperRange(KeyRang 1, KeyRang 2) returns wrong result when

[jira] [Updated] (PHOENIX-5122) PHOENIX-4322 breaks client backward compatibility

[ https://issues.apache.org/jira/browse/PHOENIX-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac updated PHOENIX-5122: - Attachment: PHOENIX-5122.patch > PHOENIX-4322 breaks client backward compatibility > --

[jira] [Updated] (PHOENIX-4929) IndexOutOfBoundsException when casting timestamp to date

[ https://issues.apache.org/jira/browse/PHOENIX-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-4929: --- Attachment: PHOENIX-4929.patch > IndexOutOfBoundsException when casting timestamp to date > ---

[jira] [Updated] (PHOENIX-5175) Separate client settings for disabling server side mutations for upserts and deletes

[ https://issues.apache.org/jira/browse/PHOENIX-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5175: Attachment: PHOENIX-5175-master-v2.patch > Separate client settings for d

[jira] [Updated] (PHOENIX-5170) Update meta timestamp of parent table when dropping index

[ https://issues.apache.org/jira/browse/PHOENIX-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gabry updated PHOENIX-5170: --- Description: I have a flume client ,which inserting values to phoenix table with an index named idx_abc. W

[jira] [Updated] (PHOENIX-4345) Error message for incorrect index is not accurate

[ https://issues.apache.org/jira/browse/PHOENIX-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-4345: --- Attachment: PHOENIX-4345-4.x-HBase-1.4.patch > Error message for incorrect index is not accurate >

[jira] [Assigned] (PHOENIX-4929) IndexOutOfBoundsException when casting timestamp to date

[ https://issues.apache.org/jira/browse/PHOENIX-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-4929: -- Assignee: Xinyi Yan Affects Version/s: (was: 4.14.0) Attachment:

[jira] [Updated] (PHOENIX-5170) Update meta timestamp of parent table when dropping index

[ https://issues.apache.org/jira/browse/PHOENIX-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gabry updated PHOENIX-5170: --- Flags: Patch,Important External issue URL: https://issues.apache.org/jira/browse/PHOENIX-51

[jira] [Updated] (PHOENIX-5170) Update meta timestamp of parent table when dropping index

[ https://issues.apache.org/jira/browse/PHOENIX-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gabry updated PHOENIX-5170: --- Comment: was deleted (was: Any body here:() > Update meta timestamp of parent table when dropping index >

[jira] [Updated] (PHOENIX-5170) Update meta timestamp of parent table when dropping index

[ https://issues.apache.org/jira/browse/PHOENIX-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gabry updated PHOENIX-5170: --- Attachment: updateParentTableMetaWhenDroppingIndex.patch Fix Version/s: 5.1.0 Description: I h