Phil Rzewski

Here's a crude example of implementing the proposal using existing building blocks. ``` $ zq -version Version: v1.7.0-41-g58e7993d $ cat messages.ndjson {"message": "One"} {"message": "Two"} Message {"message": "Three"} $ zq...

There was another recent request for this functionality in https://github.com/brimdata/zui/issues/2933. The user made a couple suggestions that might be worth considering in our design here: 1. Including the line number...

Note the changes over the years with "partial loads" as captured in https://github.com/brimdata/zui/issues/2660.

@mattnibs started looking into this for JSON recently and noted that the way we currently read JSON makes this particularly challenging. It sounds like if we brought back the idea...

I've been tinkering in this area a bit more and while we're waiting on this functionality in SuperDB I found this `jq` filter seems to provide a helpful, conservative filtering...

To go along with that last comment, here's a brief overview of the fault tolerant JSON reading modes in DuckDB and ClickHouse. ## DuckDB Attempting to read the `file_0005.json.gz` shown...

Another recent example of this came up with the data set used in #6206. At a high level, the reason I ended up using DuckDB to convert the TSV to...