Skip to main content

Community

Connector Improvement: Create Schema - required for DBRK setup

Answered

Please sign in to leave a comment.

Comments

4 comments

    Hi Nitin,

    Thanks for bringing this to our attention. Can you elaborate on the reasons the schema should not be created by Fivetran?

    Best,

     

    As per Novartis standard No schema should be created without S3 path. When Fivetran automatically creates the schema, the Data directly lands into the platform managed path where there is no encryption. So, the use case team is asking to remove this privilege for the list.

    Hi Nitin,

    This privilege is required during connector creation and whenever a new schema is selected within an existing connection. Alternatively, you may configure Delta tables to be created in a user-provided external location rather than in Databricks-managed storage.

     

    Best regards,

    Hi Nigin,

    We're revisiting this request and want to understand your process. Fivetran can create schemas dynamically as new ones appear in the source, so we'd like to know how you handle those. We're also curious about your workflow for creating a schema before setting up a pipeline, since creating a connector in Fivetran requires specifying a schema name upfront.

    Best,