-
Notifications
You must be signed in to change notification settings - Fork 28.7k
[SPARK-4261][BUILD][SQL] Make right version info for beeline #3124
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
More detail discuss link to #3103 |
Test build #22969 has started for PR 3124 at commit
|
Test build #22969 has finished for PR 3124 at commit
|
Test PASSed. |
@@ -95,6 +95,30 @@ | |||
<skip>true</skip> | |||
</configuration> | |||
</plugin> | |||
<!-- Deploy datanucleus jars to the spark/lib_managed/jars directory --> |
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.
fix this
Test build #22989 has started for PR 3124 at commit
|
Updated and locally test ok. With this PR the output will be
|
<plugin> | ||
<groupId>org.apache.maven.plugins</groupId> | ||
<artifactId>maven-dependency-plugin</artifactId> | ||
<version>2.4</version> |
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.
Nit: you should just inherit version config from the parent pom
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.
Seems there is no maven-dependency-plugin version in parent Pom? @srowen
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.
Oh, hm. I suggest adding it in <pluginManagement>
-- just with the version. Also, use 2.9, not 2.4.
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.
Ok
Test build #22989 has finished for PR 3124 at commit
|
Test PASSed. |
Updated. |
Test build #22995 has started for PR 3124 at commit
|
Test build #22995 has finished for PR 3124 at commit
|
Test PASSed. |
@pwendell, can you take a look at this? |
Test build #23035 has started for PR 3124 at commit
|
Test build #23035 has finished for PR 3124 at commit
|
Test PASSed. |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
@pwendell any thoughts on the build changes here? |
ping @pwendell |
ping |
1 similar comment
ping |
Is Hive reading the version from a manifest somewhere? It's sort of unfortunate to have to increase the number of special case jars for a cosmetic change like this. Can we instead just add the relevant manifest file to our assembly? |
Hi @pwendell, Beeline relies on the
which is same with manifest of SBT assembly jar. The problem of using assembly jar is that Hive beeline version will be We can not read the right version if using assembly jar |
Test build #24409 has started for PR 3124 at commit
|
Test build #24409 has finished for PR 3124 at commit
|
Test PASSed. |
Ping |
1 similar comment
Ping |
I also disagree with this change, as it seems to be saying we should declare Spark's version in the Manifest to be incorrect, and match Beeline's, just to fix a cosmetic issue. |
ok, I am closing this since this issue do not affect functional and as @srowen said it is a "cosmetic issue" |
More detail discuss link to #3103
Build spark with maven, then use beeline to connect jdbc/odbc server, the output will be
This PR make right version info for beeline by excluding hive-beeline from the assembly jar, and deliver it as a separate jar to "lib_managed/jars", a WIP tag here is because i have not tested this locally.