[SPARK-27858][SQL] Fix for avro deserialization on union types with multiple non-null types #24722
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gcmerz
changed the title
Member
|
Thank you for your first contribution, @gcmerz ! |
Member
|
ok to test |
|
Test build #105850 has finished for PR 24722 at commit
|
external/avro/src/test/scala/org/apache/spark/sql/avro/AvroSuite.scala
Outdated
Show resolved
Hide resolved
dongjoon-hyun
changed the title
external/avro/src/test/scala/org/apache/spark/sql/avro/AvroSuite.scala
Outdated
Show resolved
Hide resolved
dongjoon-hyun
requested changes
May 28, 2019
Member
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
I left two minor comments on the test case. Could you update them? Also, I updated the PR title and description a little bit.
Member
|
cc @dbtsai and @gengliangwang |
Author
|
Applied the tweaks--thank you so much for the quick review! |
Member
|
You're welcome. Thank you for swift update. |
|
Test build #105855 has finished for PR 24722 at commit
|
Member
|
Merged to |
dongjoon-hyun
pushed a commit
that referenced
this pull request
May 28, 2019
…ultiple non-null types ## What changes were proposed in this pull request? This PR aims to fix an issue on a union avro type with more than one non-null value (for instance `["string", "null", "int"]`) whose the deserialization to a DataFrame would throw a `java.lang.ArrayIndexOutOfBoundsException`. The issue was that the `fieldWriter` relied on the index from the avro schema before nulls were filtered out. ## How was this patch tested? A test for the case of multiple non-null values was added and the tests were run using sbt by running `testOnly org.apache.spark.sql.avro.AvroSuite` Closes #24722 from gcmerz/master. Authored-by: Gabbi Merz <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 29e154b) Signed-off-by: Dongjoon Hyun <[email protected]>
Member
|
@gcmerz . What is your id in Apache JIRA? If you don't have, please create one. Then, I can assign that issue to you. And, FYI, in GitHub personal setting, you can additionally add your Palantir email (used in this PR). Then, your commit with Palantir ID also will show your GitHub profile. |
Member
|
A late LGTM! Thanks for the fix @gcmerz |
Author
|
@dongjoon-hyun Made a Jira account with username "gcmerz" and added palantir email. Thanks again! |
Member
|
It's assigned to you, @gcmerz . Welcome to the Apache Spark community! |
Member
|
Thank you for review, @gengliangwang . |
vinooganesh
pushed a commit
to palantir/spark
that referenced
this pull request
May 28, 2019
…ultiple non-null types ## What changes were proposed in this pull request? This PR aims to fix an issue on a union avro type with more than one non-null value (for instance `["string", "null", "int"]`) whose the deserialization to a DataFrame would throw a `java.lang.ArrayIndexOutOfBoundsException`. The issue was that the `fieldWriter` relied on the index from the avro schema before nulls were filtered out. ## How was this patch tested? A test for the case of multiple non-null values was added and the tests were run using sbt by running `testOnly org.apache.spark.sql.avro.AvroSuite` Closes apache#24722 from gcmerz/master. Authored-by: Gabbi Merz <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
rluta
pushed a commit
to rluta/spark
that referenced
this pull request
Sep 17, 2019
…ultiple non-null types ## What changes were proposed in this pull request? This PR aims to fix an issue on a union avro type with more than one non-null value (for instance `["string", "null", "int"]`) whose the deserialization to a DataFrame would throw a `java.lang.ArrayIndexOutOfBoundsException`. The issue was that the `fieldWriter` relied on the index from the avro schema before nulls were filtered out. ## How was this patch tested? A test for the case of multiple non-null values was added and the tests were run using sbt by running `testOnly org.apache.spark.sql.avro.AvroSuite` Closes apache#24722 from gcmerz/master. Authored-by: Gabbi Merz <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 29e154b) Signed-off-by: Dongjoon Hyun <[email protected]>
kai-chi
pushed a commit
to kai-chi/spark
that referenced
this pull request
Sep 26, 2019
…ultiple non-null types ## What changes were proposed in this pull request? This PR aims to fix an issue on a union avro type with more than one non-null value (for instance `["string", "null", "int"]`) whose the deserialization to a DataFrame would throw a `java.lang.ArrayIndexOutOfBoundsException`. The issue was that the `fieldWriter` relied on the index from the avro schema before nulls were filtered out. ## How was this patch tested? A test for the case of multiple non-null values was added and the tests were run using sbt by running `testOnly org.apache.spark.sql.avro.AvroSuite` Closes apache#24722 from gcmerz/master. Authored-by: Gabbi Merz <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 29e154b) Signed-off-by: Dongjoon Hyun <[email protected]>
otterc
pushed a commit
to linkedin/spark
that referenced
this pull request
Mar 22, 2023
…ultiple non-null types ## What changes were proposed in this pull request? This PR aims to fix an issue on a union avro type with more than one non-null value (for instance `["string", "null", "int"]`) whose the deserialization to a DataFrame would throw a `java.lang.ArrayIndexOutOfBoundsException`. The issue was that the `fieldWriter` relied on the index from the avro schema before nulls were filtered out. ## How was this patch tested? A test for the case of multiple non-null values was added and the tests were run using sbt by running `testOnly org.apache.spark.sql.avro.AvroSuite` Closes apache#24722 from gcmerz/master. Authored-by: Gabbi Merz <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 29e154b) RB=2633258 G=spark-reviewers R=ekrogen,wyzhang,wmoustaf A=ekrogen
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to fix an issue on a union avro type with more than one non-null value (for instance
["string", "null", "int"]) whose the deserialization to a DataFrame would throw ajava.lang.ArrayIndexOutOfBoundsException. The issue was that thefieldWriterrelied on the index from the avro schema before nulls were filtered out.How was this patch tested?
A test for the case of multiple non-null values was added and the tests were run using sbt by running
testOnly org.apache.spark.sql.avro.AvroSuite