Skip to content
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

HIVE-24138. Llap external client flow is broken due to netty shading. #1491

Merged
merged 2 commits into from
Nov 23, 2020

Conversation

ayushtkn
Copy link
Member

Copy link
Contributor

@abstractdog abstractdog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

discussed on internal ticket, this looks good to me, +1

details:
by @abstractdog
" I'm absolutely fine with reverting netty shading, especially because you achieved a green test run upstream...I think, for upstream, all of the shading magic was because of testing failures, and of the suspected benefit that we would have fewer problems with netty later, but unfortunately this hasn't turned out to be the case.
More or less the upstream and downstream patch contains the same changes as far as I can see.

Can I have some minor questions/notes about the result of the patch? Otherwise, I'm about to give a +1 on this patch.

  1. UPSTREAM: Could you just confirm how did you manage to get rid of upstream test failures? I think when you removed "netty.hadoop.version" stuff from itests/qtest/pom.xml, and removed netty relocation, you made both hadoop's 4.0.52.Final and hive's 4.1.48.Final available on classpath, which was the source of all problems I had upstream. Again, I'm fine with that as long as the tests pass (as we don't release from upstream, so I only care of tests), just asking.
    If you run a mini llap local qtest, you can refer to this log message (not surprisingly, I added this line during my netty work...)

  2. What's the content of packaging/target/apache-hive-3.1.3000.7.2.3.0-SNAPSHOT-bin.tar.gz/lib/ after this patch?
    UPDATE: I've checked that currently (without the patch, on cdpd-master), there is only netty-all-4.1.48.Final.jar, and with the patch, it's the same, which is fine.
    (I'm not sure how we use the dist package in our distributions, but this way, we still won't ship double netty-all jar from hive build package, which is promising.)"

by @ayushtkn
"I ran your test on the upstream code and checked the classpath, there is all one netty-all version, which I think is same as what I wanted to achieve.
the source of having netty-all is one from hive, as it is declared as a direct dependency for hive, second is through hadoop, since it is a transitive dependency, which has a different version as that of hive, So if we let it run ideally, it should lead to two netty-versions which I guess led to failures in your case.
Now, presently while including hadoop dependencies I excluded netty-all, so the transitive dependency of netty-all isn't fetched, so instead of that version the hive dependency version is used for hadoop.
This doesn't bother Hadoop jars, as I told I confirmed it, there was no code change in hadoop for migration from 4.0 line 4.1 line and since there is only one netty-all jar, so no conflict, hence no failures.

For the 2 you already confirmed, I too confirmed it, the packaging has only one netty-all, that would be always from the hive direct dependency,"

@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the dev@hive.apache.org list if the patch is in need of reviews.

@github-actions github-actions bot added the stale label Nov 21, 2020
@ayushtkn
Copy link
Member Author

@abstractdog can you help merge this

@github-actions github-actions bot removed the stale label Nov 22, 2020
@abstractdog abstractdog merged commit c345cdf into apache:master Nov 23, 2020
ashish-kumar-sharma pushed a commit to ashish-kumar-sharma/hive that referenced this pull request Mar 31, 2022
…apache#1491) (Ayush Saxena reviewed by Laszlo Bodor)

* HIVE-24138. Llap external client flow is broken due to netty shading.
* Cleanup: Try Remove Unwanted Exclusion.
amanraj2520 pushed a commit to amanraj2520/hive that referenced this pull request Dec 13, 2022
…apache#1491) (Ayush Saxena reviewed by Laszlo Bodor)

* HIVE-24138. Llap external client flow is broken due to netty shading.
* Cleanup: Try Remove Unwanted Exclusion.

(cherry picked from commit c345cdf)

# Conflicts:
#	pom.xml
#	ql/pom.xml
amanraj2520 pushed a commit to amanraj2520/hive that referenced this pull request Dec 15, 2022
…apache#1491) (Ayush Saxena reviewed by Laszlo Bodor)

* HIVE-24138. Llap external client flow is broken due to netty shading.
* Cleanup: Try Remove Unwanted Exclusion.

(cherry picked from commit c345cdf)

# Conflicts:
#	pom.xml
#	ql/pom.xml
Diksha628 pushed a commit to Diksha628/hive that referenced this pull request Oct 19, 2023
…apache#1491) (Ayush Saxena reviewed by Laszlo Bodor)

* HIVE-24138. Llap external client flow is broken due to netty shading.
* Cleanup: Try Remove Unwanted Exclusion.
udaynpusa pushed a commit to mapr/hive that referenced this pull request Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants