[
https://issues.apache.org/jira/browse/HIVE-11205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619006#comment-14619006
]
Hive QA commented on HIVE-11205:
--------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12744176/HIVE-11205.patch
{color:green}SUCCESS:{color} +1 9136 tests passed
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4537/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4537/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-4537/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12744176 - PreCommit-HIVE-TRUNK-Build
> Unable to create table being in read-only database
> --------------------------------------------------
>
> Key: HIVE-11205
> URL: https://issues.apache.org/jira/browse/HIVE-11205
> Project: Hive
> Issue Type: Bug
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Mariusz Strzelecki
> Assignee: Mariusz Strzelecki
> Attachments: HIVE-11205.patch
>
>
> With enabled Legacy Authorization I cannot create table being in database
> that is read-only to me. For example:
> {noformat}
> > use ro_db;
> No rows affected (1.222 seconds)
> > create table rw_db.test (s string);
> Error: Error while compiling statement: No privilege 'Create' found for
> outputs { database:ro_db} (state=42000,code=403)
> > use rw_db;
> No rows affected (0.407 seconds)
> > create table rw_db.test (s string);
> No rows affected (2.216 seconds)
> {noformat}
> This happens because doAuthorization method checks write permissions against
> current database and then againts output database. Check for current database
> is not needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
