Skip to content

Conversation

@davies
Copy link
Contributor

@davies davies commented Aug 14, 2015

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.

@davies davies force-pushed the serialize_utf8string branch from 05b5da0 to ebeb697 Compare August 14, 2015 18:11
Copy link
Contributor Author

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?

Copy link
Contributor

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.

Copy link
Contributor Author

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is this for?

@SparkQA
Copy link

SparkQA commented Aug 14, 2015

Test build #40904 has finished for PR 8210 at commit 4ba1ac0.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • public final class UTF8String implements Comparable<UTF8String>, Externalizable

@SparkQA
Copy link

SparkQA commented Aug 14, 2015

Test build #40913 timed out for PR 8210 at commit e677bc3 after a configured wait of 175m.

@SparkQA
Copy link

SparkQA commented Aug 15, 2015

Test build #1611 timed out for PR 8210 at commit e677bc3 after a configured wait of 175m.

@SparkQA
Copy link

SparkQA commented Aug 15, 2015

Test build #1613 timed out for PR 8210 at commit e677bc3 after a configured wait of 175m.

asfgit pushed a commit that referenced this pull request Aug 15, 2015
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]>
@asfgit asfgit closed this in 7c1e568 Aug 15, 2015
CodingCat pushed a commit to CodingCat/spark that referenced this pull request Aug 17, 2015
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants