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

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



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

{color:green}SUCCESS:{color} +1 due to 10 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 16686 tests passed

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12975837 - 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.10.patch, HIVE-21838.11.patch, 
> HIVE-21838.12.patch, HIVE-21838.13.patch, HIVE-21838.13.patch, 
> HIVE-21838.2.patch, HIVE-21838.3.patch, HIVE-21838.4.patch, 
> HIVE-21838.5.patch, HIVE-21838.6.patch, HIVE-21838.7.patch, 
> HIVE-21838.8.patch, HIVE-21838.9.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.14#76016)

Reply via email to