-
Notifications
You must be signed in to change notification settings - Fork 409
[CELEBORN-2235][CIP-14] Adapt Java end's serialization to CppWriterClient #3561
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
[CELEBORN-2235][CIP-14] Adapt Java end's serialization to CppWriterClient #3561
Conversation
|
@SteNicholas @RexXiong @FMX @afterincomparableyum Could you kindly help review this PR? Thanks a lot. Note that this PR adds modification to Java end, which has to be carefully reviewed. Any suggestion is welcome, thanks a lot. |
|
I will take a look over the next couple of days @HolyLow, thank you for letting me know |
| serdeVersion: SerdeVersion) | ||
| extends RequestLocationCallContext with Logging { | ||
| val endedMapIds = new util.HashSet[Integer]() | ||
| val endedMapIds = new util.ArrayList[Integer]() |
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.
Why change HashSet to ArrayList? Is there a specific reason or benefit for doing so?
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.
ArrayList takes less overhead than HashSet, so here we change to use ArrayList. Besides, it is more complex to convert between HashSet and ProtoBuf's List data structure.
|
Thanks, merge to main(v0.7.0) |
What changes were proposed in this pull request?
This PR adapts Java end's serialization to CppWriterClient, including RegisterShuffle/Response, Revive/Response, MapperEnd/Response. Joint test for cpp-write java-read procedure is included as well.
Why are the changes needed?
Support writing to Celeborn server with CppWriterClient.
Does this PR resolve a correctness bug?
No.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Compilation and integration tests.