Forum Discussion
Issue Writing to OneLake-Enabled KQL Database Delta Tables
Hi Anonymous The code you shared is taking around 30–40 seconds to append a single record. Could you help me understand why this is taking so long? I’m looking to ingest the data as quickly as possible. Is there any alternative approach that would allow faster ingestion?
Hi Dinzz
That behavior is expected and not related to your code itself. The Kusto Spark connector (even in Direct ingestion mode) is optimized for batch ingestion, not for low-latency, row-by-row writes. Each Spark write triggers to authentication and token validation, Ingestion orchestration in KQL and Extent creation and commit on the KQL side
Because of this, ingesting a single record can easily take 30–40 seconds, which is expected behavior.
Currently, there is no supported way in Fabric to ingest single records into KQL with millisecond-level latency, and direct Delta writes are intentionally blocked.
Thanks.
hi Anonymous thank you for the explanation it helped a lot
Hi Dinzz
Thank you for reaching out to the Microsoft Fabric Forum Community.
I hope the information provided was helpful. If you still have questions, please don't hesitate to reach out to the community.
Hi Dinzz
Hope everything’s going smoothly on your end. I wanted to check if the issue got sorted. if you have any other issues please reach community.