[
https://issues.apache.org/jira/browse/PHOENIX-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572497#comment-16572497
]
James Taylor commented on PHOENIX-4838:
---------------------------------------
I commented on that pull request why I don't think it's a good idea to remove
viewIndexId. We should instead keep it, but allow it to be a long or a short on
a table by table basis. We don't want to have to rewrite the existing rows
(i.e. the data rows) in the existing views that are already using a short value.
> Remove viewIndexId from PHOENIX protobuf
> ----------------------------------------
>
> Key: PHOENIX-4838
> URL: https://issues.apache.org/jira/browse/PHOENIX-4838
> Project: Phoenix
> Issue Type: Task
> Affects Versions: 5.0.0
> Reporter: Mehdi Salarkia
> Priority: Minor
>
> As part of discussion to address PHOENIX-3547 the suggestion was to add a new
> long property (viewIndexLongId) and remove veiwIndexId which is an int in the
> next version of Apache Phoenix to support more number of indices while
> keeping backward compatibility during the migration process.
> More details:
> [https://github.com/apache/phoenix/pull/317]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
