[jira] [Assigned] (PHOENIX-6154) Move check to client side to see if there are any child views that need to be dropped while dropping a table/view

[ https://issues.apache.org/jira/browse/PHOENIX-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni reassigned PHOENIX-6154: - Assignee: (was: Chinmay Kulkarni) > Move check to client side to see if th

[jira] [Assigned] (PHOENIX-6134) Provide a server-side configuration to disallow all DDLs

[ https://issues.apache.org/jira/browse/PHOENIX-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni reassigned PHOENIX-6134: - Assignee: Chinmay Kulkarni > Provide a server-side configuration to disallow a

[jira] [Updated] (PHOENIX-6141) Ensure consistency between SYSTEM.CATALOG and SYSTEM.CHILD_LINK

[ https://issues.apache.org/jira/browse/PHOENIX-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6141: -- Priority: Blocker (was: Major) > Ensure consistency between SYSTEM.CATALOG and SYSTE

[jira] [Updated] (PHOENIX-6134) Provide a server-side configuration to disallow all DDLs

[ https://issues.apache.org/jira/browse/PHOENIX-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6134: -- Priority: Critical (was: Major) > Provide a server-side configuration to disallow al

[jira] [Created] (PHOENIX-6142) Make DDL operations resilient to orphan parent->child linking rows in SYSTEM.CHILD_LINK

Chinmay Kulkarni created PHOENIX-6142: - Summary: Make DDL operations resilient to orphan parent->child linking rows in SYSTEM.CHILD_LINK Key: PHOENIX-6142 URL: https://issues.apache.org/jira/browse/PHOENIX-614

[jira] [Created] (PHOENIX-6141) Ensure consistency between SYSTEM.CATALOG and SYSTEM.CHILD_LINK

Chinmay Kulkarni created PHOENIX-6141: - Summary: Ensure consistency between SYSTEM.CATALOG and SYSTEM.CHILD_LINK Key: PHOENIX-6141 URL: https://issues.apache.org/jira/browse/PHOENIX-6141 Project:

[jira] [Updated] (PHOENIX-6075) DDLs issued via a tenant-specific connection do not write SYSTEM.MUTEX cells

[ https://issues.apache.org/jira/browse/PHOENIX-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6075: -- Attachment: PHOENIX-6075-4.x-v2.patch > DDLs issued via a tenant-specific connection

[jira] [Updated] (PHOENIX-6075) DDLs issued via a tenant-specific connection do not write SYSTEM.MUTEX cells

[ https://issues.apache.org/jira/browse/PHOENIX-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6075: -- Attachment: PHOENIX-6075-4.x-v1.patch > DDLs issued via a tenant-specific connection

[jira] [Updated] (PHOENIX-6139) Fix ConcurrentMutationsExtendedIT

[ https://issues.apache.org/jira/browse/PHOENIX-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6139: -- Labels: phoenix-hardening quality-improvement (was: ) > Fix ConcurrentMutationsExten

[jira] [Updated] (PHOENIX-6139) Fix ConcurrentMutationsExtendedIT

[ https://issues.apache.org/jira/browse/PHOENIX-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6139: -- Description: ConcurrentMutationsExtendedIT has been flapping and randomly failing on

[jira] [Created] (PHOENIX-6139) Fix ConcurrentMutationsExtendedIT

Chinmay Kulkarni created PHOENIX-6139: - Summary: Fix ConcurrentMutationsExtendedIT Key: PHOENIX-6139 URL: https://issues.apache.org/jira/browse/PHOENIX-6139 Project: Phoenix Issue Type: B

[jira] [Updated] (PHOENIX-6072) SYSTEM.MUTEX not created with a TTL on a fresh cluster connected to by a 4.15+ client

[ https://issues.apache.org/jira/browse/PHOENIX-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6072: -- Attachment: PHOENIX-6072-master-v1.patch > SYSTEM.MUTEX not created with a TTL on a f

[jira] [Updated] (PHOENIX-6075) DDLs issued via a tenant-specific connection do not write SYSTEM.MUTEX cells

[ https://issues.apache.org/jira/browse/PHOENIX-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6075: -- Fix Version/s: 5.1.0 > DDLs issued via a tenant-specific connection do not write SYST

[jira] [Updated] (PHOENIX-6134) Provide a server-side configuration to disallow all DDLs

[ https://issues.apache.org/jira/browse/PHOENIX-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6134: -- Description: Having such an option is useful when doing a Phoenix rollback on a clust

[jira] [Created] (PHOENIX-6134) Provide a server-side configuration to disallow all DDLs

Chinmay Kulkarni created PHOENIX-6134: - Summary: Provide a server-side configuration to disallow all DDLs Key: PHOENIX-6134 URL: https://issues.apache.org/jira/browse/PHOENIX-6134 Project: Phoenix

[jira] [Updated] (PHOENIX-6132) Exclude upstream project's transitive dependencies from phoenix-client JAR build.

[ https://issues.apache.org/jira/browse/PHOENIX-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6132: -- Priority: Major (was: Trivial) > Exclude upstream project's transitive dependencies

[jira] [Updated] (PHOENIX-6133) Exclude transitive dependency of hadoop-common STAX2 and WOODSTOX jars from phoenix-client JAR

[ https://issues.apache.org/jira/browse/PHOENIX-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6133: -- Fix Version/s: 4.16.0 > Exclude transitive dependency of hadoop-common STAX2 and WOOD

[jira] [Updated] (PHOENIX-6133) Exclude transitive dependency of hadoop-common STAX2 and WOODSTOX jars from phoenix-client JAR

[ https://issues.apache.org/jira/browse/PHOENIX-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6133: -- Affects Version/s: 4.15.0 > Exclude transitive dependency of hadoop-common STAX2 and

[jira] [Updated] (PHOENIX-6132) Exclude upstream project's transitive dependencies from phoenix-client JAR build.

[ https://issues.apache.org/jira/browse/PHOENIX-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6132: -- Affects Version/s: 4.15.0 > Exclude upstream project's transitive dependencies from p

[jira] [Updated] (PHOENIX-6132) Exclude upstream project's transitive dependencies from phoenix-client JAR build.

[ https://issues.apache.org/jira/browse/PHOENIX-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6132: -- Fix Version/s: 4.16.0 > Exclude upstream project's transitive dependencies from phoen

[jira] [Updated] (PHOENIX-6129) Remove unnecessary HBase admin API calls when writing and deleting mutex cells

[ https://issues.apache.org/jira/browse/PHOENIX-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6129: -- Summary: Remove unnecessary HBase admin API calls when writing and deleting mutex cel

[jira] [Updated] (PHOENIX-6127) Prevent unnecessary HBase admin API calls in ViewUtil.getSystemTableForChildLinks() and act lazily instead

[ https://issues.apache.org/jira/browse/PHOENIX-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6127: -- Summary: Prevent unnecessary HBase admin API calls in ViewUtil.getSystemTableForChild

[jira] [Created] (PHOENIX-6129) Remove unnecessary HBase Admin API calls when writing and deleting mutex cells

Chinmay Kulkarni created PHOENIX-6129: - Summary: Remove unnecessary HBase Admin API calls when writing and deleting mutex cells Key: PHOENIX-6129 URL: https://issues.apache.org/jira/browse/PHOENIX-6129

[jira] [Created] (PHOENIX-6128) Remove unused getAdmin() call inside CQSI.init()

Chinmay Kulkarni created PHOENIX-6128: - Summary: Remove unused getAdmin() call inside CQSI.init() Key: PHOENIX-6128 URL: https://issues.apache.org/jira/browse/PHOENIX-6128 Project: Phoenix

[jira] [Created] (PHOENIX-6127) Prevent unnecessary HBase Admin API calls in ViewUtil.getSystemTableForChildLinks() and act lazily instead

Chinmay Kulkarni created PHOENIX-6127: - Summary: Prevent unnecessary HBase Admin API calls in ViewUtil.getSystemTableForChildLinks() and act lazily instead Key: PHOENIX-6127 URL: https://issues.apache.org/jira

[jira] [Updated] (PHOENIX-6126) All createViewAddChildLink requests will go to the same region of SYSTEM.CHILD_LINK

[ https://issues.apache.org/jira/browse/PHOENIX-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6126: -- Priority: Minor (was: Major) > All createViewAddChildLink requests will go to the sa

[jira] [Created] (PHOENIX-6126) All createViewAddChildLink requests will go to the same region of SYSTEM.CHILD_LINK

Chinmay Kulkarni created PHOENIX-6126: - Summary: All createViewAddChildLink requests will go to the same region of SYSTEM.CHILD_LINK Key: PHOENIX-6126 URL: https://issues.apache.org/jira/browse/PHOENIX-6126

[jira] [Created] (PHOENIX-6125) Make sure SYSTEM.TASK does not split

Chinmay Kulkarni created PHOENIX-6125: - Summary: Make sure SYSTEM.TASK does not split Key: PHOENIX-6125 URL: https://issues.apache.org/jira/browse/PHOENIX-6125 Project: Phoenix Issue Type

[jira] [Created] (PHOENIX-6124) Block adding/dropping a column on a parent view for clients <4.15 and for clients that have phoenix.allow.system.catalog.rollback=true

Chinmay Kulkarni created PHOENIX-6124: - Summary: Block adding/dropping a column on a parent view for clients <4.15 and for clients that have phoenix.allow.system.catalog.rollback=true Key: PHOENIX-6124 URL: h

[jira] [Created] (PHOENIX-6123) Old clients cannot query a view if the parent has an index

Chinmay Kulkarni created PHOENIX-6123: - Summary: Old clients cannot query a view if the parent has an index Key: PHOENIX-6123 URL: https://issues.apache.org/jira/browse/PHOENIX-6123 Project: Phoeni

[jira] [Updated] (PHOENIX-4195) PHOENIX-4195 Deleting view rows with extended PKs through the base table silently fails

[ https://issues.apache.org/jira/browse/PHOENIX-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-4195: -- Fix Version/s: 4.16.0 > PHOENIX-4195 Deleting view rows with extended PKs through the

[jira] [Updated] (PHOENIX-4861) While adding a view column make a single RPC to update the encoded column qualifier counter and remove the table from the cache of the physical table

[ https://issues.apache.org/jira/browse/PHOENIX-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-4861: -- Fix Version/s: (was: 4.16.1) 4.16.0 > While adding a view colu

[jira] [Updated] (PHOENIX-5960) Creating a view on a non-existent table throws the wrong exception

[ https://issues.apache.org/jira/browse/PHOENIX-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5960: -- Fix Version/s: 4.16.0 > Creating a view on a non-existent table throws the wrong exce

[jira] [Updated] (PHOENIX-5943) Consider splitting up SYSTEM.TASK into 2 tables - one for queued jobs and one for task history

[ https://issues.apache.org/jira/browse/PHOENIX-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5943: -- Fix Version/s: (was: 4.16.1) 4.17.0 > Consider splitting up SY

[jira] [Updated] (PHOENIX-5943) Consider splitting up SYSTEM.TASK into 2 tables - one for queued jobs and one for task history

[ https://issues.apache.org/jira/browse/PHOENIX-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5943: -- Fix Version/s: (was: 4.16.0) 4.16.1 > Consider splitting up SY

[jira] [Updated] (PHOENIX-4878) Remove SharedTableState and replace with PTable

[ https://issues.apache.org/jira/browse/PHOENIX-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-4878: -- Priority: Minor (was: Major) > Remove SharedTableState and replace with PTable > ---

[jira] [Updated] (PHOENIX-6036) Introduce a new statement to rollback Splittable SYSTEM.CATALOG changes when phoenix.allow.system.catalog.rollback=true

[ https://issues.apache.org/jira/browse/PHOENIX-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6036: -- Priority: Critical (was: Major) > Introduce a new statement to rollback Splittable S

[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data

[ https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5066: -- Fix Version/s: (was: 4.15.1) > The TimeZone is incorrectly used during writing or

[jira] [Updated] (PHOENIX-4846) WhereOptimizer.pushKeyExpressionsToScan() does not work correctly if the sort order of pk columns being filtered on changes

[ https://issues.apache.org/jira/browse/PHOENIX-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-4846: -- Fix Version/s: (was: 4.16.1) (was: 4.15.1)

[jira] [Updated] (PHOENIX-6069) We should check that the parent table key is in the region in the MetaDataEndpointImpl.dropTable code

[jira] [Updated] (PHOENIX-6069) We should check that the parent table key is in the region in the MetaDataEndpointImpl.dropTable code

[ https://issues.apache.org/jira/browse/PHOENIX-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6069: -- Attachment: (was: PHOENIX-6069-4.x-v1.patch) > We should check that the parent ta

[jira] [Updated] (PHOENIX-6069) We should check that the parent table key is in the region in the MetaDataEndpointImpl.dropTable code

[ https://issues.apache.org/jira/browse/PHOENIX-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6069: -- Attachment: (was: PHOENIX-6069-4.x.patch) > We should check that the parent table

[jira] [Updated] (PHOENIX-6092) Optionally queue DDL requests issued while metadata upgrade is in progress and replay on upgrade failure

[ https://issues.apache.org/jira/browse/PHOENIX-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6092: -- Description: Currently, if a metadata upgrade is in progress (either triggered by an

[jira] [Updated] (PHOENIX-6092) Optionally queue DDL requests issued while metadata upgrade is in progress and replay on upgrade failure

[ https://issues.apache.org/jira/browse/PHOENIX-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6092: -- Summary: Optionally queue DDL requests issued while metadata upgrade is in progress a

[jira] [Updated] (PHOENIX-6092) Queue DDL requests issued while metadata upgrade is in progress and replay on upgrade failure

[ https://issues.apache.org/jira/browse/PHOENIX-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6092: -- Description: Currently, if a metadata upgrade is in progress (either triggered by an

[jira] [Created] (PHOENIX-6092) Queue DDL requests issued while metadata upgrade is in progress and replay on upgrade failure

Chinmay Kulkarni created PHOENIX-6092: - Summary: Queue DDL requests issued while metadata upgrade is in progress and replay on upgrade failure Key: PHOENIX-6092 URL: https://issues.apache.org/jira/browse/PHOEN

[jira] [Updated] (PHOENIX-6086) Take a snapshot of all SYSTEM tables before attempting to upgrade them

[ https://issues.apache.org/jira/browse/PHOENIX-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6086: -- Priority: Critical (was: Major) > Take a snapshot of all SYSTEM tables before attemp

[jira] [Updated] (PHOENIX-6086) Take a snapshot of all SYSTEM tables before attempting to upgrade them

[ https://issues.apache.org/jira/browse/PHOENIX-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6086: -- Description: Currently we only take a snapshot of SYSTEM.CATALOG before attempting to

[jira] [Created] (PHOENIX-6091) Calling MetaDataProtocol.getVersion() on a 4.16 timestamp gives version as 4.15.x

Chinmay Kulkarni created PHOENIX-6091: - Summary: Calling MetaDataProtocol.getVersion() on a 4.16 timestamp gives version as 4.15.x Key: PHOENIX-6091 URL: https://issues.apache.org/jira/browse/PHOENIX-6091

[jira] [Updated] (PHOENIX-5634) Use 'phoenix.default.update.cache.frequency' from connection properties at query time

[ https://issues.apache.org/jira/browse/PHOENIX-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5634: -- Fix Version/s: 4.16.0 > Use 'phoenix.default.update.cache.frequency' from connection

[jira] [Created] (PHOENIX-6087) Phoenix Connection leak in UpgradeUtil.addViewIndexToParentLinks()

Chinmay Kulkarni created PHOENIX-6087: - Summary: Phoenix Connection leak in UpgradeUtil.addViewIndexToParentLinks() Key: PHOENIX-6087 URL: https://issues.apache.org/jira/browse/PHOENIX-6087 Projec

[jira] [Updated] (PHOENIX-6086) Take a snapshot of all SYSTEM tables before attempting to upgrade them

[ https://issues.apache.org/jira/browse/PHOENIX-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6086: -- Description: Currently we only take a snapshot of SYSTEM.CATALOG before attempting to

[jira] [Created] (PHOENIX-6086) Take a snapshot of all SYSTEM tables before attempting to upgrade them

Chinmay Kulkarni created PHOENIX-6086: - Summary: Take a snapshot of all SYSTEM tables before attempting to upgrade them Key: PHOENIX-6086 URL: https://issues.apache.org/jira/browse/PHOENIX-6086 Pr

[jira] [Created] (PHOENIX-6085) Remove duplicate calls to getSysMutexPhysicalTableNameBytes() during the upgrade path

Chinmay Kulkarni created PHOENIX-6085: - Summary: Remove duplicate calls to getSysMutexPhysicalTableNameBytes() during the upgrade path Key: PHOENIX-6085 URL: https://issues.apache.org/jira/browse/PHOENIX-6085

[jira] [Updated] (PHOENIX-6083) View index creation does a checkAndPut on an incorrect row key

[ https://issues.apache.org/jira/browse/PHOENIX-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6083: -- Attachment: (was: image-2020-08-18-11-09-46-151.png) > View index creation does a

[jira] [Updated] (PHOENIX-6083) View index creation does a checkAndPut on an incorrect row key

[ https://issues.apache.org/jira/browse/PHOENIX-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6083: -- Affects Version/s: 5.0.0 4.15.0 > View index creation does a c

[jira] [Updated] (PHOENIX-6083) View index creation does a checkAndPut on an incorrect row key

[ https://issues.apache.org/jira/browse/PHOENIX-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6083: -- Fix Version/s: 4.16.0 5.1.0 > View index creation does a checkAndP

[jira] [Updated] (PHOENIX-6083) View index creation does a checkAndPut on an incorrect row key

[ https://issues.apache.org/jira/browse/PHOENIX-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6083: -- Labels: phoenix-hardening quality-improvement (was: ) > View index creation does a c

[jira] [Created] (PHOENIX-6083) View index creation does a checkAndPut on an incorrect row key

Chinmay Kulkarni created PHOENIX-6083: - Summary: View index creation does a checkAndPut on an incorrect row key Key: PHOENIX-6083 URL: https://issues.apache.org/jira/browse/PHOENIX-6083 Project: P

[jira] [Updated] (PHOENIX-6082) No need to do checkAndPut when altering properties for a table or view with column-encoding enabled

[ https://issues.apache.org/jira/browse/PHOENIX-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6082: -- Affects Version/s: 5.0.0 4.15.0 > No need to do checkAndPut wh

[jira] [Updated] (PHOENIX-6082) No need to do checkAndPut when altering properties for a table or view with column-encoding enabled

[ https://issues.apache.org/jira/browse/PHOENIX-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6082: -- Labels: performance phoenix-hardening quality-improvement (was: ) > No need to do ch

[jira] [Updated] (PHOENIX-6082) No need to do checkAndPut when altering properties for a table or view with column-encoding enabled

[ https://issues.apache.org/jira/browse/PHOENIX-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6082: -- Fix Version/s: 4.16.0 5.1.0 > No need to do checkAndPut when alter

[jira] [Created] (PHOENIX-6082) No need to do checkAndPut when altering properties for a table or view with column-encoding enabled

Chinmay Kulkarni created PHOENIX-6082: - Summary: No need to do checkAndPut when altering properties for a table or view with column-encoding enabled Key: PHOENIX-6082 URL: https://issues.apache.org/jira/browse

[jira] [Updated] (PHOENIX-6075) DDLs issued via a tenant-specific connection do not write SYSTEM.MUTEX cells

[ https://issues.apache.org/jira/browse/PHOENIX-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6075: -- Priority: Blocker (was: Major) > DDLs issued via a tenant-specific connection do not

[jira] [Updated] (PHOENIX-6075) DDLs issued via a tenant-specific connection do not write SYSTEM.MUTEX cells

[ https://issues.apache.org/jira/browse/PHOENIX-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6075: -- Affects Version/s: 5.0.0 4.15.0 > DDLs issued via a tenant-spe

[jira] [Updated] (PHOENIX-6075) DDLs issued via a tenant-specific connection do not write SYSTEM.MUTEX cells

[ https://issues.apache.org/jira/browse/PHOENIX-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6075: -- Fix Version/s: 4.16.0 > DDLs issued via a tenant-specific connection do not write SYS

[jira] [Created] (PHOENIX-6075) DDLs issued via a tenant-specific connection do not write SYSTEM.MUTEX cells

Chinmay Kulkarni created PHOENIX-6075: - Summary: DDLs issued via a tenant-specific connection do not write SYSTEM.MUTEX cells Key: PHOENIX-6075 URL: https://issues.apache.org/jira/browse/PHOENIX-6075

[jira] [Assigned] (PHOENIX-6072) SYSTEM.MUTEX not created with a TTL on a fresh cluster connected to by a 4.15+ client

[ https://issues.apache.org/jira/browse/PHOENIX-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni reassigned PHOENIX-6072: - Assignee: Chinmay Kulkarni > SYSTEM.MUTEX not created with a TTL on a fresh cl

[jira] [Created] (PHOENIX-6072) SYSTEM.MUTEX not created with a TTL on a fresh cluster connected to by a 4.15+ client

Chinmay Kulkarni created PHOENIX-6072: - Summary: SYSTEM.MUTEX not created with a TTL on a fresh cluster connected to by a 4.15+ client Key: PHOENIX-6072 URL: https://issues.apache.org/jira/browse/PHOENIX-6072

[jira] [Created] (PHOENIX-6069) We should check that the parent table key is in the region in the MetaDataEndpointImpl.dropTable code

Chinmay Kulkarni created PHOENIX-6069: - Summary: We should check that the parent table key is in the region in the MetaDataEndpointImpl.dropTable code Key: PHOENIX-6069 URL: https://issues.apache.org/jira/brow

[jira] [Updated] (PHOENIX-6066) MetaDataEndpointImpl.doGetTable should acquire a readLock instead of an exclusive writeLock on the table header row

[ https://issues.apache.org/jira/browse/PHOENIX-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6066: -- Description: Throughout MetaDataEndpointImpl, wherever we need to acquire a row lock

[jira] [Updated] (PHOENIX-6066) MetaDataEndpointImpl.doGetTable should acquire a readLock instead of an exclusive writeLock on the table header row

[ https://issues.apache.org/jira/browse/PHOENIX-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6066: -- Description: Throughout MetaDataEndpointImpl, wherever we need to acquire a row lock

[jira] [Updated] (PHOENIX-6066) MetaDataEndpointImpl.doGetTable should acquire a readLock instead of an exclusive writeLock on the table header row

[ https://issues.apache.org/jira/browse/PHOENIX-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6066: -- Labels: quality-improvement (was: ) > MetaDataEndpointImpl.doGetTable should acquire

[jira] [Created] (PHOENIX-6066) MetaDataEndpointImpl.doGetTable should acquire a readLock instead of an exclusive writeLock on the table header row

Chinmay Kulkarni created PHOENIX-6066: - Summary: MetaDataEndpointImpl.doGetTable should acquire a readLock instead of an exclusive writeLock on the table header row Key: PHOENIX-6066 URL: https://issues.apache

[jira] [Updated] (PHOENIX-6035) Extend phoenix.allow.system.catalog.rollback or introduce a new config to completely rollback changes introduced by Splittable SYSTEM.CATALOG

[ https://issues.apache.org/jira/browse/PHOENIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6035: -- Summary: Extend phoenix.allow.system.catalog.rollback or introduce a new config to co

[jira] [Updated] (PHOENIX-5404) Move check to client side to see if there are any child views that need to be dropped while receating a table/view

[ https://issues.apache.org/jira/browse/PHOENIX-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5404: -- Priority: Major (was: Blocker) > Move check to client side to see if there are any c

[jira] [Updated] (PHOENIX-5404) Move check to client side to see if there are any child views that need to be dropped while receating a table/view

[ https://issues.apache.org/jira/browse/PHOENIX-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5404: -- Priority: Blocker (was: Major) > Move check to client side to see if there are any c

[jira] [Updated] (PHOENIX-5497) When dropping a view, use the PTable for generating delete mutations for links rather than scanning SYSTEM.CATALOG

[ https://issues.apache.org/jira/browse/PHOENIX-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5497: -- Parent: PHOENIX-3534 Issue Type: Sub-task (was: Improvement) > When dropping

[jira] [Updated] (PHOENIX-5498) When dropping a view, send delete mutations for parent->child links from client to server rather than doing server-server RPCs

[ https://issues.apache.org/jira/browse/PHOENIX-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5498: -- Parent: PHOENIX-3534 Issue Type: Sub-task (was: Improvement) > When dropping

[jira] [Deleted] (PHOENIX-6062) When dropping a view, use the PTable for generating delete mutations for links rather than scanning SYSTEM.CATALOG

[ https://issues.apache.org/jira/browse/PHOENIX-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni deleted PHOENIX-6062: -- > When dropping a view, use the PTable for generating delete mutations for > links rath

[jira] [Created] (PHOENIX-6062) When dropping a view, use the PTable for generating delete mutations for links rather than scanning SYSTEM.CATALOG

Chinmay Kulkarni created PHOENIX-6062: - Summary: When dropping a view, use the PTable for generating delete mutations for links rather than scanning SYSTEM.CATALOG Key: PHOENIX-6062 URL: https://issues.apache.

[jira] [Updated] (PHOENIX-4868) Create a column attribute IS_EXCLUDED to denote a dropped derived column and remove LinkType.EXCLUDED_COLUMN

[ https://issues.apache.org/jira/browse/PHOENIX-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-4868: -- Fix Version/s: 4.16.1 > Create a column attribute IS_EXCLUDED to denote a dropped der

[jira] [Updated] (PHOENIX-4868) Create a column attribute IS_EXCLUDED to denote a dropped derived column and remove LinkType.EXCLUDED_COLUMN

[ https://issues.apache.org/jira/browse/PHOENIX-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-4868: -- Affects Version/s: 5.0.0 4.15.0 > Create a column attribute IS

[jira] [Updated] (PHOENIX-4861) While adding a view column make a single RPC to update the encoded column qualifier counter and remove the table from the cache of the physical table

[ https://issues.apache.org/jira/browse/PHOENIX-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-4861: -- Affects Version/s: 5.0.0 4.15.0 > While adding a view column m

[jira] [Updated] (PHOENIX-4861) While adding a view column make a single RPC to update the encoded column qualifier counter and remove the table from the cache of the physical table

[ https://issues.apache.org/jira/browse/PHOENIX-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-4861: -- Fix Version/s: 4.16.1 > While adding a view column make a single RPC to update the en

[jira] [Updated] (PHOENIX-5958) Diverged view created via an older client still sees dropped column data

[ https://issues.apache.org/jira/browse/PHOENIX-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5958: -- Attachment: (was: PHOENIX-5958-4.x-v3.patch) > Diverged view created via an older

[jira] [Updated] (PHOENIX-5958) Diverged view created via an older client still sees dropped column data

[ https://issues.apache.org/jira/browse/PHOENIX-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5958: -- Attachment: PHOENIX-5958-4.x-v3.patch > Diverged view created via an older client sti

[jira] [Assigned] (PHOENIX-5958) Diverged view created via an older client still sees dropped column data

[ https://issues.apache.org/jira/browse/PHOENIX-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni reassigned PHOENIX-5958: - Assignee: Chinmay Kulkarni > Diverged view created via an older client still s

[jira] [Updated] (PHOENIX-5958) Diverged view created via an older client still sees dropped column data

[ https://issues.apache.org/jira/browse/PHOENIX-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5958: -- Attachment: PHOENIX-5958-4.x-v2.patch > Diverged view created via an older client sti

[jira] [Updated] (PHOENIX-5958) Diverged view created via an older client still sees dropped column data

[ https://issues.apache.org/jira/browse/PHOENIX-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5958: -- Attachment: (was: PHOENIX-5958-4.x-v1.patch) > Diverged view created via an older

[jira] [Updated] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6045: -- Fix Version/s: 4.16.0 5.1.0 > Delete that should qualify for index

[jira] [Created] (PHOENIX-6047) Release phoenix-queryserver jars compatible with 4.15 and create a workflow for future 4.x releases

Chinmay Kulkarni created PHOENIX-6047: - Summary: Release phoenix-queryserver jars compatible with 4.15 and create a workflow for future 4.x releases Key: PHOENIX-6047 URL: https://issues.apache.org/jira/browse

[jira] [Created] (PHOENIX-6046) Release a phoenix-connectors jar compatible with 4.15 and create a workflow for future 4.x releases

Chinmay Kulkarni created PHOENIX-6046: - Summary: Release a phoenix-connectors jar compatible with 4.15 and create a workflow for future 4.x releases Key: PHOENIX-6046 URL: https://issues.apache.org/jira/browse

[jira] [Updated] (PHOENIX-5958) Diverged view created via an older client still sees dropped column data

[ https://issues.apache.org/jira/browse/PHOENIX-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5958: -- Attachment: (was: PHOENIX-5958-4.x-v1.patch) > Diverged view created via an older

[jira] [Updated] (PHOENIX-5958) Diverged view created via an older client still sees dropped column data

[ https://issues.apache.org/jira/browse/PHOENIX-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5958: -- Comment: was deleted (was: Thanks [~tdsilva]. Attaching a debug patch to test if code

[jira] [Updated] (PHOENIX-5958) Diverged view created via an older client still sees dropped column data

[ https://issues.apache.org/jira/browse/PHOENIX-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5958: -- Comment: was deleted (was: {color:red}-1 overall{color}. Here are the results of tes

[jira] [Updated] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6045: -- Affects Version/s: 5.0.0 4.15.0 4.14.3

[jira] [Created] (PHOENIX-6036) Introduce a new statement to rollback Splittable SYSTEM.CATALOG changes when phoenix.allow.system.catalog.rollback=true

Chinmay Kulkarni created PHOENIX-6036: - Summary: Introduce a new statement to rollback Splittable SYSTEM.CATALOG changes when phoenix.allow.system.catalog.rollback=true Key: PHOENIX-6036 URL: https://issues.ap

[jira] [Updated] (PHOENIX-6035) Extend phoenix.allow.system.catalog.rollback to completely rollback changes introduced by Splittable SYSTEM.CATALOG

[ https://issues.apache.org/jira/browse/PHOENIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6035: -- Description: Currently, https://issues.apache.org/jira/browse/PHOENIX-3534 just makes

[jira] [Updated] (PHOENIX-6035) Extend phoenix.allow.system.catalog.rollback to completely rollback changes introduced by Splittable SYSTEM.CATALOG

[ https://issues.apache.org/jira/browse/PHOENIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6035: -- Fix Version/s: 4.16.0 5.1.0 > Extend phoenix.allow.system.catalog.

<    1   2   3   4   5   6   7   8   9   10   >