[
https://issues.apache.org/jira/browse/HIVE-22029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankesh updated HIVE-22029:
--------------------------
Description:
After enabling Column level masking on a Table, create table as select command
fails during preCbo planner context.
Here is the stack trace for the failure :
Caused by: java.lang.RuntimeException: java.lang.AssertionError:Unexpected type
UNEXPECTED
! at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.fixUpAfterCbo(CalcitePlanner.java:949)
! at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.genOPTree(CalcitePlanner.java:367)
! at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:11153)
! at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.analyzeInternal(CalcitePlanner.java:286)
! at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:258)
! at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:515)
! at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1320)
! at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1298)
! at
org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:204)
!
As far as my understanding, it is setting UNEXPECTED type when there is a
masked table and it do not understand what is the datatype for the column.
We are setting again the context type, but my suspect is we are not resetting
the context.
was:
After enabling Column level masking on a Table, create table as select command
fails.
Here is the stack trace for the failure :
Caused by: java.lang.RuntimeException: java.lang.AssertionError:Unexpected type
UNEXPECTED
! at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.fixUpAfterCbo(CalcitePlanner.java:949)
! at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.genOPTree(CalcitePlanner.java:367)
! at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:11153)
! at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.analyzeInternal(CalcitePlanner.java:286)
! at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:258)
! at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:515)
! at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1320)
! at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1298)
! at
org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:204)
!
As far as my understanding, it is setting UNEXPECTED type when there is a
masked table and it do not understand what is the datatype for the column.
> Create table as select throws an error for Masked enabled table
> ---------------------------------------------------------------
>
> Key: HIVE-22029
> URL: https://issues.apache.org/jira/browse/HIVE-22029
> Project: Hive
> Issue Type: Bug
> Reporter: Ankesh
> Priority: Major
>
> After enabling Column level masking on a Table, create table as select
> command fails during preCbo planner context.
>
> Here is the stack trace for the failure :
> Caused by: java.lang.RuntimeException: java.lang.AssertionError:Unexpected
> type UNEXPECTED
> ! at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.fixUpAfterCbo(CalcitePlanner.java:949)
> ! at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.genOPTree(CalcitePlanner.java:367)
> ! at
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:11153)
> ! at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.analyzeInternal(CalcitePlanner.java:286)
> ! at
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:258)
> ! at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:515)
> ! at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1320)
> ! at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1298)
> ! at
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:204)
> !
>
>
> As far as my understanding, it is setting UNEXPECTED type when there is a
> masked table and it do not understand what is the datatype for the column.
> We are setting again the context type, but my suspect is we are not resetting
> the context.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
