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

Hudson commented on PHOENIX-4607:
---------------------------------

ABORTED: Integrated in Jenkins build PreCommit-PHOENIX-Build #1781 (See 
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/1781/])
PHOENIX-4607 - Allow PhoenixInputFormat to use tenant-specific (gjacoby: rev 
a35591c876ddb338cdb8269e67aed92ed6e5d485)
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/util/PhoenixConfigurationUtil.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/util/PhoenixMapReduceUtil.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/MapReduceIT.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/PhoenixInputFormat.java


> 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
>             Fix For: 4.14.0, 5.0.0
>
>         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)

Reply via email to