You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (JIRA)" <ji...@apache.org> on 2018/02/14 23:36:00 UTC

[jira] [Commented] (PHOENIX-4607) Allow PhoenixInputFormat to use tenant-specific connections

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

Geoffrey Jacoby commented on PHOENIX-4607:
------------------------------------------

[~jamestaylor], if MapReduce selects can use tenant-specific connections, will we automatically get the ability to use a tenant-view in the FROM clause of a MapReduce SELECT?

> Allow PhoenixInputFormat to use tenant-specific connections
> -----------------------------------------------------------
>
>                 Key: PHOENIX-4607
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4607
>             Project: Phoenix
>          Issue Type: New Feature
>    Affects Versions: 4.13.0
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>
> When using Phoenix's MapReduce integration, the actual connections for the SELECT query are created by PhoenixInputFormat. While PhoenixInputFormat has support for a few connection properties such as SCN, a TenantId is not one of them. 
> Add the ability to specify a TenantId for the PhoenixInputFormat's connections to use. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)