DBI methods for Kusto table management
# S4 method for AzureKustoConnection,character
dbReadTable(conn, name, ...)# S4 method for AzureKustoConnection,ANY
dbWriteTable(conn, name, value, method, ...)
# S4 method for AzureKustoConnection
dbCreateTable(conn, name, fields, ..., row.names = NULL, temporary = FALSE)
# S4 method for AzureKustoConnection,ANY
dbRemoveTable(conn, name, ...)
# S4 method for AzureKustoConnection
dbListTables(conn, ...)
# S4 method for AzureKustoConnection,ANY
dbExistsTable(conn, name, ...)
For dbReadTable, an in-memory data frame containing the table.
An AzureKustoConnection object.
A string containing a table name.
Further arguments passed to run_query.
For dbWriteTable, a data frame to be written to a Kusto table.
For dbWriteTable, the ingestion method to use to write the table. See ingest_local.
For dbCreateTable, the table specification: either a named character vector, or a data frame of sample values.
For dbCreateTable, the row names. Not used.
For dbCreateTable, whether to create a temporary table. Must be FALSE for Kusto.
These functions read, write, create and delete a table, list the tables in a Kusto database, and check for table existence. With the exception of dbWriteTable, they ultimately call run_query which does the actual work of communicating with the Kusto server. dbWriteTable calls ingest_local to write the data to the server; note that it only supports ingesting a local data frame, as per the DBI spec.
Kusto does not have the concept of temporary tables, so calling dbCreateTable with temporary set to anything other than FALSE will generate an error.
dbReadTable and dbWriteTable are likely to be of limited use in practical scenarios, since Kusto tables tend to be much larger than available memory.
AzureKusto-connection, dbConnect, run_query, ingest_local