Skip to content

query-wasm (M4): ungate classic checkpoints via async footer SchemaQuery #116

Closed

Description

@roeap

M4/v2 follow-up to #112.

v1 gates checkpointed tables to Unsupported (falling back to the server) because the scan SM's checkpoint-footer SchemaQuery step would need a kernel engine. This is the biggest coverage gap: any non-trivial table gets checkpointed, so today they all fall back.

Plan

  • Service EngineRequest::SchemaQuery asynchronously over the session object store via parquet::arrow::async_reader / ParquetMetaDataReader — still engine-free (kernel schema via TryFromArrow). The current execute_schema_query_phase in delta-df-provider/src/executor/mod.rs returns an "unsupported in v1" error; replace it with the async read.
  • Remove the checkpoint gate from crates/query-wasm/src/resolve.rs for classic-named checkpoints (keep v2/UUID gated — see the v2-checkpoint issue).
  • Regression: a checkpointed fixture reads back identically to the commit-only path.

Why: the async footer read is engine-free and unblocks the majority of real tables.

Activity

  1. added 4 commits that reference this issue on Jul 16, 2026
    5d99774
    b6c9672
    c331c04
    3ee25e1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions