You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was fixed upstream in #44532 (GH-44101), released in Arrow 19.0.0. The malformed ColumnIndex {...}" output came from a stray string literal in printer.cc introduced by #38860 (18.0.0); #44532 corrected it to emit "ColumnIndex": {"offset": ..., "length": ...}.
Since then the printer has been migrated to a proper JsonWriter (#50877, #50990), so malformed keys of this kind are structurally impossible now, and #47190 added a ValidJsonOutput test in reader_test.cc that parses the printer's output to make sure it stays valid JSON.
ClickHouse's fork (ClickHouse#72, linked above) is based on release/16.1.0, which predates the fix, so the fork would need to rebase or cherry-pick f5691d4 rather than anything changing here.
@thisisnic I think this one can be closed as fixed.
Note: I used Claude Code to help research this, but I read the ticket, the code and the linked commits myself and the conclusion here is mine, not the tool's.
Activity
stackedsax commentedon Oct 4, 2026
This was fixed upstream in #44532 (GH-44101), released in Arrow 19.0.0. The malformed
ColumnIndex {...}"output came from a stray string literal inprinter.ccintroduced by #38860 (18.0.0); #44532 corrected it to emit"ColumnIndex": {"offset": ..., "length": ...}.Since then the printer has been migrated to a proper
JsonWriter(#50877, #50990), so malformed keys of this kind are structurally impossible now, and #47190 added aValidJsonOutputtest inreader_test.ccthat parses the printer's output to make sure it stays valid JSON.ClickHouse's fork (ClickHouse#72, linked above) is based on
release/16.1.0, which predates the fix, so the fork would need to rebase or cherry-pick f5691d4 rather than anything changing here.@thisisnic I think this one can be closed as fixed.
Note: I used Claude Code to help research this, but I read the ticket, the code and the linked commits myself and the conclusion here is mine, not the tool's.
adamreeve commentedon Oct 13, 2026
Thanks for the investigation @stackedsax!