[
https://issues.apache.org/jira/browse/PHOENIX-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197772#comment-14197772
]
Hudson commented on PHOENIX-1401:
---------------------------------
SUCCESS: Integrated in Phoenix-master #471 (See
[https://builds.apache.org/job/Phoenix-master/471/])
PHOENIX-1401 SYSTEM.SEQUENCE table is not pre-split as expected (jtaylor: rev
880fd9f9447da2bf435af2031c9468797558bb79)
*
phoenix-core/src/main/java/org/apache/phoenix/schema/TableAlreadyExistsException.java
* phoenix-core/src/main/java/org/apache/phoenix/util/UpgradeUtil.java
*
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataProtocol.java
PHOENIX-1401 SYSTEM.SEQUENCE table is not pre-split as expected (jtaylor: rev
86dff2cc4c5ece8f9ed8625f32029f218c94c700)
* phoenix-core/src/main/java/org/apache/phoenix/util/UpgradeUtil.java
> SYSTEM.SEQUENCE table is not pre-split as expected
> --------------------------------------------------
>
> Key: PHOENIX-1401
> URL: https://issues.apache.org/jira/browse/PHOENIX-1401
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.2, 3.2
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.3, 3.3, 4.2.1, 3.2.1
>
> Attachments: PHOENIX-1401.patch, PHOENIX-1401_v2.patch,
> PHOENIX-1401_v3.patch
>
>
> If a user is upgrading from 4.1 to 4.2, we salt the SYSTEM.SEQUENCE table,
> but we're not pre-splitting it as we should and thus not getting any
> performance gain. Any range scans done will not function correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
