Add extractor predicates #2984
Merged
Add extractor predicates #2984
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
tobim
reviewed
Mar 2, 2023
jachris
force-pushed
the
topic/extractor-predicates
branch
2 times, most recently
from
6b3e1ec to
35ecbf9
Compare
tobim
reviewed
Mar 2, 2023
tobim
approved these changes
Mar 2, 2023
Extractors such as `id.orig_h` and `:uint64` are now allowed where a predicate is expected. They expand to `id.orig_h != nil` and `:uint64 != nil`, respectively.
jachris
force-pushed
the
topic/extractor-predicates
branch
from
5dda47c to
1b1c591
Compare
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.
Extractors such as
id.orig_hand:uint64are now allowed where a predicate is expected. They expand toid.orig_h != niland:uint64 != nil, respectively.Closes tenzir/issues#50.