Skip to content

Destructure proto hooks for FileScanConfig and MemorySourceConfig #24624

Description

@adriangb

Scope

file type
datasource/src/file_scan_config/proto.rs FileScanConfig
datasource/src/memory.rs MemorySourceConfig

4 hooks (2 encoders, 2 decoders).

Notes

FileScanConfig is the shared base message every file source embeds, so a field dropped here is dropped for Parquet, CSV, JSON, Arrow and Avro at once -- it is the highest-leverage hook in this EPIC. It currently mixes getter calls and direct field reads.

MemorySourceConfig::projected_schema is unmentioned by the encoder and is derived from the schema plus projection on decode; that should become an explicit _ binding.

Why

Serde hooks that read state through getters or self.field make an added field invisible to serialization: nothing breaks at compile time, the field simply stops round-tripping, and Debug-comparing round-trip tests do not notice. HashJoinExec::fetch was lost exactly this way (#24165), and #24609 is a second live instance found by applying the convention to one file.

#24164 established the fix -- exhaustive destructuring in both directions -- and applied it to the join plans. The physical-plan plan nodes are done. physical-expr and the datasource* crates were never converted.

What to do

For each hook in scope:

  1. In try_to_proto, start with an exhaustive let Self {{ .. }} -- no .. rest pattern. Fields that are genuinely not serialized bind to _ with a short comment saying why (derived at construction, runtime state, recomputed on decode, carried by a parent message).
  2. In try_from_proto, destructure the prost-generated node struct the same way, so adding a field to datafusion.proto is a compile error in every decoder.
  3. If the destructure turns up a field that should round-trip but has no wire representation, add it to the message and cover it with a test that fails without the fix.

Definition of done

Metadata

Metadata

Assignees

Labels

protoRelated to proto crate

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions