Support last_update_time in nanoseconds #960
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
jfrancoa
force-pushed
the
last_update_nano
branch
from
1c13d03 to
e6326df
Compare
It was observed that in old versions of weaviate, the last_update_time field is being retrieved in nanoseconds which causes a ValueError exception. fixes: gh-958
jfrancoa
force-pushed
the
last_update_nano
branch
from
e6326df to
e56302e
Compare
dirkkul
approved these changes
Mar 15, 2024
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.
It was observed that in old versions of weaviate, the last_update_time field is being retrieved in nanoseconds which causes a ValueError exception.
fixes: gh-958