Skip to content

Sync with upstream and bump version to 0.54.3 - #4

Open
adriangb wants to merge 16 commits into
mainfrom
claude/release-version-prep-ii17k2
Open

adriangb wants to merge 16 commits into
mainfrom
claude/release-version-prep-ii17k2

Conversation

@adriangb

Copy link
Copy Markdown
Member

Prep for a new release.

main here was at 0.52.0 (datafusion 52), 15 commits behind datafusion-contrib/datafusion-functions-json, which has since published 0.53.0, 0.53.1, 0.54.0, 0.54.1 and 0.54.2 to crates.io. Since the release workflow runs cargo publish on tag push, any version already on crates.io would fail to publish — so this syncs first, then cuts the next number.

Changes

  • Fast-forwards to upstream main (774c570). origin/main is 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, the json_union_to_text UDF, Arrow JSON extension type metadata, string type coercions, and the recent null-array / nested-string / integer-overflow fixes.
  • Bumps version in Cargo.toml from 0.54.2 to 0.54.3.

0.54.3 is the next unpublished version, and there are exactly two bugfixes merged upstream since the v0.54.2 tag that it would release:

Testing

cargo test passes on this branch: 168 passed, 0 failed.

Releasing

Merging this doesn't publish anything — CI only runs cargo publish for tag pushes. Push v0.54.3 on the merge commit when you want it out.


Generated by Claude Code

adriangb and others added 16 commits March 24, 2026 15:34
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
Comment thread src/common_union.rs

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants