-
Notifications
You must be signed in to change notification settings - Fork 440
TEZ-4650: Remove useless logic from AM plugin management: processSchedulerDescriptors #433
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
8bee6d7 to
10f2d44
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
apparently, there is a failing case: I'm going to investigate this: it seems like this unit test asserts that the yarn plugin descriptor is hacked to the entities even when enableYarn:false, so the application expects it to be present in non-local mode, even when containersEnabled=false...which still seems quite hacky, need to understand what use case this unit test covers EDIT: in the only 1 known custom plugin use-case, which is Hive LLAP, Hive sets the descriptor to enableYarn:true: tez/tez-api/src/main/java/org/apache/tez/serviceplugins/api/ServicePluginsDescriptor.java Line 138 in 0a5c714
so, this unit test doesn't cover a known use-case |
This comment was marked as outdated.
This comment was marked as outdated.
532f0f1 to
d5bfce2
Compare
|
🎊 +1 overall
This message was automatically generated. |
ayushtkn
left a comment
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
See: jira description
Additional local testing:
Also tez has unit test coverage in this area: in case it's green, this patch is safe.