AVRO-2254: [java] fix unresolved schema name #2365
Merged
Conversation
This file contains 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
martin-g
changed the title
clesaec
force-pushed
the
avro-2254_unionWith2Record
branch
from
8a98795
to
cd30eb9
Compare
Done |
opwvhk
approved these changes
Sep 19, 2023
RanbirK
pushed a commit
to RanbirK/avro
that referenced
this pull request
May 13, 2024
* AVRO-2254: fix unresolved shema name
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is the purpose of the change
AVRO-2254 :
Currently, SchemaResolver.unresolvedSchema method generate always schema with same name. The idea supply Zoltan Farkas is to generate another name each time.
So, the intent of this PR is just to transformed what is proposed in PR form.
Verifying this change
unio.avdl + union.avpr add test on this.
Documentation