Phil Rzewski

In bug #5886, I mentioned how I originally attempted to work around this problem with an approach that used lateral subqueries, but that panic blocked me. Now that the bug...

Hi @chrismo. Sorry for the trouble. Indeed, some adjustments to `from` were made in #5378 to make way for SQL coverage, so you're seeing the impact of that here. To...

@chrismo: Yes, good find. While I happened to mention #5378 as the first step in these changes that led to where we are now with different `from`/`eval` behaviors and how...

We need to spend some time thinking about what operators in other tools do this so we're not reinventing the wheel. @nwt noted that this would probably be performed as...

Thanks to the new `join` implementation added in #5962, I think we can effectively do what @mccanne described in the last [comment](https://github.com/brimdata/super/issues/3056#issuecomment-963692960) above. Updating the simple example shown above for...

A community user recently started making use of `-f text`, and after seeing their struggles I added some minimal coverage of the format in a new [Simplified Text Outputs](https://zed.brimdata.io/docs/commands/zq#simplified-text-outputs) section...

Another user asked about this in a recent [community Slack thread](https://brimdata.slack.com/archives/CTSMAK6G7/p1736539106935469). In their own words: > is there a way to get `-f text` to interpret newlines the way I...

The functionality described in the last comment above has been added to SuperDB via the changes in #5570 that provide the `-f line` option. Related documentation is in #5571 and...

@zmajeed: Thanks for your interest in Zed! By chance are you familiar with [Grok](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html)? We actually have a PR set to merge soon (#4827) where we'll introduce a Grok function...

@zmajeed: Yes, I understand Grok can seem kind off-putting, particularly at first. Since you mentioned that log querying is a primary use case for you, at some point you may...