This repository was archived by the owner on Apr 22, 2022. It is now read-only.
Use native timestamps in default schema#7
Open
asnare wants to merge 1 commit into
Open
Conversation
|
LGTM |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
This pull request updates the default schema to use proper timestamps for the timestamp fields. Prior to Avro 1.9 this meant pulling in JODA, but now that JSR310 is supported by Avro no additional dependencies are created.
Downstream consumers of the default records will not be affected by this; existing read-schemas will remain compatible.
This pull request will resolve issue #6 .