hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-23461) Needs to capture input/output entities in explainRewrite
Date Wed, 27 May 2020 04:20:00 GMT


Hive QA commented on HIVE-23461:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 17286 tests executed
*Failed tests:*
org.apache.hive.beeline.TestBeeLineWithArgs.testRowsAffected (batchId=210)

Test results:
Console output:
Test logs:

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
Tests exited with: TestsFailedException: 1 tests failed

This message is automatically generated.

ATTACHMENT ID: 13004078 - PreCommit-HIVE-Build

> Needs to capture input/output entities in explainRewrite
> --------------------------------------------------------
>                 Key: HIVE-23461
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Authorization
>            Reporter: Wenchao Li
>            Assignee: Naresh P R
>            Priority: Major
>         Attachments: HIVE-23461.patch
> HIVE-18778(CVE-2018-1314) capture input/output entitles in explain semantic analyzer
so when a query is disallowed by Ranger, Sentry or Sqlstd authorizizer, the corresponding
explain statement will be disallowed either.
> However, ExplainSQRewriteSemanticAnalyzer also uses an instance of DDLSemanticAnalyzer
to analyze the explain rewrite query.
> {code:java}
> SemanticAnalyzer sem = (SemanticAnalyzer)
>  SemanticAnalyzerFactory.get(queryState, input);
> sem.analyze(input, ctx);
> sem.validate();{code}
> The inputs/outputs entities for this query are never set on the instance of ExplainSQRewriteSemanticAnalyzer
itself and thus is not propagated into the HookContext in the calling Driver code. It is a
similar issue to HIVE-18778.

This message was sent by Atlassian Jira

View raw message