Repository navigation
There is no Synapse connector #31670
Replies: 1 comment
|
If you're using the OpenMetadata distribution, that missing option is expected: its UI service list explicitly includes Synapse under The slow Azure SQL ingestion is a separate question; successfully establishing an SQL connection doesn't establish that its metadata queries are appropriate for your Synapse pool. Before changing timeouts or increasing parallelism, could you share the OpenMetadata and ingestion-package versions, whether this is a dedicated or serverless SQL pool, and the operation where ingestion spends its time? Redacted logs showing whether it's database/schema discovery, table metadata, or profiling would narrow this down considerably. I wouldn't promise that selecting Azure SQL is an equivalent replacement for the dedicated connector without checking that path against your pool type. |
Uh oh!
There was an error while loading. Please reload this page.
I see no Synapse connector option , is this normal? I tried connect to Synapse using the Azure SQL connector , and the ingestion is insanely slow.
All reactions