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

Hadoop QA commented on PHOENIX-4940:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12958107/PHOENIX-4940-4.x.patch
  against master branch at commit 0d44f7625a7958d58fa596bdd0da67ff501da84c.
  ATTACHMENT ID: 12958107

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2323//console

This message is automatically generated.

> IndexTool should be able to rebuild tenant-owned indexes
> --------------------------------------------------------
>
>                 Key: PHOENIX-4940
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4940
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.14.0, 5.0.0
>            Reporter: Geoffrey Jacoby
>            Assignee: Gokcen Iskender
>            Priority: Major
>         Attachments: PHOENIX-4940-4.x.patch, PHOENIX-4940-addendum.patch
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> IndexTool uses global connections to lookup the indexes which it's asked to 
> rebuild, which means that it won't be able to see indexes owned by tenant 
> views. We should add an optional tenantId parameter to it that will use a 
> tenant connection (and potentially our MapReduce framework's tenant 
> connection support) to allow for rebuilding those indexes as well. 



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

Reply via email to