Add Microsoft Fabric and Databricks UCsupport docs#1296
Conversation
Add Microsoft Fabric docs and Databricks UCsupport
There was a problem hiding this comment.
Pull request overview
Updates the documentation to include Microsoft Fabric guidance and to expand Databricks documentation around Delta / Unity Catalog support (issue #1295).
Changes:
- Expanded “Running on Fabric” docs to distinguish Community vs Enterprise usage.
- Updated Databricks running and connector docs to mention Delta tables / Unity Catalog.
- Added a new Microsoft Fabric page under “Data Sources and Sinks” and linked it from the docs summary.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/running/running-on-fabric.md | Refines Fabric running instructions and adds Community/Enterprise sections. |
| docs/running/databricks.md | Updates Databricks running guidance to mention Delta/Unity Catalog and UCPipe. |
| docs/dataSourcesAndSinks/fabric.md | Adds a new Microsoft Fabric connector overview page. |
| docs/dataSourcesAndSinks/databricks.md | Updates Databricks connector overview to mention Delta/Unity Catalog for Community. |
| docs/dataSourcesAndSinks/connectors.md | Adds Microsoft Fabric to the top-level connector list. |
| docs/SUMMARY.md | Adds Microsoft Fabric under “Data Sources and Sinks” in the TOC. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ## For running the Zingg Enterprise version on Microsoft Fabric: | ||
|
|
||
| This uses the Zingg Enterprise Python API and all [file formats and data sources and sinks](../dataSourcesAndSinks/) are supported within Microsoft Fabric with **Zingg Enterprise** including additional advanced features and support. |
There was a problem hiding this comment.
The link target ../dataSourcesAndSinks/ points to a directory. To avoid broken links and be consistent with other docs, link to a concrete page (e.g., ../dataSourcesAndSinks/connectors.md or whichever page you intend).
| This uses the Zingg Enterprise Python API and all [file formats and data sources and sinks](../dataSourcesAndSinks/) are supported within Microsoft Fabric with **Zingg Enterprise** including additional advanced features and support. | |
| This uses the Zingg Enterprise Python API and all [file formats and data sources and sinks](../dataSourcesAndSinks/connectors.md) are supported within Microsoft Fabric with **Zingg Enterprise** including additional advanced features and support. |
| You can access all the supported data sources like Parquet, Delta tables, and Unity Catalog (for governed Delta tables) while running **Zingg Community version**. | ||
|
|
There was a problem hiding this comment.
This claims Zingg Community can access “Unity Catalog (for governed Delta tables)”, but the only Unity Catalog-specific pipe currently documented is zinggEC.enterprise.common.epipes.UCPipe (Enterprise). Please adjust the edition wording or add a brief explanation of how Community reads UC-governed tables (with the corresponding Pipe/API reference) so the docs don’t imply unsupported functionality.
| You can access all the supported data sources like Parquet, Delta tables, and Unity Catalog (for governed Delta tables) while running **Zingg Community version**. | |
| You can access all the supported data sources like Parquet and Delta tables while running **Zingg Community version**. | |
| For Unity Catalog-governed Delta tables, use **Zingg Enterprise version**, which provides the Unity Catalog-specific `zinggEC.enterprise.common.epipes.UCPipe`. |
| You can access all the supported data sources like parquet and other file formats while running **Zingg Community version**. **Zingg Enterprise version** supports additional advanced features. | ||
|
|
||
| Please check the various ways in which you can run **Zingg Community version on Microsoft Fabric** [here](../running/running-on-fabric.md) |
There was a problem hiding this comment.
Minor consistency: “parquet” is lowercased here, but elsewhere in the docs file formats are capitalized (e.g., “Parquet” in dataSourcesAndSinks/databricks.md). Consider capitalizing it for consistency, and add trailing punctuation to the sentence with the link.
| You can access all the supported data sources like parquet and other file formats while running **Zingg Community version**. **Zingg Enterprise version** supports additional advanced features. | |
| Please check the various ways in which you can run **Zingg Community version on Microsoft Fabric** [here](../running/running-on-fabric.md) | |
| You can access all the supported data sources like Parquet and other file formats while running **Zingg Community version**. **Zingg Enterprise version** supports additional advanced features. | |
| Please check the various ways in which you can run **Zingg Community version on Microsoft Fabric** [here](../running/running-on-fabric.md). |
| ## For running the Zingg Community version on Databricks: | ||
|
|
||
| This uses the Zingg Community Python API and an [example notebook](../../examples/databricks/FebrlExample.ipynb) and a [step by step guide](https://www.zingg.ai/documentation-article/identity-resolution-on-databricks-for-customer-360) is available. | ||
| This uses the Zingg Community Python API and supports Delta tables as well as Unity Catalog (for governed Delta tables) using UCPipe. An [example notebook](../../examples/databricks/FebrlExample.ipynb) and a [step by step guide](https://www.zingg.ai/documentation-article/identity-resolution-on-databricks-for-customer-360) is available. |
There was a problem hiding this comment.
The text says the Community Python API supports Unity Catalog “using UCPipe”, but UCPipe is documented as an enterprise pipe (zinggEC.enterprise.common.epipes.UCPipe). Please clarify which edition actually supports UC + UCPipe, and either (a) move this UC/UCPipe mention to the Enterprise section, or (b) describe the Community-compatible approach (and link to the correct Pipe/API docs).
| ## For running the Zingg Enterprise version on Databricks: | ||
|
|
||
| This uses the Zingg Enterprise Python API and all [file formats and data sources and sinks](../dataSourcesAndSinks/) are supported within Databricks with **Zingg Enterprise** including Unity Catalog, Delta file format and InMemory. | ||
| This uses the Zingg Enterprise Python API and all [file formats and data sources and sinks](../dataSourcesAndSinks/) are supported within Databricks with **Zingg Enterprise** including Delta tables, Unity Catalog (for governed Delta tables), and InMemory. |
There was a problem hiding this comment.
The link target ../dataSourcesAndSinks/ points to a directory; elsewhere in the docs links are to a specific page (e.g., dataSourcesAndSinks/connectors.md). This directory link is likely to be broken depending on the site generator—please link to the intended page explicitly.
| This uses the Zingg Enterprise Python API and all [file formats and data sources and sinks](../dataSourcesAndSinks/) are supported within Databricks with **Zingg Enterprise** including Delta tables, Unity Catalog (for governed Delta tables), and InMemory. | |
| This uses the Zingg Enterprise Python API and all [file formats and data sources and sinks](../dataSourcesAndSinks/connectors.md) are supported within Databricks with **Zingg Enterprise** including Delta tables, Unity Catalog (for governed Delta tables), and InMemory. |
| # Running on Fabric | ||
|
|
||
| You can run Zingg on Microsoft Fabric directly using the Fabric notebook interface. | ||
| You can run the **Zingg Community Version** on Microsoft Fabric directly using the Fabric notebook interface. |
There was a problem hiding this comment.
This page’s front matter only sets description, but other pages under docs/running/ define at least title, parent, and nav_order (e.g., running/databricks.md, running/azure.md). Without these, this page may not appear correctly in navigation—consider adding the missing front-matter keys to match the rest of the section.
Add Microsoft Fabric docs and Databricks UCsupport. fixes #1295