When creating KustoConnectionStringBuilder for ICslAdminProvider, when do we use connection string vs Ingest url? whats the difference between two? I know to use .purge command we need to use ingest url, where when using .set command we use connection string. I didnt find anything in the docs. Please provide me with the explanation or if there is doc link for it. Thanks

Hello @Ankit Awadhiya , Microsoft provides multiple SDKs for working with Azure Data Explorer: If you want to ingest data, try Kusto.Ingest : Microsoft.Azure.Kusto.Ingest library is a .NET 4.7.2 library for ingesting data into your cluster. Here is a blog post explaining how to use this SDK. It references the ingestion URL for direct or queued ingestion. The ICslAdminProvider class you mention is part of the Kusto.Data library: You create either a query client ( ICslQueryProvider ) or a management command provider ( ICslAdminProvider ) from a connection string object pointing at the Kusto engine service The Kusto Client SDK (Kusto.Data) exposes a programmatic API similar to ADO.NET, so using it should feel natural for users experienced with .NET. You can then issue data queries or management commands by specifying the appropriate Kusto Query Language string. I'm not sure about your statement regarding the .purge command. It seems this is something related to the admin provider: using var client = KustoClientFactory.CreateCslAdminProvider(connectionStringBuilder); var command = CslCommandGenerator.GeneratePurgeTableCommand("tableName"); using var reader = client.ExecuteControlCommand(command); I recommend experimenting with the SDKs and some test data first. If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.

Management command vs query command

Accepted answer

Sander van de Velde | MVP 32,736 Reputation points MVP

2023-09-18T20:55:52.0633333+00:00
Hello @Ankit Awadhiya ,

Microsoft provides multiple SDKs for working with Azure Data Explorer:

If you want to ingest data, try Kusto.Ingest:

Microsoft.Azure.Kusto.Ingest library is a .NET 4.7.2 library for ingesting data into your cluster.

Here is a blog post explaining how to use this SDK. It references the ingestion URL for direct or queued ingestion.

The ICslAdminProvider class you mention is part of the Kusto.Data library:

You create either a query client (ICslQueryProvider) or a management command provider (ICslAdminProvider) from a connection string object pointing at the Kusto engine service

The Kusto Client SDK (Kusto.Data) exposes a programmatic API similar to ADO.NET, so using it should feel natural for users experienced with .NET. You can then issue data queries or management commands by specifying the appropriate Kusto Query Language string.

I'm not sure about your statement regarding the .purge command.

It seems this is something related to the admin provider:

using var client = KustoClientFactory.CreateCslAdminProvider(connectionStringBuilder); var command = CslCommandGenerator.GeneratePurgeTableCommand("tableName"); using var reader = client.ExecuteControlCommand(command);

I recommend experimenting with the SDKs and some test data first.

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.
Please sign in to rate this answer.
Ankit Awadhiya 55 Reputation points

2023-09-18T21:26:55.4566667+00:00

Like for example here:

We are using ingest url, as a case of admin provider.

but here on the other hand, we are using connection string not the ingest url. So I am confused when to use ingest url and when to use connection string with the admin provider and whats the difference between the two.

Sander van de Velde | MVP 32,736 Reputation points MVP

2023-09-18T22:05:36.5833333+00:00

I agree that the first example, part of this documentation could be confusing:

// Connect to the Data Management service #connect "https://ingest-[YourClusterName].[region].kusto.windows.net" // To purge table records .purge table [TableName] records in database [DatabaseName] with (noregrets='true') <| [Predicate] // To purge materialized view records .purge materialized-view [MaterializedViewName] records in database [DatabaseName] with (noregrets='true') <| [Predicate]

But these are KQL examples and should be executed using the ADX Query tooling in the portal.

Actually, that purge command works even without the #connect line if you have admin rights.

On the same page, the other example tell why this line is added:

// Connect to the Data Management service - this command only works in Kusto.Explorer #connect "https://ingest-[YourClusterName].[region].kusto.windows.net"

So, please ignore that line and stick to the documentation regarding the SDK and the different parts of it (ingesting, querying, admin tasks).

Ankit Awadhiya 55 Reputation points

2023-09-18T23:25:35.9533333+00:00

I am still confused about this. Maybe I will do some more testing on this.

My use case is that I am using .net sdk ICslAdminProvider to create admin commands and execute those commands.

With this admin provider, for the purge command I have to create KustoClientStringBuilder by passing IngestUri, and for other admin commands, I have to pass the connectionString.

So that I don't understand.

Sander van de Velde | MVP 32,736 Reputation points MVP

2023-09-19T07:01:55.6233333+00:00

Hello @Ankit Awadhiya ,

From the documentation I read and the experience I have with ingestion, the ingestion URL is only used by the Ingestion SDK.

The Adminprovider needs connection string like access:

...a management command provider (ICslAdminProvider) from a connection string object pointing at the Kusto engine service...

Also, this is seen in the examples:

var kustoUri = "https://<clusterName>.<region>.kusto.windows.net"; var connectionStringBuilder = new KustoConnectionStringBuilder(kustoUri).WithAadUserPromptAuthentication(); using var client = KustoClientFactory.CreateCslAdminProvider(connectionStringBuilder);

This seems to include the purge logic.

Ankit Awadhiya 55 Reputation points

2023-09-19T20:24:14.0233333+00:00

Thanks for the explanation.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Management command vs query command

0 additional answers

Your answer