DB - Databricks SQL

overview databricks integration enables an edge system to connect with databricks supported communication outbound (write from edge to databricks) yes inbound (read from databricks to edge) no configurations variable detail required name enter a name for the connector yes connection string connection string for the data source name for personal token authentication, use the following format token\ personal access token\@server hostname\ port number/http path?param1=value1\&param2=value2 for m2m oauth authentication, use the following format server hostname\ port number/http path?authtype=oauthm2m\&clientid=client id\&clientsecret=client secret yes table table name yes mapping data from a predefined table could be mapped into a custom one example {"from" "to"} where "from" is a column from predefined table, and "to" is a column from destination table see docid\ ycgpmzedeewio4mes3mto to learn more no create table if selected and table doesn't exist, the table is created with the necessary format see docid\ ycgpmzedeewio4mes3mto to learn more no bulk insert count to enable this option, enter the number of messages to group together and send as one bulk insert statement enabling this option can improve how quickly data is processed when dealing with high volumes of tags no commit timeout timeout (in milliseconds) for committing bulk inserts no throttling limit set a limit on the number of outbound messages per second if sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost no persistent storage if enabled, messages in the outbound queue are stored on disk if there are interruptions in connection or power loss, messages will be retained and eventually sent when the connection is restored no queue mode select the sequence of data transfer fifo or lifo selecting fifo (first in first out) will send the earliest message first selecting lifo (last in first out) will send the latest message first no