You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2019/04/24 22:33:00 UTC

[jira] [Commented] (PHOENIX-5168) IndexScrutinyTool cannot output to table when analyzing tenant-owned indexes

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

Hadoop QA commented on PHOENIX-5168:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12966940/PHOENIX-5168.patch
  against master branch at commit a3fbbb8fa098ae1420823bc03e5f9b5203a22962.
  ATTACHMENT ID: 12966940

    {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:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:red}-1 release audit{color}.  The applied patch generated 6 release audit warnings (more than the master's current 0 warnings).

    {color:red}-1 lineLengths{color}.  The patch introduces the following lines longer than 100:
    +            ResultSet count = conn.createStatement().executeQuery("select count(*) from " + tableFullName);
+                    getArgValues("", tenantViewName, indexNameTenant, 10L, SourceTable.DATA_TABLE_SOURCE, true, outputFormat, null,
+                try (Connection outputConn = ConnectionUtil.getOutputConnection(outputConfiguration)) {

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexSplitForwardScanIT

Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/2529//testReport/
Release audit warnings: https://builds.apache.org/job/PreCommit-PHOENIX-Build/2529//artifact/patchprocess/patchReleaseAuditWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/2529//console

This message is automatically generated.

> IndexScrutinyTool cannot output to table when analyzing tenant-owned indexes
> ----------------------------------------------------------------------------
>
>                 Key: PHOENIX-5168
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5168
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Gokcen Iskender
>            Assignee: Gokcen Iskender
>            Priority: Major
>         Attachments: PHOENIX-5168.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> IndexScrutiny has a new feature of using tenant connections (when tenant-Id parameter is used) to lookup the indexes on tenant views.
> When tenant-id option is provided and output-format is set to TABLE, we get an error that PHOENIX_SCRUTINY_TABLE cannot be created due to permission. 
> We should be able to output to a table when tenant-id option is used.
> Note that output-format set to FILE is supported.
>  



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