Unique Constraints on Optimizations


1 comment

  • Comment actions Permalink
    Official comment
    Nick Golovin

    Hi Stefan,

    we added this request to the list of our feature candidates. There is no ETA at this point of time. Upvotes from other customers could help us prioritize the feature development. 

    During the internal discussions the following topic was raised, that affects the usefulness of this feature:

    The majority of our customers are using specialized anlytical databases like Azure Synapse, AWS Redshift, Snowflake) as analytical storage. One common characteristic of the above databases is that although they allow defining unique constraints, but they do not enforce them, so that a column defined as unique may still contain duplicate values. 

    A possible solution to this would be, that instead of creating unique column we would allow executing a user-defined parametrized SQL query, which could, depending on the user definition, create unique constraint or just validate the new materialization table and based on this validation decide whether to enable the new mattable or not. 

    best regards,




Please sign in to leave a comment.

Powered by Zendesk