[
https://issues.apache.org/jira/browse/PHOENIX-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662674#comment-14662674
]
ASF GitHub Bot commented on PHOENIX-1673:
-----------------------------------------
Github user JamesRTaylor commented on the pull request:
https://github.com/apache/phoenix/pull/104#issuecomment-128863633
This feature would allow the tenant ID to be represented through more types
than just a VARCHAR. Some users may have tenants identified by an int or a long
instead of a string. The tenant ID would still be passed as the stringified
value, but the underlying table could use an int or a long as the column type.
As you mentioned, the system tables (SYSTEM.CATALOG and SYSTEM.SEQUENCE) would
need to continue to use the string representation. Every type can be converted
to a string, so this should be ok (pending testing).
> Allow tenant ID to be of any integral data type
> -----------------------------------------------
>
> Key: PHOENIX-1673
> URL: https://issues.apache.org/jira/browse/PHOENIX-1673
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.3.0
> Reporter: Mark Tse
> Labels: Newbie, multi-tenant
> Fix For: 4.4.1
>
>
> When creating multi-tenant tables and views, the column that identifies the
> tenant (first primary key column) must be of type 'VARCHAR' or 'CHAR'.
> It should be possible to relax this restriction to use any integral data
> type. The tenant ID from the connection property can be converted based on
> the data type of the first primary key column.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
