-
Notifications
You must be signed in to change notification settings - Fork 440
TEZ-1037: Replace multiple members in TaskAttemptImpl for container related stuff with a single reference to the container. #305
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
…elated stuff with a single reference to the container. Change-Id: I987e92f3cc504f0701a2b7ebde53aac62daf84fc
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
I have 3 checkstyle warnings, 2 for unused import, I will fix it. One for creating getter/setter, which looks overkill to me for test purpose and to make checkstyle happy. |
Change-Id: Ibee2288595810c5330181a6eb416ff34bdd283fd
|
🎊 +1 overall
This message was automatically generated. |
|
I can see that we're doing lots of interning stuff in the TaskAttemptImpl, which kind of looks like boilerplate from the TaskAttempImpl class' point of view let it be: basically, a new TezContainer (or name it as you like) class can have all these fields that you're about to remove from TaskAttemptImpl optionally: look for usages of org.apache.hadoop.yarn.api.records.Container in tez code and remove it from there too (it can be done in followup tickets) |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
@abstractdog I have addressed the review comments, added a new TezContainer Class & pushed the methods there, let me know if it looks good. One checkstyle is left intentionally, that visibility is changed for test & satisfying that looked like an overkill |
| import org.apache.hadoop.yarn.util.RackResolver; | ||
| import org.apache.tez.util.StringInterner; | ||
|
|
||
| public class TezContainer extends Container { |
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.
please add a class javadoc comment clarifying the purpose of this class
which is basically to have a convenience wrapper around org.apache.hadoop.yarn.api.records.Container
everything looks good, left a minor comment about TezContainer, otherwise +1 |
|
🎊 +1 overall
This message was automatically generated. |
…elated stuff with a single reference to the container. (apache#305) (Ayush Saxena reviewed by Laszlo Bodor) (cherry picked from commit 4b97acb)
…tainer related stuff with a single reference to the container. (apache#305) (Ayush Saxena reviewed by Laszlo Bodor)" This reverts commit 5baad9a.
…tainer related stuff with a single reference to the container. (apache#305) (Ayush Saxena reviewed by Laszlo Bodor)" This reverts commit 4b97acb.
No description provided.