phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1673) Allow tenant ID to be of any integral data type
Date Wed, 12 Aug 2015 18:20:45 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693965#comment-14693965
] 

ASF GitHub Bot commented on PHOENIX-1673:
-----------------------------------------

Github user elilevine commented on the pull request:

    https://github.com/apache/phoenix/pull/104#issuecomment-130400117
  
    Good stuff, @JeffreyLyonsD2L! One last thing: can you update this pull request so it merges
with Phoenix master cleanly (there are some conflicts now)? Also, would be great to see a
PR for one of the 4.x branches if this patch does not merge cleanly there. You don't need
to do it for each 4.x branch, one is fine. I'll take care of the rest. Again, thank you for
your contributions.


> 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
>            Assignee: Jeffrey Lyons
>              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)

Mime
View raw message