phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4607) Allow PhoenixInputFormat to use tenant-specific connections
Date Thu, 01 Mar 2018 21:41:00 GMT

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

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

I noticed that there was a pre-existing connection leak in PhoenixInputFormat (the non-Hive
version, so different from PHOENIX-4635), so I fixed it and made a v2. 

 

> 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
>              Labels: mapreduce
>         Attachments: PHOENIX-4607-v2.patch, PHOENIX-4607.patch
>
>
> 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)

Mime
View raw message