feat: add multi-catalog and multi-schema support for Stitch integration #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit implements the ability to scan and configure Stitch across multiple Databricks catalogs and schemas in a single operation, while maintaining full backward compatibility with single-location usage.
Key changes:
Core functionality (stitch_tools.py):
Command interface (setup_stitch.py):
Type safety (url_utils.py):
Testing (test_stitch_tools.py):
Usage examples:
Single location (backward compatible): /setup-stitch --catalog_name prod --schema_name crm
Multiple locations: /setup-stitch --targets prod.crm,prod.ecommerce,analytics.customers --output_catalog prod
Demo:
NOTE: Relevant tables' columns were already tagged with PII info
Databricks notebook screenshots after successful multi-catalog multi-schema stitch operation:





