[
https://issues.apache.org/jira/browse/PHOENIX-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572749#comment-16572749
]
Thomas D'Silva commented on PHOENIX-4838:
-----------------------------------------
I think [~m2je] is going to keep the existing VIEW_INDEX_ID column and add a
column to store its type.
PTable will represent the viewindexid as a long. In order to allow an old
client to talk to a new server should we keep the existing short field and add
a new field to represent the viewIndexId stored as a long in PTable.proto? The
server would set both the existing field and this new field.
> 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)
