Phil Rzewski

#5041 was opened to change the behavior so `collect()` would preserve these values, but then we discussed it as a team and have decided to hold off on merging anything...

In the time since this issue was opened, the language has been evolving into SuperSQL (currently at commit 4084e01) and so mimicking SQL becomes our typical starting position when picking...

A community user noticed in #5759 that `error("missing")` values are being similarly skipped, e.g., ``` $ super -version Version: v1.18.0-366-g7f5ca96c0 $ echo '1 2 error("missing") 4' | zq -z 'collect(this)'...

I think this issue is no longer relevant since with the new `join` implementation added in #5962 the concept of "assignments" has been removed. ## Details Below is an example...

Note to self: Update #4937 when this issue is fixed.

Verified in Zed commit 711bf9f. Repeating the original repro, the `count()` result nows resets to zero when processing begins on the second array value. ``` $ zq -version Version: v1.15.0-34-g711bf9f4...

@mccanne  pointed out that the changes proposed in #2586 will make it easier for us to implement these persistent preferences, since having one set of global flags means there's no...

After learning about [user-defined operators](https://zed.brimdata.io/docs/language/statements#operator-statements) a and [user-defined functions](https://zed.brimdata.io/docs/language/statements#func-statements) a community user recently mentioned in a [Slack thread](https://brimdata.slack.com/archives/CTT24051C/p1708113590411679?thread_ts=1708107741.577409&cid=CTT24051C) how handy this would be. In their own words: > Would be...

The Zed docs published in #2836 cited this issue as a current limitation. When this issue is addressed, the docs should be updated.

It looks like the join-key expressions in the new `join` implementation added in #5962 are no longer "fussy". ## Details Here's a walk through of how things stand as of...