Closed philrz closed 4 years ago
Verified in zq
commit 8820a88
. Now we get a helpful error message and no stack dump.
$ zq echo '{"foo": "bar"}' | zq -o s3://zq-771/foo.zng -
{"foo": "bar"}: stat {"foo": "bar"}: no such file or directory
Thanks @mattnibs!
I stumbled onto this quite by accident while verifying https://github.com/brimsec/zq/issues/771. I'm running
zq
commit4e6680f
.The leading
zq
on the very front of the command line was unintentional, but triggered this stack dump. Obviously I should not have expected success since I made a mistake, but surely we'd not want the stack dump either.It appears like it may be unique to the new S3 output option, since there's no stack dump when I attempt to output to a local file.