Skip to content

feat: Allow destinations to declare and act on schema limitations #14587

@erezrokah

Description

@erezrokah

Are you positive this feature should be implemented in the SDK?

  • I'm positive this is an SDK feature

Which problem is this feature request solving?

We used to validate table and column names match a specific pattern and maximum length. That was mostly oriented at PostgreSQL, but doesn't work that well when using other destinations, like syncing from OracleDB source to Snowflake destination where you can have uppercase table names.

Other destinations limitations can be constraint key length (like in #13569).

Describe the solution you'd like

Destinations should be able to declare limitations on the schema they support, and possibly a default behavior on how to handle those (or error out).

Pull request (optional)

  • I can submit a pull request

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions