Execute a SQL Query

Execute a SQL Query activity in the Databricks connector.

Compatibilidade do projeto

Windows | Multiplataforma

Visão geral

Description	Método do API	Caminho da API
Run a SQL statement on a Databricks SQL warehouse. Requires warehouse_id and statement; rows come back under result.data_array with column metadata in manifest.schema.	Postar	/statements

Entrada

Parâmetro	Description	Tipo de dados
SQL Statement *	The SQL statement to execute. For example, SELECT * FROM hive_metastore.default.p_order LIMIT 10.	String
Warehouse ID *	ID of the SQL warehouse to run the statement on. For example, a1b2c3d4e5f6a7b8.	String
Catálogo	Catalog used as the default for the statement. For example, main.	String
Esquema	Schema used as the default for the statement. For example, default.	String
Wait Timeout	How long to wait synchronously, 0s or 5s-50s. Default: 30s.	String
On Wait Timeout	CONTINUE returns a statement_id to poll; CANCEL aborts the statement. For long queries, set Wait Timeout to 0s and On Wait Timeout to CONTINUE, then poll with Get SQL Statement Result. Allowed values: CONTINUE, CANCEL. Default: CONTINUE.	String
Row Limit	Maximum number of rows to return. For example, 1000.	Número inteiro
Byte Limit	Maximum result size in bytes. For example, 10485760.	Número inteiro
Disposition	INLINE returns data in the response; EXTERNAL_LINKS returns presigned URLs. Allowed values: INLINE, EXTERNAL_LINKS. Default: INLINE.	String
Format	Result serialization format. Allowed values: JSON_ARRAY, ARROW_STREAM, CSV. Default: JSON_ARRAY.	String
Parâmetros	Named parameter markers, for example [{"name":"p","value":"1","type":"INT"}].	Matriz

* Required parameter.

Saída

Parâmetro	Description	Tipo de dados
Statement ID	Server-assigned statement id; poll with Get Statement.	String
Status	Execution state: PENDING, RUNNING, SUCCEEDED, FAILED, CANCELED, CLOSED.	object
Manifest	Result schema, chunk layout and row counts.	object
Resultado	Result payload; row data is under result.data_array.	object

Observação:

You might see variations in the output depending on where you run the activity. In API workflows and Maestro Flow, a single response object containing all the fields is returned. In RPA workflows, not all fields are exposed, but you can still retrieve them from the exposed response object.