Introduce the #import_time meta extractor
#2019
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
dispanser
approved these changes
Jan 7, 2022
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.
This introduces the
#import_timemeta extractor to the query language. Use it to query for data based on the timestamp that the data arrived at the VAST server process, e.g.,vast export json '#import_time > 1 hour ago'will export all data that was added in the last hour as NDJSON.The new extractor behaves like a timestamp in the query language and can be used for comparisons with time value literals.
馃摑 Checklist
馃幆 Review Instructions
Review commit-by-commit. Test extensively locally. Previous PRs added unit test coverage, so this only adds integration test coverage now that it is exposed to the user.