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

Hive QA commented on HIVE-21838:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12972132/HIVE-21838.2.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17641/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17641/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17641/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12972132/HIVE-21838.2.patch 
was found in seen patch url's cache and a test was probably run already on it. 
Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12972132 - PreCommit-HIVE-Build

> Hive Metastore Translation: Add API call to tell client why table has limited 
> access
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-21838
>                 URL: https://issues.apache.org/jira/browse/HIVE-21838
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Yongzhi Chen
>            Assignee: Naveen Gangam
>            Priority: Major
>         Attachments: HIVE-21838.2.patch, HIVE-21838.patch
>
>
> When a table access type is Read-only or None, we need a way to tell clients 
> why. 



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

Reply via email to