[
https://issues.apache.org/jira/browse/PHOENIX-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782043#comment-15782043
]
Jeremy Huffman commented on PHOENIX-3547:
-----------------------------------------
The limitation with the VIEW_INDEX_ID doesn't cause a problem for me if I use
multi-tenant tables, because then the limitation is per tenant.
It is only an issue if I don't use the tenant feature of Phoenix but still have
logical tenants in my application layer. Then the limit is a problem because it
is a global limit.
That is why I can either solve my problem with a larger VIEW_INDEX_ID or some
more flexibility in the sharing of tenant tables, I don't really need both. I
will write up a separate Jira for that use case and include an example to make
it more clear.
> 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
> Priority: Minor
>
> 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
(v6.3.4#6332)
