[ https://issues.apache.org/jira/browse/HIVE-10630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555373#comment-14555373 ]
Eugene Koifman commented on HIVE-10630: --------------------------------------- Committed to master and 1.2.1 > Renaming tables across encryption zones renames table even though the > operation throws error > -------------------------------------------------------------------------------------------- > > Key: HIVE-10630 > URL: https://issues.apache.org/jira/browse/HIVE-10630 > Project: Hive > Issue Type: Sub-task > Components: Metastore, Security > Reporter: Deepesh Khandelwal > Assignee: Eugene Koifman > Fix For: 1.3.0, 1.2.1 > > Attachments: HIVE-10630.patch > > > Create a table with data in an encrypted zone 1 and then rename it to > encrypted zone 2. > {noformat} > hive> alter table encdb1.testtbl rename to encdb2.testtbl; > FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.DDLTask. Unable to alter table. Unable to > access old location > hdfs://node-1.example.com:8020/apps/hive/warehouse/encdb1.db/testtbl for > table encdb1.testtbl > {noformat} > Even though the command errors out the table is renamed. I think the right > behavior should be to not rename the table at all including the metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)