Repository navigation
Conversation
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…trib#111) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…ntrib#112) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…fusion-contrib#114) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…type (datafusion-contrib#115) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ontrib#118) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…rib#124) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Picks up the two bugfixes merged since v0.54.2: - Fix nested JSON string access (datafusion-contrib#121) - Fix panic on JSON integers outside the i64 fast path (datafusion-contrib#124) Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CShJj2bykoAodw9WnMQuRY
There was a problem hiding this comment.
🟡 Medium src/common_union.rs:184
Unions produced by previous releases are no longer recognized as JSON unions. The code identifies a union by comparing the full UnionFields for equality, and union_fields() now adds ARROW:extension:name and ARROW:extension:metadata keys to the array and object child fields. Existing unions whose child fields carry only the legacy is_json=true metadata fail this equality check, so passing them into JsonUnionEncoder::from_union or json_union_to_text is rejected as a non-JSON union — even though the legacy is_json key was explicitly retained for backward compatibility. Recognition should accept both the legacy and canonical metadata shapes (e.g., ignore these additive metadata keys when identifying the union type), not require an exact match.
🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
In file @src/common_union.rs around line 184:
Unions produced by previous releases are no longer recognized as JSON unions. The code identifies a union by comparing the full `UnionFields` for equality, and `union_fields()` now adds `ARROW:extension:name` and `ARROW:extension:metadata` keys to the `array` and `object` child fields. Existing unions whose child fields carry only the legacy `is_json=true` metadata fail this equality check, so passing them into `JsonUnionEncoder::from_union` or `json_union_to_text` is rejected as a non-JSON union — even though the legacy `is_json` key was explicitly retained for backward compatibility. Recognition should accept both the legacy and canonical metadata shapes (e.g., ignore these additive metadata keys when identifying the union type), not require an exact match.
Prep for a new release.
mainhere was at0.52.0(datafusion 52), 15 commits behinddatafusion-contrib/datafusion-functions-json, which has since published0.53.0,0.53.1,0.54.0,0.54.1and0.54.2to crates.io. Since the release workflow runscargo publishon tag push, any version already on crates.io would fail to publish — so this syncs first, then cuts the next number.Changes
main(774c570).origin/mainis a strict ancestor, so this is a clean fast-forward — no conflicts, no rewritten history. It brings in DataFusion 53 and 54 support, jiter 0.15, thejson_union_to_textUDF, Arrow JSON extension type metadata, string type coercions, and the recent null-array / nested-string / integer-overflow fixes.versioninCargo.tomlfrom0.54.2to0.54.3.0.54.3is the next unpublished version, and there are exactly two bugfixes merged upstream since thev0.54.2tag that it would release:Testing
cargo testpasses on this branch: 168 passed, 0 failed.Releasing
Merging this doesn't publish anything — CI only runs
cargo publishfor tag pushes. Pushv0.54.3on the merge commit when you want it out.Generated by Claude Code