Skip to main content
GuideServerConfigure and deploy Tabsdata servers on your machine.TutorialsConfigure data integration workflows within a running Tabsdata server.Advanced TutorialsBuild end-to-end workflows between two specific systems.API ReferenceCLI ReferenceRelease Notes
Version: 2.0.0

DatabricksSrc

class
class DatabricksSrc(
queries: QueriesSpec,
initial_values: BasicDictSpec | None = None,
src_cfg: SrcCfgSpec | None = None,
)

Bases: Src

Categories: source

Databricks source for @publisher -- one output slot per query.

Every table this source publishes automatically carries two metadata columns: @td.sql.query, the text of the query that produced the row, and @td.sql.initial_values, the JSON serialization of the bind values that query ran with (an empty JSON object when it has no binds). Setting the src_cfg key tabsdata.src_metadata.drop to True leaves them off.

Parameters

parameter
queriesQueriesSpec (list[str])

SQL statements, one output slot per entry, run through the Statement Execution API.

parameter
initial_valuesBasicDictSpec | None (dict[str, str | int | float | bool] | None)

Optional {bind_name: value} seed dict. Each name binds into the query as a :var statement parameter (typed, native binding); it seeds the first run only, after which the plugin reads ctx.get_attr(bind_name) and the function persists new values with ctx.set_attr(bind_name, ...).

parameter
src_cfgSrcCfgSpec | None (Mapping[Literal['databricks.logging_level', 'tabsdata.src_metadata.drop'], Any] | None)

Optional connector config; supported keys are databricks.logging_level and tabsdata.src_metadata.drop.