-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-9725] [SQL] fix serialization of UTF8String across different JVM #8210
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
05b5da0 to
ebeb697
Compare
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.
Is there a way to still having them as final?
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.
See if you can use Externalizable instead.
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.
Externalizable still need them to be non-final. Should we use UNSAFE here? Not sure about the performance difference about final and non-final.
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.
what is this for?
|
Test build #40904 has finished for PR 8210 at commit
|
|
Test build #40913 timed out for PR 8210 at commit |
|
Test build #1611 timed out for PR 8210 at commit |
|
Test build #1613 timed out for PR 8210 at commit |
The BYTE_ARRAY_OFFSET could be different in JVM with different configurations (for example, different heap size, 24 if heap > 32G, otherwise 16), so offset of UTF8String is not portable, we should handler that during serialization. Author: Davies Liu <[email protected]> Closes #8210 from davies/serialize_utf8string. (cherry picked from commit 7c1e568) Signed-off-by: Davies Liu <[email protected]>
The BYTE_ARRAY_OFFSET could be different in JVM with different configurations (for example, different heap size, 24 if heap > 32G, otherwise 16), so offset of UTF8String is not portable, we should handler that during serialization. Author: Davies Liu <[email protected]> Closes apache#8210 from davies/serialize_utf8string.
The BYTE_ARRAY_OFFSET could be different in JVM with different configurations (for example, different heap size, 24 if heap > 32G, otherwise 16), so offset of UTF8String is not portable, we should handler that during serialization.