[
https://issues.apache.org/jira/browse/PHOENIX-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967307#comment-16967307
]
Rajeshbabu Chintaguntla commented on PHOENIX-3547:
--------------------------------------------------
[~larsh][~m2je]
In MetaDataEndpointImpl while creating view index id we are always preparing
long view index id irrespective of client passed data type. To avoid all these
issues it might be best to have two sequences one for existing view index id
and other for long view index ids so based on data type we can use the data
type what do you think?
> Promote CATALOG.VIEW_INDEX_ID to an int
> ---------------------------------------
>
> Key: PHOENIX-3547
> URL: https://issues.apache.org/jira/browse/PHOENIX-3547
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Jeremy Huffman
> Assignee: Mehdi Salarkia
> Priority: Blocker
> Fix For: 4.15.0, 5.1.0
>
> Attachments: 4.x-HBase-0.98.patch, 4.x-HBase-1.1.patch,
> 4.x-HBase-1.2.patch, 4.x-HBase-1.3.patch, 4.x-HBase-1.4.patch,
> 4.x-cdh5.11.patch, 4.x-cdh5.12.patch, 4.x-cdh5.13.patch, 4.x-cdh5.14.patch,
> master-PHOENIX-3547.patch
>
>
> Increase the size of CATALOG.VIEW_INDEX_ID from smallint to int to support a
> large number of indexed views on a single table.
> Per James: "The code would just need to be tolerant when reading the data if
> the length is two byte short versus four byte int. At write time, we'd just
> always write an int."
> See:
> https://lists.apache.org/thread.html/22849e4fc73452cee3bea763cf6d5af7164dedcb44573ba6b9f452a2@%3Cuser.phoenix.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
