Skip to content

docs: update proto-models README for the datafusion-common dependency - #67

Closed
adriangb wants to merge 1 commit into
mainfrom
claude/datafusion-followup-pr-lxornm
Closed

docs: update proto-models README for the datafusion-common dependency#67
adriangb wants to merge 1 commit into
mainfrom
claude/datafusion-followup-pr-lxornm

Conversation

@adriangb

Copy link
Copy Markdown
Member

Which issue does this PR close?

Follow-up to the review comment on apache#24205: apache#24205 (comment)

No separate issue.

Rationale for this change

apache#24205 ("Restore the From / TryFrom proto conversions dropped since 54.1.0") adds a direct datafusion-common dependency to datafusion-proto-models and puts the From / TryFrom impls in the crate. datafusion/proto-models/README.md was not updated alongside it, so it now says the opposite of what is true:

It is intentionally kept narrow: it has no DataFusion dependencies beyond datafusion-proto-common and exposes only the generated structs (and optional pbjson/serde support).

@timsaucer flagged this on the Cargo.toml change; the reply there was that it would be handled as a follow-up. That's this PR.

The crate's lib.rs docs were already updated in apache#24205 — this brings the README in line with them.

What changes are included in this PR?

datafusion/proto-models/README.md only:

  • The crate's contents now include the From / TryFrom conversions between the generated proto types and the datafusion-common types they mirror, with the reason those impls live here (the DataFusion side sits below this crate in the dependency graph, mirroring how datafusion-proto-common handles ScalarValue and Statistics).
  • Restated the narrowness claim accurately: datafusion-common and datafusion-proto-common are the only DataFusion dependencies, and no datafusion-expr or execution crates.
  • Added the datafusion-common crates.io link definition.

Note: this is written against the post-apache#24205 state of the crate, so it should be reviewed/merged after apache#24205 lands. It's based on main rather than stacked on that branch, so it does not depend on it mechanically and will not conflict.

Are these changes tested?

Not applicable — documentation only. ./ci/scripts/doc_prettier_check.sh passes (it made no changes to the file).

Are there any user-facing changes?

Documentation only; no API or behavior changes. The corrected text is user-facing in the sense that this README is the crate's rendered description on crates.io.


Generated by Claude Code

`datafusion-proto-models` now depends on `datafusion-common` and hosts the
`From` / `TryFrom` conversions between the generated proto types and their
`datafusion-common` counterparts, but the crate README still claimed it had
no DataFusion dependencies beyond `datafusion-proto-common` and exposed only
the generated structs.

Describe the conversions and why they live in this crate, and spell out the
narrowness that still holds: `datafusion-common` and `datafusion-proto-common`
are the only DataFusion dependencies.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GoAdfGfHwhLreDPDQ9GoDK
@adriangb adriangb closed this Aug 11, 2026
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.

2 participants