zed
zed copied to clipboard
brimdata
A novel data lake based on super-structured data
A user asked in a recent [community Slack thread](https://brimdata.slack.com/archives/CTSMAK6G7/p1730920605821519): > is there an easy way to floor a duration? `18m2.43245343s` => `18m2s` There's some ways to achieve this in the...
From zio/csvio/reader.go: ``` // XXX This is a placeholder for an option that will allow one to convert // all csv fields to strings and defer any type coercion presumably...
At the moment the SUP spec indicates that both `Inf` and `+Inf` are ways to express "positive infinity", but only `+Inf` currently works. In the review comments of #5386 @mccanne...
## tl;dr This shows no output, despite the fact that the naked `foo` is invalid ZSON input. ``` $ echo 'foo' | super -i jsup -z -c 'yield typeof(this)' -...
## What's Changed This adds support for env var `ZTEST_VECTOR` which can be set to `true` to have the same effect as having added `vector: true` to each ztest YAML....
Currently in SuperSQL, `count` (both the aggregate function and operator) returns a `uint64` type, but it would be more in keeping with SQL conventions to return a signed type such...
Given the recent improvements with type checking and schemas, "column does not exist" error messages are expected with these queries. ``` $ super -c "SELECT foobar;" {foobar:error("missing")} $ super -c...
This query doesn't work in `super` but does in Postgres. ``` $ super -f parquet -o data.parquet -c "values {a:1},{a:1},{a:2}" && super -c "SELECT SUM(DISTINCT a) + SUM(DISTINCT a) FROM...
The join-key expressions currently work on each side's respective table. You should be able to refer to either side on either side of the join expression. The cut-expressions will continue...
The semantic analyzer should check that an anti join does not specify join assignments as the right-hand side is undefined in anti matches. An error should be reported if such...