[
https://issues.apache.org/jira/browse/HIVE-19569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508614#comment-16508614
]
Hive QA commented on HIVE-19569:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12927260/HIVE-19569.03.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/11714/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11714/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11714/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hiveptest/working/scratch/source-prep.sh' failed with exit
status 1 and output '+ date '+%Y-%m-%d %T.%3N'
2018-06-11 19:33:12.670
+ [[ -n /usr/lib/jvm/java-8-openjdk-amd64 ]]
+ export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
+ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
+ export
PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
+
PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'MAVEN_OPTS=-Xmx1g '
+ MAVEN_OPTS='-Xmx1g '
+ cd /data/hiveptest/working/
+ tee /data/hiveptest/logs/PreCommit-HIVE-Build-11714/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ git = \s\v\n ]]
+ [[ git = \g\i\t ]]
+ [[ -z master ]]
+ [[ -d apache-github-source-source ]]
+ [[ ! -d apache-github-source-source/.git ]]
+ [[ ! -d apache-github-source-source ]]
+ date '+%Y-%m-%d %T.%3N'
2018-06-11 19:33:12.673
+ cd apache-github-source-source
+ git fetch origin
>From https://github.com/apache/hive
9f54302..8902563 master -> origin/master
2b5e215..66ed015 branch-3 -> origin/branch-3
+ git reset --hard HEAD
HEAD is now at 9f54302 HIVE-19237: addendum to fix HIVE-19789
+ git clean -f -d
+ git checkout master
Already on 'master'
Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
+ git reset --hard origin/master
HEAD is now at 8902563 HIVE-19833 : reduce LLAP IO min allocation to match ORC
variable CB size (Sergey Shelukhin, reviewed by Gopal Vijayaraghavan)
+ git merge --ff-only origin/master
Already up-to-date.
+ date '+%Y-%m-%d %T.%3N'
2018-06-11 19:33:14.848
+ rm -rf ../yetus_PreCommit-HIVE-Build-11714
+ mkdir ../yetus_PreCommit-HIVE-Build-11714
+ git gc
+ cp -R . ../yetus_PreCommit-HIVE-Build-11714
+ mkdir /data/hiveptest/logs/PreCommit-HIVE-Build-11714/yetus
+ patchCommandPath=/data/hiveptest/working/scratch/smart-apply-patch.sh
+ patchFilePath=/data/hiveptest/working/scratch/build.patch
+ [[ -f /data/hiveptest/working/scratch/build.patch ]]
+ chmod +x /data/hiveptest/working/scratch/smart-apply-patch.sh
+ /data/hiveptest/working/scratch/smart-apply-patch.sh
/data/hiveptest/working/scratch/build.patch
error: a/ql/src/test/org/apache/hadoop/hive/ql/TestTxnConcatenate.java: does
not exist in index
error:
a/standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java:
does not exist in index
error:
a/standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java:
does not exist in index
error:
a/standalone-metastore/src/test/java/org/apache/hadoop/hive/metastore/client/TestTablesCreateDropAlterTruncate.java:
does not exist in index
error: patch failed:
standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java:22
Falling back to three-way merge...
Applied patch to
'standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java'
cleanly.
error: patch failed:
standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java:3944
Falling back to three-way merge...
Applied patch to
'standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java'
with conflicts.
Going to apply patch with: git apply -p1
error: patch failed:
standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java:22
Falling back to three-way merge...
Applied patch to
'standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java'
cleanly.
error: patch failed:
standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java:3944
Falling back to three-way merge...
Applied patch to
'standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java'
with conflicts.
U
standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java
+ result=1
+ '[' 1 -ne 0 ']'
+ rm -rf yetus_PreCommit-HIVE-Build-11714
+ exit 1
'
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12927260 - 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,
> HIVE-19569.03.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)
