Closed alfred-landrum closed 3 years ago
Verified in zq
commit 21b50d02
.
The symptom was present as of commit 9ab4d535
that came before the change in the first of two linked PRs. I happened to have my own ZNG version of the wrccdc-year1 that yielded a different erroneous event count, but still showed the same symptoms of the differing count and error message.
$ zq -version
Version: v0.23.0-9-g9ab4d535
$ zq -t "count()" *
#0:record[count:uint64]
0:[96217189;]
$ zar import -s 128MiB *
$ zar zq -t "count()"
#0:record[count:uint64]
0:[96141291;]
$ find $ZAR_ROOT -name "d*.zng" | xargs zq -t "count()"
/Users/phil/logs/zd/20170324/d-1kNcQnzxTQLZvoN3owklLVK10qr.zng: _path (string): expected primitive type, got container
Now at zq
commit 21b50d02
, the counts are the same and we no longer see the final error message.
$ zq -version
Version: v0.23.0-23-g21b50d02
$ zq -t "count()" *
#0:record[count:uint64]
0:[96217189;]
$ zar import -s 128MiB *
$ zar zq -t "count()"
#0:record[count:uint64]
0:[96217189;]
$ find $ZAR_ROOT -name "d*.zng" | xargs zq -t "count()"
#0:record[count:uint64]
0:[96217189;]
Thanks @mattnibs!
Using the ~4GB
wrccdc-year1
logs, I see a large discrepancy in records when I import it into zar:Additionally, if I try to manually verify against the data files in the resulting archive, I see this zq error:
I wonder if this is related to the fact that some records have the same timestamp, as I saw a similar problem when I was working on the overlap support. (Though note the above runs don't perform any compaction).