Skip to content

Type variation in substrait: Hardcoding the numbers isn't really the proper way to do type variations. #12355

@alamb

Description

@alamb

FWIW, hardcoding the numbers isn't really the proper way to do type variations. (Rather we should add the variation as an extension and refer to the extension's id.) However, given this is already used for default vs large, I guess adding view makes sense - and they can all be migrated at once to the proper way someday.

Originally posted by @Blizzara in #12199 (comment)

The idea here is for someone to research how this is supposed to work and then change the datafusion substrait implementation to do it

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