[jira] [Assigned] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required
[ https://issues.apache.org/jira/browse/PHOENIX-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva reassigned PHOENIX-4765: --- Assignee: Thomas D'Silva > Add client and server side config property to enable rollback of splittable > System Catalog if required > -- > > Key: PHOENIX-4765 > URL: https://issues.apache.org/jira/browse/PHOENIX-4765 > Project: Phoenix > Issue Type: Sub-task >Reporter: Thomas D'Silva >Assignee: Thomas D'Silva >Priority: Blocker > > After the server has been upgraded we will have a client and server side > config property that will allow us to rollback the upgrade if required. This > config will: > 1. Continue storing parent column metadata along with a child view > 2. Disallow metadata changes to a base table that require being propagated to > child views. > 3. Prevent SYSTEM.CATALOG from splitting. > If the client is older than the server we also disallow metadata changes to a > base table with child views since we no longer lock the parent on the server > side. This is handled on the client side as part of PHOENIX-3534. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (PHOENIX-4766) Create client side config to stop sending parent metadata while creating child views
[ https://issues.apache.org/jira/browse/PHOENIX-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva resolved PHOENIX-4766. - Resolution: Fixed > Create client side config to stop sending parent metadata while creating > child views > > > Key: PHOENIX-4766 > URL: https://issues.apache.org/jira/browse/PHOENIX-4766 > Project: Phoenix > Issue Type: Sub-task >Reporter: Thomas D'Silva >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required
[ https://issues.apache.org/jira/browse/PHOENIX-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4765: Description: After the server has been upgraded we will have a client and server side config property that will allow us to rollback the upgrade if required. This config will: 1. Continue storing parent column metadata along with a child view 2. Disallow metadata changes to a base table that require being propagated to child views. 3. Prevent SYSTEM.CATALOG from splitting. If the client is older than the server we also disallow metadata changes to a base table with child views since we no longer lock the parent on the server side. This is handled on the client side as part of PHOENIX-3534. was: After the server has been upgraded we will have a server side config property that will allow us to rollback the upgrade if required. This config will: 1. Disallow metadata changes to a base table that require being propagated to child views. If the client is older than the server we also disallow metadata changes to a base table with child views since we no longer lock the parent on the server side. This is handled on the client side in the new jar. 2. Prevent SYSTEM.CATALOG from splitting. > Add client and server side config property to enable rollback of splittable > System Catalog if required > -- > > Key: PHOENIX-4765 > URL: https://issues.apache.org/jira/browse/PHOENIX-4765 > Project: Phoenix > Issue Type: Sub-task >Reporter: Thomas D'Silva >Priority: Blocker > > After the server has been upgraded we will have a client and server side > config property that will allow us to rollback the upgrade if required. This > config will: > 1. Continue storing parent column metadata along with a child view > 2. Disallow metadata changes to a base table that require being propagated to > child views. > 3. Prevent SYSTEM.CATALOG from splitting. > If the client is older than the server we also disallow metadata changes to a > base table with child views since we no longer lock the parent on the server > side. This is handled on the client side as part of PHOENIX-3534. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required
[ https://issues.apache.org/jira/browse/PHOENIX-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4765: Summary: Add client and server side config property to enable rollback of splittable System Catalog if required (was: Add server side config property to disallow metadata changes that require being propagated to children) > Add client and server side config property to enable rollback of splittable > System Catalog if required > -- > > Key: PHOENIX-4765 > URL: https://issues.apache.org/jira/browse/PHOENIX-4765 > Project: Phoenix > Issue Type: Sub-task >Reporter: Thomas D'Silva >Priority: Blocker > > After the server has been upgraded we will have a server side config property > that will allow us to rollback the upgrade if required. This config will: > 1. Disallow metadata changes to a base table that require being propagated to > child views. > If the client is older than the server we also disallow metadata changes to a > base table with child views since we no longer lock the parent on the server > side. This is handled on the client side in the new jar. > 2. Prevent SYSTEM.CATALOG from splitting. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (PHOENIX-5000) Make SecureUserConnectionsTest as Integration test
[ https://issues.apache.org/jira/browse/PHOENIX-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta resolved PHOENIX-5000. -- Resolution: Fixed Fix Version/s: 5.1.0 4.15.0 Pushed the addendum patches to master (5.x-HBase-2.0), 4.x-HBase-1.4, 4.x-HBase-1.3 and 4.x-HBase-1.2 branches. > Make SecureUserConnectionsTest as Integration test > -- > > Key: PHOENIX-5000 > URL: https://issues.apache.org/jira/browse/PHOENIX-5000 > Project: Phoenix > Issue Type: Bug >Reporter: Karan Mehta >Assignee: Karan Mehta >Priority: Major > Fix For: 4.15.0, 5.1.0 > > Attachments: PHOENIX-5000.master.001.patch, > PHOENIX-5000.master.002.patch, PHOENIX-5000.master.003.patch, > PHOENIX-5000.master.004.patch > > > SecureUserConnectionsTest is marked as unit test even though it starts a > MiniKdc as part of its setup. Moreover it is flaky since it fails to find > Kerberos realm on Jenkins boxes. Since this unit test fails, it doesn't allow > other Integration tests to run. > This Jira is aimed two fold, first to move this to IT and second understand > the reason for flakyness. > [~tdsilva] FYI. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (PHOENIX-5000) Make SecureUserConnectionsTest as Integration test
[ https://issues.apache.org/jira/browse/PHOENIX-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta reopened PHOENIX-5000: -- Thanks [~tdsilva] for pointing it out. Will add the addendum. > Make SecureUserConnectionsTest as Integration test > -- > > Key: PHOENIX-5000 > URL: https://issues.apache.org/jira/browse/PHOENIX-5000 > Project: Phoenix > Issue Type: Bug >Reporter: Karan Mehta >Assignee: Karan Mehta >Priority: Major > Attachments: PHOENIX-5000.master.001.patch, > PHOENIX-5000.master.002.patch, PHOENIX-5000.master.003.patch, > PHOENIX-5000.master.004.patch > > > SecureUserConnectionsTest is marked as unit test even though it starts a > MiniKdc as part of its setup. Moreover it is flaky since it fails to find > Kerberos realm on Jenkins boxes. Since this unit test fails, it doesn't allow > other Integration tests to run. > This Jira is aimed two fold, first to move this to IT and second understand > the reason for flakyness. > [~tdsilva] FYI. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (PHOENIX-5031) Fix TenantSpecificViewIndexIT test failures in HBase 1.2 branch
Thomas D'Silva created PHOENIX-5031: --- Summary: Fix TenantSpecificViewIndexIT test failures in HBase 1.2 branch Key: PHOENIX-5031 URL: https://issues.apache.org/jira/browse/PHOENIX-5031 Project: Phoenix Issue Type: Bug Reporter: Thomas D'Silva Assignee: Thomas D'Silva org.apache.phoenix.end2end.TenantSpecificViewIndexIT.testMultiCFViewLocalIndex org.apache.phoenix.end2end.TenantSpecificViewIndexIT.testMultiCFViewIndexWithNamespaceMapping org.apache.phoenix.end2end.TenantSpecificViewIndexIT.testMultiCFViewIndex -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4983) Allow using a connection with a SCN set to write data to tables EXCEPT transactional tables or mutable tables with indexes
[ https://issues.apache.org/jira/browse/PHOENIX-4983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-4983: Description: Currently If a SCN set on a connection it is read-only. We only need to prevent a client from setting the timestamp for transactional tables or mutable tables with global and local indexes. (was: Currently If a SCN set on a connection it is read-only. We only need to prevent a client from setting the timestamp for transactional tables or mutable tables with global indexes.) > Allow using a connection with a SCN set to write data to tables EXCEPT > transactional tables or mutable tables with indexes > -- > > Key: PHOENIX-4983 > URL: https://issues.apache.org/jira/browse/PHOENIX-4983 > Project: Phoenix > Issue Type: New Feature >Reporter: Thomas D'Silva >Assignee: Swaroopa Kadam >Priority: Major > Labels: SFDC > > Currently If a SCN set on a connection it is read-only. We only need to > prevent a client from setting the timestamp for transactional tables or > mutable tables with global and local indexes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
