[
https://issues.apache.org/jira/browse/HIVE-19569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507563#comment-16507563
]
Hive QA commented on HIVE-19569:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12927194/HIVE-19569.02.patch
{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 10 failed/errored test(s), 14437 tests
executed
*Failed tests:*
{noformat}
TestBeeLineExceptionHandling - did not produce a TEST-*.xml file (likely timed
out) (batchId=193)
TestBeeLineHistory - did not produce a TEST-*.xml file (likely timed out)
(batchId=193)
TestBeelineArgParsing - did not produce a TEST-*.xml file (likely timed out)
(batchId=193)
TestClientCommandHookFactory - did not produce a TEST-*.xml file (likely timed
out) (batchId=193)
TestHiveCli - did not produce a TEST-*.xml file (likely timed out) (batchId=193)
TestHiveSchemaTool - did not produce a TEST-*.xml file (likely timed out)
(batchId=193)
TestIncrementalRows - did not produce a TEST-*.xml file (likely timed out)
(batchId=193)
TestShutdownHook - did not produce a TEST-*.xml file (likely timed out)
(batchId=193)
TestTableOutputFormat - did not produce a TEST-*.xml file (likely timed out)
(batchId=193)
org.apache.hadoop.hive.ql.stats.TestStatsUpdaterThread.testQueueingWithThreads
(batchId=276)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/11693/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11693/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11693/
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
Tests exited with: TestsFailedException: 10 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12927194 - PreCommit-HIVE-Build
> alter table db1.t1 rename db2.t2 generates
> MetaStoreEventListener.onDropTable()
> -------------------------------------------------------------------------------
>
> Key: HIVE-19569
> URL: https://issues.apache.org/jira/browse/HIVE-19569
> Project: Hive
> Issue Type: Bug
> Components: Metastore, Standalone Metastore, Transactions
> Affects Versions: 3.0.0
> Reporter: Eugene Koifman
> Assignee: mahesh kumar behera
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-19569.01.patch, HIVE-19569.02.patch
>
>
> When renaming a table within the same DB, this operation causes
> {{MetaStoreEventListener.onAlterTable()}} to fire but when changing DB name
> for a table it causes {{MetaStoreEventListener.onDropTable()}} +
> {{MetaStoreEventListener.onCreateTable()}}.
> The files from original table are moved to new table location.
> This creates confusing semantics since any logic in {{onDropTable()}} doesn't
> know about the larger context, i.e. that there will be a matching
> {{onCreateTable()}}.
> In particular, this causes a problem for Acid tables since files moved from
> old table use WriteIDs that are not meaningful with the context of new table.
> Current implementation is due to replication. This should ideally be changed
> to raise a "not supported" error for tables that are marked for replication.
> cc [~sankarh]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
