[GH-ISSUE #5487] [Feature] Add JSON Lines output for large row-oriented results #3341

New issue

Closed

opened 2026-10-31 00:39:20 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-31 00:39:20 +00:00

Owner

Originally created by @jayykernel on GitHub (Oct 20, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/5487

Problem

Large inventories and analysis-view collections may be awkward to consume as one JSON array: scripts must parse the whole document before processing its first row, and large responses can be cumbersome to stream or filter.

Proposed change

Consider an opt-in JSON Lines format for row-oriented results. Each line should be one independently parseable record, with coverage and truncation information defined in a documented convention rather than silently discarded.

Acceptance criteria

JSON Lines is available only for result types with a clear record boundary.
Every emitted line is valid JSON and record order is deterministic.
The format preserves stable source indices/identities and does not imply complete coverage when output is partial.
Errors and final coverage metadata have a documented representation that cannot be mistaken for an ordinary data row.
Tests cover empty results, multiline strings, partial coverage, and records with large fields.

This is a proposed alternative output format, not a claim that existing JSON is invalid.

Originally created by @jayykernel on GitHub (Oct 20, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5487 ### Problem Large inventories and analysis-view collections may be awkward to consume as one JSON array: scripts must parse the whole document before processing its first row, and large responses can be cumbersome to stream or filter. ### Proposed change Consider an opt-in JSON Lines format for row-oriented results. Each line should be one independently parseable record, with coverage and truncation information defined in a documented convention rather than silently discarded. ### Acceptance criteria - JSON Lines is available only for result types with a clear record boundary. - Every emitted line is valid JSON and record order is deterministic. - The format preserves stable source indices/identities and does not imply complete coverage when output is partial. - Errors and final coverage metadata have a documented representation that cannot be mistaken for an ordinary data row. - Tests cover empty results, multiline strings, partial coverage, and records with large fields. This is a proposed alternative output format, not a claim that existing JSON is invalid.

bsakaguchi closed this issue

2026-10-31 00:39:20 +00:00

bsakaguchi commented

2026-10-31 00:39:21 +00:00

Author

Owner

@matbrgz commented on GitHub (Oct 20, 2026):

Cross-referencing with canonical feature #5481 () and siblings #5482, #5486, and #5490. Represents part of the headless CLI batch inspection, structured I/O, and streaming output suite. Cataloged under Cluster AV in consolidation tracker #4330.

@matbrgz commented on GitHub (Oct 20, 2026): Cross-referencing with canonical feature #5481 () and siblings #5482, #5486, and #5490. Represents part of the headless CLI batch inspection, structured I/O, and streaming output suite. Cataloged under Cluster AV in consolidation tracker #4330.

bsakaguchi referenced this issue

2026-10-31 01:00:24 +00:00

[PR #2124] [CLOSED] feat(domain): add opt-in address-normalized function text views #5045

bsakaguchi referenced this issue

2026-10-31 01:08:56 +00:00

[PR #3394] [CLOSED] test(javascript): assert wrapper ownership in the correct source mode #5721