grange
grange copied to clipboard
square
A modern subset of the range query language
`%allclusters()` doesn't currently parse but should. Workaround is `%{allclusters()}`. There is a relevant pending range spec in `expand_test.go`.
There are a number of range specs that have some variation of the form `%a{b}c` that don't currently work. See the pending list inside `expand_test.go` for more examples.
`(bad,mad,good) & /ad/` and `/ad/ & (bad,mad,good)` should be equivalent, but the latter doesn't work as expected, because first the LHS expands to nothing before the intersection applies. The relevant...
The current implementation of numeric expansion (see `numericRangeRegex` and associated code) doesn't handle some newer additions to range spec such as `a1a1..a1a3` and `a2a2a1..a2a2`. It may be possible to patch...
When `%{has(HOST;foo)}` doesn't return any result `d%{has(HOST;foo)}:KEYS` returns a bunch of things
The following range query returns no data: ``` $ er -e '%{has(HOST;foo)}' [WARNING] No nodes returned ``` However, appending `:KEYS` returns some data: ``` $ er -e '%{has(HOST;foo)}:KEYS' ... ```...
