[#xx] Add support for SELECT-FILTER expressions #118
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
pool
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-sdk-go#118
Loading…
Reference in a new issue
No description provided.
Delete branch "ale64bit/frostfs-sdk-go:feature/select-filter-expr"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This will allow the policy playground command to evaluate
FILTER
s andSELECT
ors independently, to better understand their effect and build policies incrementally.Signed-off-by: Alejandro Lopez a.lopez@yadro.com
[#xx] Add support for SELECT-FILTER expressionsto WIP: [#xx] Add support for SELECT-FILTER expressionsWIP: [#xx] Add support for SELECT-FILTER expressionsto [#xx] Add support for SELECT-FILTER expressions@ -1,4 +1,4 @@
// Code generated from Query.g4 by ANTLR 4.13.0. DO NOT EDIT.
// Code generated from /home/alopez/src/frostfs-sdk-go/netmap/parser/Query.g4 by ANTLR 4.13.0. DO NOT EDIT.
looks redundant)
fixed.
It looks like this is generated when
make policy
is used, but not whengo generate ./...
is used. We should probably fix this.9ac75c07cc
to6ba1adfa07
Could you elaborate, how it helps?
I mean we can (?) decode SELECT/FILTER separately, and a separate root terminal will introduce some branching in the CLI anyway, so what is the benefit?