[
https://issues.apache.org/jira/browse/PHOENIX-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967864#comment-16967864
]
Lars Hofhansl commented on PHOENIX-3547:
----------------------------------------
[~rajeshbabu] that could work.
An earlier patch I had on PHOENIX-5486 (still attached to the issue, it's -v3)
always has the sequence start at Short.MIN_VALUE. We lose the negative space
from Long, but I assume that 2bn+32k views are plenty per table. We could
revive that code. Two sequences might be a smarter way to solve this.
Note that PHOENIX-5559 is somehow caused by the client encoding the viewIndexId
into a short, thus sending the same value for different indexes. That *might*
be solved by this as well, since we won't be trying to encode Longs down to
Shorts. I have attached a test case to PHOENIX-5559 that shows the issues. If
these two tests pass, I'd feel reasonably good.
> 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)
