Databricks database support #3518
Conversation
Feature/add databricks support
|
|
|
+1 |
|
@zayscue Did you get this working with Unity Catalog? I'm trying to follow along here and connect to the catalog then database/schema, and it's not working as intended. Did you need to complement catalog support separately? Or changes to the URL? |
|
Came here looking for Databricks support in Flyaway |
|
Would love to utilize this feature and see it get some attention by Databricks and Red-Gate folks and get merged. |
|
Any news on this? |
|
Which release will have Databricks support? |
| @@ -13,7 +13,7 @@ | |||
| * See the License for the specific language governing permissions and | |||
| * limitations under the License. | |||
| */ | |||
| package org.flywaydb.commandline.command.version; | |||
| package org.flywaydb.commandline.logging.version; | |||
There was a problem hiding this comment.
Hope I'm within the bounds of reasonableness. Since you've changed the path here to be logging instead of version, you also need to update the line in src/main/resources/META-INF/services/org.flywaydb.core.extensibility.Plugin to org.flywaydb.commandline.logging.version.VersionCommandExtension as well. (or at least I had to in order to build this)
I think I'm missing some context here, but what's the motivation behind moving these files into logging?
| <dependency> | ||
| <groupId>com.databricks</groupId> | ||
| <artifactId>databricks-jdbc</artifactId> | ||
| <version>2.6.29</version> |
There was a problem hiding this comment.
may want to include the latest version if possible, 2.6.33
|
Forked this and made some additional changes: #3681 |
|
Waiting for this feature - please merge and release! Even if it's 'beta', lets try it. |
|
Are there any updated on this feature? |
|
Any Update on this features |
|
+1 |
|
Community db support is now handled in another repository. The databricks integration was merged recently: flyway/flyway-community-db-support#26 |
Databricks has recently expanded its data warehousing offerings, and because of this companies have begun to forgo using Databricks in combination with other warehouses like Snowflake or BigQuery and instead have decided just to keep everything within Databricks. Because of this shift, there is a need for more traditional SQL tooling that supports the Databricks SQL divers and dialect. This merge request is designed to create a community-supported Databricks SQL implementation for the flyway database migration tool.
References:
What is a Databricks SQL Warehouse: https://docs.databricks.com/sql/admin/sql-endpoints.html
Databricks SQL Reference Docs: https://docs.databricks.com/sql/language-manual/index.html