-
Notifications
You must be signed in to change notification settings - Fork 4.8k
HIVE-24553. Exclude calcite from test-jar dependency of hive-exec #1794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@sunchao Looks like "testSetHeaderValue – org.apache.hive.beeline.cli.TestHiveCli" was passed now in CI. |
@sunchao Please let me know if you think this is good to merge. I will create a JIRA for this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -99,6 +99,20 @@ | |||
<version>${project.version}</version> | |||
<classifier>tests</classifier> | |||
<scope>test</scope> | |||
<exclusions> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good as I no longer see the test failure 👍 . BTW do you know why we need to exclude calcite here but not in other places where hive-exec
is also used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the test-jar won't include shaded dependencies. Then un-shaded dependencies will be pull. So I think we need to exclude them.
If there are other places using hive-exec in test scope, I think they might also need to exclude these.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I see. I think there are a few other places with similar pattern, such as hive-webhcat-java-client
. Should we exclude in all those places?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, I think so. I will update this later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated all hive-exec test-jar usage in all pom.xml files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1. Can you create a JIRA for this? I'm not sure if master branch also have this issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created a JIRA. Updated the title and description.
Hmm, okay. Just stuck without any error/exception? Then it seems harder to figure out the reason. |
Yes just stuck without any error/exception. Thread dump also doesn't give much information which is interesting. |
OK. I tried to bump Accumulo version to 1.7.3 (the one used by master branch) and I got the exception:
as in #1792. So perhaps with Accumulo 1.6.0 the exception got swallowed silently and therefore test got stuck. After applying patch there together with the version bump the issue seems gone, but without version bump it will still stuck for unknown reason. I'll update #1792 with this change. |
Thanks. @sunchao |
So sounds like the stuck seems related to Accumulo version? |
Yes seems so although I don't know the exact reason yet. There is also another JIRA mentioning a similar test stuck issue when upgrading Accumulo from 1.7.3 to 1.8.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Will merge shortly.
Thanks @sunchao |
What changes were proposed in this pull request?
This patch proposes to exclude calcite dependencies from test-jar dependency of
hive-exec
.Why are the changes needed?
The test "org.apache.hive.beeline.cli.TestHiveCli - testSetHeaderValue" we found the exception:
This looks like adding dependency of test-jar of
hive-exec
pulls in the unshaded calcite dependencies which conflicts with shaded calcite. We should exclude unshaded calcite when adding test-jar ofhive-exec
.Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit test.