[
https://issues.apache.org/jira/browse/PHOENIX-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1401:
----------------------------------
Attachment: PHOENIX-1401_v2.patch
Enhanced patch that upgrades 4.2.0 users. For 4.2.0 users, we'll only pre-split
the SYSTEM.SEQUENCE table, while for 4.1 users, we'll salt the table and
pre-split it.
Are there APIs to provide more than one new split point for a table,
[~lhofhansl]? How long will it take to split a table 256 ways (assuming very
little data currently exists)? Would you mind giving this patch a quick review?
Once committed, [~mujtaba] would you mind testing the 4.1->4.2.1 and
4.2.0->4.2.1 upgrade paths?
> 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
> Attachments: PHOENIX-1401.patch, PHOENIX-1401_v2.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)
