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

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

HadoopQA doesn't seem to be posting to the JIRA, but the test run did occur. 
There were 10 test failures, listed here:

[https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-PHOENIX-Build/1766/#showFailuresLink]

When I run mvn clean verify locally, I can reproduce all the test failures, so 
they're not flappers – but the same test failures occur if I run mvn clean 
verify from an unchanged pull of the master branch. So, while we all seem due 
for another round of test cleanup, this patch should be fine.

[~jamestaylor], wdyt?

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