Skip to content

Drop EmptyScan in favor of allowing empty VirtualTableScan #673

@benbellick

Description

@benbellick

VirtualTableScan currently requires at least one row:

This made sense when the schema was derived from the first row (714eb77), which required EmptyScan as a separate class to represent empty tables. However, since #272, the schema is explicitly provided via .initialSchema() and is independent of the rows. This makes the non-empty constraint outdated and EmptyScan unnecessary.

We should allow empty VirtualTableScan and deprecate EmptyScan.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions