[
https://issues.apache.org/jira/browse/PHOENIX-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308442#comment-14308442
]
Samarth Jain commented on PHOENIX-1641:
---------------------------------------
If I am understanding this correctly, is the motive behind this change to allow
for upgrade from 4.x to 4.3 where x could be 0/1/2? If not, then do we still
need to have INDEX_TYPE, INDEX_DISABLE_TIMESTAMP columns since they were added
in 4.1/4.2 releases. If we really are supporting 4.x to 4.3 upgrades then we
would probably need to do similar changes for SYSTEM.SEQUENCE table too since
that table's schema also changed.
> Add back the upgrade code in ConnectionQueryServicesImpl
> --------------------------------------------------------
>
> Key: PHOENIX-1641
> URL: https://issues.apache.org/jira/browse/PHOENIX-1641
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
> Assignee: Samarth Jain
> Fix For: 5.0.0, 4.3
>
> Attachments: PHOENIX-1641.patch
>
>
> The code got removed in the commit:
> https://github.com/apache/phoenix/commit/58c80a1857659962d695bc8e5fe22b4e401b7f0a
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
