This repository was archived by the owner on Aug 2, 2022. It is now read-only.
Adding support for much more permissive date parsing for ExprTimestam… #1118
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
…pValue creation (support of T or not T, autofill missing part with 0s)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Adding support for much more permissive date parsing for ExprTimestampValue creation (support of T or not T, autofill missing part with 0s)
Issue #, if available:
These other formats instead are already supported
"yyyy-MM-dd'T'HH:mm:ss.ZZZZZZ"
"yyyy-MM-dd HH:mm:ss"
so I'm filling the gap
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.