-
Notifications
You must be signed in to change notification settings - Fork 29.1k
[SPARK-49406][SQL][TESTS] Add three test cases for from_avro/to_avro from the perspective of GenericRecord
#47888
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
…from the perspective of `GenericRecord`
|
cc @MaxGekk |
MaxGekk
left a comment
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.
| record | ||
| } | ||
|
|
||
| test("GenericRecord serialize/deserialize") { |
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.
Does this test check Spark's code? If not, let's remove it.
| } | ||
| } | ||
|
|
||
| test("use `to_avro` to read GenericRecord(stored in `struct` datatype)") { |
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.
to read? it should write, shouldn't it?
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.
I have refactored this code and it seems clearer now. Please help review it again in your free time, thanks!
from_avro/to_avro from the perspective of GenericRecordfrom_avro/to_avro from the perspective of GenericRecord
|
+1, LGTM. Merging to master. |
Thanks @MaxGekk. |
What changes were proposed in this pull request?
The pr aims to add 3 test cases for
from_avro/to_avrofrom the perspective ofGenericRecord.Why are the changes needed?
Just to add test cases and help better understand these two functions:
from_avro&to_avro.Does this PR introduce any user-facing change?
No, only just supplementary test cases.
How was this patch tested?
Update existed UT.
Was this patch authored or co-authored using generative AI tooling?
No.