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/03/01 21:39:00 UTC
[jira] [Updated] (PHOENIX-4607) Allow PhoenixInputFormat to use
tenant-specific connections
[ https://issues.apache.org/jira/browse/PHOENIX-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoffrey Jacoby updated PHOENIX-4607:
-------------------------------------
Attachment: PHOENIX-4607-v2.patch
> 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)