Skip to content

How to deal with Schema Evolution in an API? #244

Description

@rdick

Hello,

I wasn't finding any specific methods where I could evolve a tables schema when querying an api with a custom connector.

Eg.
START: Table X - id, first_name, last_name
.
CHANGE: Table X - id, first_name, last_name, middle_name
.
How can we ensure that it will push this into the schema?

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