I have a dlt streaming table with a primary key constraint defined through the schema definitions. I have redeployed the same dlt pipeline with the same target. When attempting to run the pipeline, I get the error,  ErrorClass=RESOURCE_ALREADY_EXISTS. Constraint with name `pk_constraint_name` already exists, choose a different name.

I can't find the constraint in information_schema.constraint_table_usage, and thought that the constraint is deleted, but the same error persists when rerunning with the constraint.

Is there a way to alter or drop the schema constraint? It seems to remember it even after running full refresh without constraint and then putting the same constraint back in.