[
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_v3.patch
Final patch on top of v2 patch. Instead of running admin.split() 256 times
(which wasn't working in my testing as I'd always get a not serving region
exception), I create a snapshot of the SYSTEM.SEQUENCE table, drop the table,
create it again pre-split, and then restore the snapshot. This works well in my
testing (though it'd be nice if I could create a table in a disable state so I
don't have to disable it after creating it).
> 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,
> 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)
