diff --git a/docs/assets/img/logos/databricks.png b/docs/assets/img/logos/databricks.png new file mode 100644 index 00000000000..a2d91399e62 Binary files /dev/null and b/docs/assets/img/logos/databricks.png differ diff --git a/docs/integrations/databricks.md b/docs/integrations/databricks.md index bf21d0b21be..44601412400 100644 --- a/docs/integrations/databricks.md +++ b/docs/integrations/databricks.md @@ -80,7 +80,7 @@ the Unity Catalog metadata. lakeFS support for Unity Catalog differs between lakeFS OSS and lakeFS Enterprise & Cloud. -### Catalog Exports Open-Source +### Catalog Exports lakeFS Leveraging the external tables feature within Unity Catalog, you can register a Delta Lake table exported from lakeFS and access it through the unified catalog. @@ -94,7 +94,7 @@ a way to export changes from lakeFS to Unity Catalog. For the full guide on how to use Catalog Exports with Unity Catalog, see the [documentation](./unity-catalog.md). -### lakeFS for Databricks Cloud Enterprise +### lakeFS for Databricks Enterprise lakeFS for Databricks provides a seamless integration between lakeFS and Unity Catalog. Its primary benefits over the integration offered by lakeFS open-source are: diff --git a/docs/integrations/index.md b/docs/integrations/index.md index b99d74cb8b2..b2c2a57ee60 100644 --- a/docs/integrations/index.md +++ b/docs/integrations/index.md @@ -47,7 +47,7 @@ See below for detailed instructions for using different technologies with lakeFS