Phil Rzewski

Results 577 comments of Phil Rzewski

For those that may be watching this issue, in addition to the approach shown [above](https://github.com/brimdata/super/issues/4708#issuecomment-2225851732) that can be made to work for any situation where you want to see certain...

Thanks @chrismo. Speaking as someone that bumped into this myself (hence why the issue existed 😄), it's helpful to have an external user's perspective. First I'll revisit some things shown...

@chrismo (and whoever else might be watching this issue): Working with some of the recently-added enhancements such as the initial subquery support in #6070 made me think of this issue,...

For comparison, here's the equivalent in SQL using `LAG`. ``` $ zq -j data.zson.gz > data.ndjson $ duckdb v1.1.1 af39bd0dcf Enter ".help" for usage hints. Connected to a transient in-memory...

There was another recent [community Slack thread](https://brimdata.slack.com/archives/CTSMAK6G7/p1728833757636849) with a use case that seems to fit under this same umbrella. Their example started with these two separate input records: ``` {id:1,data:{b:2}}...

Update: While a direct approach to achieve this while streaming in pipe context does not yet exist, the changes in #6344 and other recent language enhancements change how the interim...

I've attached a shell script [repro.sh.gz](https://github.com/user-attachments/files/16242116/repro.sh.gz) that reliably triggers the repro for me with GA Zed tagged `v1.17.0`. Before running, start: ``` zed -lake s3://brimdataio-lakes-us-east-2/shasta.lake.brimdata.io serve ``` ## Details I...

I happened to just now notice some slow performance when accessing that Shasta S3 bucket. On closer inspection it appears compaction has not run successfully on the Autoperf pool since...

Per the previous comment, the Zed services on Shasta have been updated to GA `v1.17.0`, compaction ran successfully, and indeed the problem no longer reproduces when the repro script is...

We discussed this one as a group and the discussion went much as I'd expected. There was consensus that a user would find this surprising, but changing the implementation to...