Update docs to reflect that Opensearch is finicky about timezones #31
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
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.
Opensearch doesn't like ISO 8601 date timestamps that don't have an explicit
Z(meaning UTC) or+04:00timezone specifier. However, not having one at all is the same as UTC.Python .isoformat dumps out datetime all the time with no Z.
This adds some documentation calling this out. Since it's a doc change, not a spec change, this doesn't have to trigger a new release of the UBI spec.
opensearch-project/OpenSearch#16673