[
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.patch
[~jeffreyz] - FYI, the upgrade we do from 4.1 to 4.2 is not quite right. Need
to test this patch, but if it looks good, you should pick this up for your
distro too.
Any opinions on handling 4.2.0 (just went out to maven today) to 4.2.1? Should
we worry about this case or just get a quick patch release out and ask users to
hold off using 4.2.0 if they're migrating from 4.1 currently? [~lhofhansl],
[~apurtell] - any opinions?
> 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
>
>
> 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)
