The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi,
I would like to try KQL Database within Fabric workspace to load json files for ETL metadata driven framework in Engineering experience.
I have created a new KQL Database in the same workspace: adf-metadata
Created new table from local file: apiIngestion
I wanted to read data from Data Factory using Lookup activity but got an error.:
It is weird, cause I do not manage a connection string. It is done automatically by Fabric as I use the KQL database in the same Fabric workspace.
I tried to write a table name manually but did not work.
I tried to write a query manualy but did not work.
I tried to create new KQL database with a name: adfMetadata but did not work.
11210:
Failed to navigate tables from Kusto database 'eeebfcb9-d71a-4016-90fa-0f799c3a9224'. Error: Kusto Connection String Builder has some invalid or conflicting properties: Can't communicate with 'trdmtava71hzcn0eqeb18t.z6.kusto.fabric.microsoft.com' as this hostname is currently not trusted; please see https://aka.ms/kustotrustedendpoints.. ', Please consult Kusto Connection String documentation at https://docs.microsoft.com/en-us/azure/kusto/api/connection-strings/kusto Kusto Connection String Builder has some invalid or conflicting properties: Can't communicate with 'trdmtava71hzcn0eqeb18t.z6.kusto.fabric.microsoft.com' as this hostname is currently not trusted; please see https://aka.ms/kustotrustedendpoints.. ', Please consult Kusto Connection String documentation at https://docs.microsoft.com/en-us/azure/kusto/api/connection-strings/kusto
Solved! Go to Solution.
This error of invalid Kusto connection string building, is identified as a bug, and is being fixed, sorry for the inconvenience.
This error of invalid Kusto connection string building, is identified as a bug, and is being fixed, sorry for the inconvenience.
Thank you, @ajarora,
Is there a way to track the issue? Perhaps through a GitHub PR or some other method?
User | Count |
---|---|
17 | |
16 | |
6 | |
2 | |
2 |
User | Count |
---|---|
43 | |
23 | |
16 | |
9 | |
6 |