-
Notifications
You must be signed in to change notification settings - Fork 173
feat(csharp/src/Drivers/Databricks): Add configurable multiple catalog support #2845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(csharp/src/Drivers/Databricks): Add configurable multiple catalog support #2845
Conversation
…g support Adds a new connection parameter 'adbc.databricks.enable_multiple_catalog_support' to control whether the driver should use multiple catalogs or restrict to a default catalog. Default is true for backward compatibility. This parameter accepts boolean values 'true'/'false' or '1'/'0' for compatibility with tools like PowerBI.
CurtHagenlocher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Is there a reason not to use "true" and "false" instead of "0" and "1" in the connection string?
| { | ||
| _enableMultipleCatalogSupport = enableMultipleCatalogSupportValue; | ||
| } | ||
| // PowerBI will pass in "1" and "0" as strings, so we need to handle that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ADBC convention is to use "true" and "false" for boolean-valued settings. Is it important to retain compatibility with ODBC here? The property name will be different anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The existing Power BI connector passed in "0", "1" etc, do you recommend changing the connector code to overwrite as true/false rather than handle here in the driver?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
CurtHagenlocher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Description
This PR adds support for configuring multiple catalog behavior in the C# Databricks ADBC driver. It introduces a new connection parameter
adbc.databricks.enable_multiple_catalog_supportthat allows users to control whether the driver should use multiple catalogs or restrict to a default catalog.Proposed Changes
adbc.databricks.enable_multiple_catalog_supportto control multiple catalog behaviorHow is this tested?
Added unit tests that verify the behavior of metadata queries (GetSchemas, GetTables) with different settings of the
CanUseMultipleCatalogsparameter. Tests confirm that when disabled, only the default catalog is used, and when enabled, multiple catalogs can be accessed.