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

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

Github user elilevine commented on a diff in the pull request:

    https://github.com/apache/phoenix/pull/104#discussion_r36558688
  
    --- Diff: 
phoenix-core/src/main/java/org/apache/phoenix/execute/BaseQueryPlan.java ---
    @@ -204,8 +204,18 @@ public final ResultIterator iterator(final List<? 
extends SQLCloseable> dependen
             } else {
                 ScanUtil.setTimeRange(scan, context.getScanTimeRange());
             }
    -        
    -        ScanUtil.setTenantId(scan, connection.getTenantId() == null ? null 
: connection.getTenantId().getBytes());
    +        byte[] tenantIdBytes;
    --- End diff --
    
    Can you explain why you need the extra if/else here?


> 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)

Reply via email to