AVRO-1904: C: Allow record to have no fields. #159
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
|
Looking at the Avro Specification it requires a record to have fields? What would the use case be to define a record without any fields? |
|
The case I saw was in my colleague's code: a possible branch of a union -- the other possible record types had fields, but one of them didn't. The real issue here is that the Java writer allows files with zero-length records to be created, but the C reader can't read them. |
iemejia
referenced
this pull request
in iemejia/avro
May 24, 2021
* Fix PCF for boolean #159 * Better PCF (more strips) and fix docstrings tests * Small fix
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.
No description provided.