Skip to content

Move protocol read validation into next::DeltaScan construction #4361

@ethan-tyler

Description

@ethan-tyler

Is your feature request related to a problem?

Protocol read eligibility check doesn't live on the shared next provider construction path. The legacy provider enforced this during scan construction, but in the next-provider flow DeltaScan::new() doesn't own the check.

That means TableProviderBuilder::build() can enforce it, but direct DeltaScan::new() callers bypass it entirely.

Describe the solution you'd like

Move the check into DeltaScan::new() or a helper it owns allowing both builder based and direct construction enforce protocol compatibility consistently.

Describe alternatives you've considered

No response

Priority

None

Additional context

Follow up for #4239.

Relevant paths:

  • Legacy check: table_provider.rs (old scan-builder path)
  • Next provider constructor: table_provider/next/mod.rs
  • Current builder: TableProviderBuilder::build()

Contribution

  • I'm willing to submit a pull request for this feature
  • I can help with testing this feature
  • I can help with documentation for this feature

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Status

No status

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions