Phil Rzewski
Phil Rzewski
Per the most recent comment from @mattnibs, indeed, I bumped into that again and forgot this issue existed, so I've got #4086 up for review currently to update that general...
When reviewing this one in a team discussion, @mccanne expressed that he's starting to have doubts whether Zed should even continue to offer this type of enum. He's agreed to...
A community zync user recently expressed a need for this functionality.
When this issue gets addressed, there's skipped Rug tests that can be re-enabled. See brimdata/rug#206.
Since this one has been hanging out for a while, I just did a quick check and confirmed that it's still with us in current Zed. ``` $ zq -version...
#3710 looks like a duplicate of this issue, so I'm closing that one. But here's a comment from there that may be relevant when we take this up: > `sqlite`...
We've improved significantly since this issue was opened. Here's a walk through the equivalent repro steps using current Zed commit 26dbda03: ``` $ zed -version Version: v1.2.0-20-g26dbda03 $ ls -l...
This issue is still present as of current Zed commit ae1ac60. ``` $ zq -version Version: v1.2.0-24-gae1ac60a $ echo '{ "foo": "(empty)" }' | zq -f zeek - #separator \x09...
Verified in Zed commit 2d52400. Now when the test data is output in Zeek format, the string is escaped to disambiguate it from the true signifier of emptiness. ``` $...
@mattnibs: Yes, what you describe is what I saw in the spec, so it makes sense that you've seen other projects do the same. I was trying to highlight two...