You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When auto provisioning the table, and specifying a schema, the schema should be automatically created. The current code base fails to autocreate the schema, and if it does not exist, the table fails to get created, and the sink will not log as intended.
Adding this auto-create functionality for the schema prevents the need for any manual intervention when deploying to a new environment.
The text was updated successfully, but these errors were encountered:
Presumably the message would be the SQL error "The specified schema name "xxxxx" either does not exist or you do not have permission to use it." But rather than responding to the error, the fix would be to check whether the schema exists and call CREATE SCHEMA if it does not.
@cdarrigo Do you see the need for any considerations beyond that?
When auto provisioning the table, and specifying a schema, the schema should be automatically created. The current code base fails to autocreate the schema, and if it does not exist, the table fails to get created, and the sink will not log as intended.
Adding this auto-create functionality for the schema prevents the need for any manual intervention when deploying to a new environment.
The text was updated successfully, but these errors were encountered: