-
Notifications
You must be signed in to change notification settings - Fork 424
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
TEZ-4548: InputDataInformationEvent to be read from serialized payload from filesystem #341
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
c583b70
to
bca30d1
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.
@ayushtkn : can you please take a look at this one? |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
tez-api/src/main/java/org/apache/tez/runtime/api/events/InputDataInformationEvent.java
Show resolved
Hide resolved
tez-api/src/main/java/org/apache/tez/runtime/api/events/InputDataInformationEvent.java
Outdated
Show resolved
Hide resolved
…d from filesystem
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
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.
few comments
tez-api/src/main/java/org/apache/tez/runtime/api/events/InputDataInformationEvent.java
Outdated
Show resolved
Hide resolved
tez-api/src/main/java/org/apache/tez/runtime/api/InputInitializerContext.java
Show resolved
Hide resolved
tez-mapreduce/src/main/java/org/apache/tez/mapreduce/hadoop/MRInputHelpers.java
Outdated
Show resolved
Hide resolved
tez-mapreduce/src/main/java/org/apache/tez/mapreduce/hadoop/MRInputHelpers.java
Show resolved
Hide resolved
tez-mapreduce/src/main/java/org/apache/tez/mapreduce/hadoop/MRInputHelpers.java
Outdated
Show resolved
Hide resolved
tez-mapreduce/src/test/java/org/apache/tez/mapreduce/hadoop/TestMRInputHelpers.java
Outdated
Show resolved
Hide resolved
tez-mapreduce/src/test/java/org/apache/tez/mapreduce/hadoop/TestMRInputHelpers.java
Outdated
Show resolved
Hide resolved
proto.hasUserPayload() ? proto.getUserPayload().asReadOnlyByteBuffer() : null); | ||
ByteBuffer payload = proto.hasUserPayload() ? proto.getUserPayload().asReadOnlyByteBuffer() : null; | ||
InputDataInformationEvent diEvent = null; | ||
if (!proto.getSerializedPath().isEmpty()) { |
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.
At this point, there maybe a possibility that payload wasn't null
as well, but we ignored that because there was a serializedPath
?
Should we throw out in that case?
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.
idea was: if there is serializedPath, we just use it and don't care about payload, we should have one or another, not both
I think the static InputDataInformationEvent creator methods take care of not having both
is it fine?
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.
should be ok if it can never reach & there is no public method which can reach here, else maybe we can have Preconditions or Assert to see we don't land up having two source of truth accidentally even in future, but I am ok
tez-runtime-internals/src/main/java/org/apache/tez/common/ProtoConverters.java
Outdated
Show resolved
Hide resolved
This comment was marked as outdated.
This comment was marked as outdated.
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.
Thanx @abstractdog for the update. There are some checkstyle warnings can you take care of them, rest things LGTM
thanks! I cannot address [HiddenField], I consider it as noise now let me know if it's fine |
@abstractdog that HiddenField should be fixable, it is telling you have localFs already defined above & you are redefining the same variable name in the test method, rather than using the class variable
Just remove that line |
This comment was marked as outdated.
This comment was marked as outdated.
LOL, right, I haven't checked it in detail, I thought it was the another checkstyle warning which is usually a noise :) fixed in 9dce61e |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
🎊 +1 overall
This message was automatically generated. |
tests passed green |
This patch implements the tez side of the scenario described in HIVE-28165 + TEZ-4548.
tez-api changes:
tez-runtime-internals:
tez-mapreduce changes:
testing: tested on cluster (together with HIVE-28165), solved an OOM issue, also tez unit tests added