AzureKusto implements a subset of the DBI specification for interfacing with databases in R. The following methods are supported:
Connections: dbConnect, dbDisconnect, dbCanConnect
Table management: dbExistsTable, dbCreateTable, dbRemoveTable, dbReadTable, dbWriteTable
Querying: dbGetQuery, dbSendQuery, dbFetch, dbSendStatement, dbExecute, dbListFields, dbColumnInfo
Kusto is quite different to the SQL databases that DBI targets, which affects the behaviour of certain DBI methods and renders other moot.
Kusto is connectionless. dbConnect simply wraps a database endpoint object, created with kusto_database_endpoint. Similarly, dbDisconnect always returns TRUE. dbCanConnect attempts to check if querying the database will succeed, but this may not be accurate.
Temporary tables are not a Kusto concept, so dbCreateTable(*, temporary=TRUE) will throw an error.
It only supports synchronous queries, with a default timeout of 4 minutes. dbSendQuery and dbSendStatement will wait for the query to execute, rather than returning immediately. The object returned contains the full result of the query, which dbFetch extracts.
The Kusto Query Language (KQL) is not SQL, and so higher-level SQL methods are not implemented.