[ 
https://issues.apache.org/jira/browse/PHOENIX-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459158#comment-16459158
 ] 

Hudson commented on PHOENIX-4709:
---------------------------------

ABORTED: Integrated in Jenkins build PreCommit-PHOENIX-Build #1846 (See 
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/1846/])
PHOENIX-4709 Alter split policy in upgrade path for system tables (jtaylor: rev 
fc194c568ee5a4a7ba0e92b64ae24f7cf4b224e5)
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixDatabaseMetaData.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/QueryConstants.java


> Alter split policy in upgrade path for system tables
> ----------------------------------------------------
>
>                 Key: PHOENIX-4709
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4709
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>            Priority: Major
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4709_v1.patch
>
>
> With PHOENIX-4700, the split policy would only change for new installations. 
> For existing installations, the schema of system tables only changes in the 
> upgrade path, including for HBase metadata now. Thus we need an ALTER TABLE 
> call in our upgrade path.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to