-
We're going to stop creating the .brim folder next to ingested data, By default, we should *not* specify a data_dir in the space create api call; so the zng data & other space information will be crea…
-
I stumbled onto this quite by accident while verifying https://github.com/brimsec/zq/issues/771. I'm running `zq` commit `4e6680f`.
The leading `zq` on the very front of the command line was unintent…
-
Use the cut proc to cut out only the fields that the user has selected in the columns picker.
-
Repro is with `zq` commit `821ae98`.
Suppose I've got a directory on an S3 bucket with valid files to be read.
```
$ aws s3 ls s3://zq-771/foo/
2020-06-16 15:26:24 541 conn.tzng
2020-06-16 15…
-
I am considering whether we should drop support for LFS in zlib-ng's native ABI and possibly partially in the compat code as well.
Assume we always define: `_FILE_OFFSET_BITS=64?`, that should repl…
Dead2 updated
4 years ago
-
The typed ndjson reader panics upon reading a record where a field that is expected to contain an array instead contains a scalar.
```sh
$ echo '{"_path":"panic","f":"foo"}' | zq -t -j panic.json …
-
```sh
10:45 ~/work/brim/zq(master)
$ git rev-parse --short HEAD
6a05953
10:45 ~/work/brim/zq(master)
$ cat blar.zng
#0:record[blar:string]
0:[blar1]
10:45 ~/work/brim/zq(master)
$ zq blar.zng…
-
The zjson writer handles aliases to primitive types ok, but not aliases to container types. (The zjson reader likely has a similar issue).
```sh
$ cat alias.tzng
#0:record[host:ip]
0:[127.0.0.2…
-
zq should support reading from and writing to locations in S3 object stores, including AWS S3 & minio. s3 locations should be recognized via `s3:///...` style urls. zq should honor any relevant config…
-
Add support for space ids, uuid-like immutable identifiers that will be used instead of space names as the resource id in api calls. The id should be created by zqd when the space is returned, and pas…