Skip to content

DataFusion's casting semantics incompatibilities are causing runtime errors #6269

Closed
Closed
DataFusion's casting semantics incompatibilities are causing runtime errors#6269
Assignees
AdamGS
Labels
bugA bug issue

Description

@AdamGS
AdamGS
opened on Feb 3, 2026

Due to DataFusion's improved projection pushdown, we now push some cast expressions into our scans, in ways that are incompatible with Vortex's cast semantics.

Examples

  1. Cast error when casting integer type to string in select statement with datafusion-vortex #6211
  2. Panic when handle schema evolution in vortex file #6264

Activity

  1. AdamGS
    self-assigned this
    on Feb 3, 2026
  2. AdamGS
    added
    bugA bug issue
    on Feb 3, 2026

  3. gatesn commented on Feb 8, 2026

    @gatesn
    gatesn
    on Feb 8, 2026
    Contributor

    @AdamGS do we get to yay/nay the projection push-down in the same way as filter push-down? If so then we probably need some way of saying whether a particular cast is supported.

    If not... I'm not sure how we can guarantee forever more that we support a super-set of DataFusion casts.

  4. vortex-data
    locked and limited conversation to collaborators on Feb 9, 2026
  5. AdamGS
    converted this issue into a discussion #6357 on Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugA bug issue

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions