Skip to content

Commit

Permalink
Add external links
Browse files Browse the repository at this point in the history
  • Loading branch information
pritishpai committed Jan 29, 2025
1 parent b530eba commit d4d544e
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/ucx/docs/process/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -305,13 +305,13 @@ Upon the first update, the cloned pipeline will copy over all the data and check
- Delta
- Autoloader
- If your pipeline uses Autoloader with file notification events, do not run the original HMS pipeline after cloning as this will cause some file notification events to be dropped from the UC clone. If the HMS original was started accidentally, missed files can be backfilled by using the `cloudFiles.backfillInterval` option in Autoloader.
- Kafka where "kafka.group.id" is not set
- Kinesis where "consumerMode" is not "efo"
- Kafka where `kafka.group.id` is not set
- Kinesis where `consumerMode` is not "efo"
- Maintenance is automatically paused (for both pipelines) while migration is in progress
- If an Autoloader source specifies an explicit cloudFiles.schemaLocation, mergeSchema needs to be set to true for the HMS original and UC clone to operate concurrently.
- Pipelines that publish tables to custom schemas are not supported.
- On tables cloned to UC, time travel queries are undefined when querying by timestamp to versions originally written on HMS. Time travel queries by version will work correctly, as will time travel queries by timestamp to versions written on UC.
- All existing limitations of using DLT on UC.
- Existing UC limitations.
- [All existing limitations](https://docs.databricks.com/en/delta-live-tables/unity-catalog.html#limitations) of using DLT on UC.
- [Existing UC limitations](https://docs.databricks.com/en/data-governance/unity-catalog/index.html#limitations)
- If tables in the HMS pipeline specify storage locations (using the "path" parameter in Python or the LOCATION clause in SQL), the configuration "pipelines.migration.ignoreExplicitPath" can be set to "true" to ignore the parameter in the cloned pipeline.

0 comments on commit d4d544e

Please sign in to comment.