ohad bitton

This usually rises when a user tries to work from Synapse using this repo connector coordinates. Meaning using `df.write.format("com.microsoft.kusto.spark.datasource")` instead of `spark.write.format("com.microsoft.kusto.spark.synapse.datasource")` We intentionally don’t allow users to use the...

Just for clarification we have different solutions that could be used here - you can create yourself blobs and set an EventGrid connection to the cluster with streaming ingest https://docs.microsoft.com/en-us/azure/data-explorer/ingest-data-event-grid?tabs=adx

The current implementation is now good for streaming support but the discussion for not implementing this is for avoiding wrong usage with spark streaming New version 3.1.0 allows 2 new...

This actually shouldnt concern most people - with newer version - with retries implemented and the ability to set the option KUSTO_MAXIMAL_EXTENTS_COUNT_FOR_SPLIT_MERGE_PER_NODE "maximalExtentsCountForSplitMergePerNode" this shouldn't be a problem.

Please call these by the real change and add a description of what the change is and only add that it solves the issue at last line of the description....

lets add to the documentation that we suggest to provide a value here as estimation can take up to 6 seconds - or is too much details for a user?

Hi @The-Funk Cole, We decided that any future change in our httpClient should move to align with other Azure SDKs httpClient usage which is using projectReactor and the underlying reactor-netty...

@The-Funk , are the thumbs up meaning you want to implement it our way or wait for us to complete this task some time in the future?

Yea this sounds good - we don't do client pools - you can see the httpclient is already a member of the KustoClient - so no work here You might...

Hey @The-Funk As i said today in the PR - main issue here would be to test it well would you like to take this effort as well ? If...