Phil Rzewski

The addition of `zed compact` via #3940 justifies revisiting the tests performed here to see if compacting the objects from the large number of commits might improve query performance., As...

At team sync today we discussed the most recent results above. There was consensus that it was unsurprising to see slow queries when the pool was still formed by 7000...

@mccanne confirmed there's some overlap between this issue and #2575.

A community zync user recently pointed out that the lack of auto-sort on `join` "blocks everyone [on their team] when they learn Zed".

Here's an interesting development. It looks like this got fixed some time ago, and was working as originally desired as recently as Zed commit cd2f3a3 on July 25, 2022. ```...

I can verify that as of GA `zq` tagged `v0.22.0`, having completed the base AWS CLI config is now enough to make this work. ``` $ echo '{"foo": "bar"}' |...

I bounced this topic off @nwt and @mccanne and they agreed there may be something to improve here, but it's part of a likely wider set of "use"-related improvements we...

Note that as of current Zed commit 9c0f097, as shown in https://zed.brimdata.io/docs/next/commands/zed#211-query, a plain reference to `HEAD` does work. ``` $ zed -version Version: v1.2.0-49-g9c0f0973 $ curl http://localhost:9867/version {"version":"v1.2.0-49-g9c0f0973"} $...

I happened to bump into this problem again, then found this issue was already open. Here's the example with current Zed commit 26dbda0 so you can see my journey. I...

Verified in Zed commit 418c024. The example above no longer produces a parse error. ``` $ zq -version Version: v1.2.0-86-g418c024d $ echo '"foo_.:/%#123@~bar"' | zq -z '*123*' - "foo_.:/%#123@~bar" ```...