-
```
21:38 ~/work/brim/zq(master)
$ zq -t test.tzng
#0:record[tls:record[fingerprint:string,issuerdn:string,ja3:record[],ja3s:record[],notafter:string,notbefore:string,serial:string,sni:string,subj…
-
-
When narrowing down the root cause of #1087, we found that stack traces were being generated. However, the team was surprised to find that they were not landing in full in the `zqd` logs (though they …
-
`zar index ` checks that the type of `` is the same in all records, and produces an error if not. The same is not true when building a custom index. We should check for and error on type changes when …
-
Follow on from https://github.com/brimsec/zq/issues/989 : The archive stats information should include information about the indexes. There should be a record for each index file, and it should includ…
-
As a first step for zar s3 support, make `zar import` and `zar zq` work for an S3 data storage location.
-
I ran into this bug while finishing up #856 (rename proc):
```
$ zq -t "head 1 | cut id | put id2=id.orig_h | cut -c id.orig_h" conn.log …
-
I was running a `zar` demo yesterday and it went off the rails when running through the [simple graph queries](https://github.com/brimsec/zq/tree/master/cmd/zar#simple-graph-queries) step. I've done a…
-
Start with the following input data:
```
cat bug.zng
#0:record[a:int]
0:[1;]
0:[2;]
```
As of `zq` commit `1759030`, the following syntax was working:
```
# zq "c=count()" bug.zng
#0:record[c:count…
-