published on Friday, May 29, 2026 by Pulumi
published on Friday, May 29, 2026 by Pulumi
Create FeatureEngineeringKafkaConfig Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new FeatureEngineeringKafkaConfig(name: string, args: FeatureEngineeringKafkaConfigArgs, opts?: CustomResourceOptions);@overload
def FeatureEngineeringKafkaConfig(resource_name: str,
args: FeatureEngineeringKafkaConfigArgs,
opts: Optional[ResourceOptions] = None)
@overload
def FeatureEngineeringKafkaConfig(resource_name: str,
opts: Optional[ResourceOptions] = None,
auth_config: Optional[FeatureEngineeringKafkaConfigAuthConfigArgs] = None,
bootstrap_servers: Optional[str] = None,
subscription_mode: Optional[FeatureEngineeringKafkaConfigSubscriptionModeArgs] = None,
backfill_source: Optional[FeatureEngineeringKafkaConfigBackfillSourceArgs] = None,
extra_options: Optional[Mapping[str, str]] = None,
key_schema: Optional[FeatureEngineeringKafkaConfigKeySchemaArgs] = None,
provider_config: Optional[FeatureEngineeringKafkaConfigProviderConfigArgs] = None,
value_schema: Optional[FeatureEngineeringKafkaConfigValueSchemaArgs] = None)func NewFeatureEngineeringKafkaConfig(ctx *Context, name string, args FeatureEngineeringKafkaConfigArgs, opts ...ResourceOption) (*FeatureEngineeringKafkaConfig, error)public FeatureEngineeringKafkaConfig(string name, FeatureEngineeringKafkaConfigArgs args, CustomResourceOptions? opts = null)
public FeatureEngineeringKafkaConfig(String name, FeatureEngineeringKafkaConfigArgs args)
public FeatureEngineeringKafkaConfig(String name, FeatureEngineeringKafkaConfigArgs args, CustomResourceOptions options)
type: databricks:FeatureEngineeringKafkaConfig
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
resource "databricks_featureengineeringkafkaconfig" "name" {
# resource properties
}Parameters
- name string
- The unique name of the resource.
- args FeatureEngineeringKafkaConfigArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args FeatureEngineeringKafkaConfigArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args FeatureEngineeringKafkaConfigArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args FeatureEngineeringKafkaConfigArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args FeatureEngineeringKafkaConfigArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var featureEngineeringKafkaConfigResource = new Databricks.FeatureEngineeringKafkaConfig("featureEngineeringKafkaConfigResource", new()
{
AuthConfig = new Databricks.Inputs.FeatureEngineeringKafkaConfigAuthConfigArgs
{
MtlsConfig = new Databricks.Inputs.FeatureEngineeringKafkaConfigAuthConfigMtlsConfigArgs
{
KeyPasswordRef = new Databricks.Inputs.FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeyPasswordRefArgs
{
Key = "string",
Scope = "string",
},
KeystoreLocation = "string",
KeystorePasswordRef = new Databricks.Inputs.FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeystorePasswordRefArgs
{
Key = "string",
Scope = "string",
},
TruststoreLocation = "string",
TruststorePasswordRef = new Databricks.Inputs.FeatureEngineeringKafkaConfigAuthConfigMtlsConfigTruststorePasswordRefArgs
{
Key = "string",
Scope = "string",
},
DisableHostnameVerification = false,
},
UcServiceCredentialName = "string",
},
BootstrapServers = "string",
SubscriptionMode = new Databricks.Inputs.FeatureEngineeringKafkaConfigSubscriptionModeArgs
{
Assign = "string",
Subscribe = "string",
SubscribePattern = "string",
},
BackfillSource = new Databricks.Inputs.FeatureEngineeringKafkaConfigBackfillSourceArgs
{
DeltaTableName = "string",
DeltaTableSource = new Databricks.Inputs.FeatureEngineeringKafkaConfigBackfillSourceDeltaTableSourceArgs
{
FullName = "string",
DataframeSchema = "string",
EntityColumns = new[]
{
"string",
},
FilterCondition = "string",
TimeseriesColumn = "string",
TransformationSql = "string",
},
},
ExtraOptions =
{
{ "string", "string" },
},
KeySchema = new Databricks.Inputs.FeatureEngineeringKafkaConfigKeySchemaArgs
{
JsonSchema = "string",
},
ProviderConfig = new Databricks.Inputs.FeatureEngineeringKafkaConfigProviderConfigArgs
{
WorkspaceId = "string",
},
ValueSchema = new Databricks.Inputs.FeatureEngineeringKafkaConfigValueSchemaArgs
{
JsonSchema = "string",
},
});
example, err := databricks.NewFeatureEngineeringKafkaConfig(ctx, "featureEngineeringKafkaConfigResource", &databricks.FeatureEngineeringKafkaConfigArgs{
AuthConfig: &databricks.FeatureEngineeringKafkaConfigAuthConfigArgs{
MtlsConfig: &databricks.FeatureEngineeringKafkaConfigAuthConfigMtlsConfigArgs{
KeyPasswordRef: &databricks.FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeyPasswordRefArgs{
Key: pulumi.String("string"),
Scope: pulumi.String("string"),
},
KeystoreLocation: pulumi.String("string"),
KeystorePasswordRef: &databricks.FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeystorePasswordRefArgs{
Key: pulumi.String("string"),
Scope: pulumi.String("string"),
},
TruststoreLocation: pulumi.String("string"),
TruststorePasswordRef: &databricks.FeatureEngineeringKafkaConfigAuthConfigMtlsConfigTruststorePasswordRefArgs{
Key: pulumi.String("string"),
Scope: pulumi.String("string"),
},
DisableHostnameVerification: pulumi.Bool(false),
},
UcServiceCredentialName: pulumi.String("string"),
},
BootstrapServers: pulumi.String("string"),
SubscriptionMode: &databricks.FeatureEngineeringKafkaConfigSubscriptionModeArgs{
Assign: pulumi.String("string"),
Subscribe: pulumi.String("string"),
SubscribePattern: pulumi.String("string"),
},
BackfillSource: &databricks.FeatureEngineeringKafkaConfigBackfillSourceArgs{
DeltaTableName: pulumi.String("string"),
DeltaTableSource: &databricks.FeatureEngineeringKafkaConfigBackfillSourceDeltaTableSourceArgs{
FullName: pulumi.String("string"),
DataframeSchema: pulumi.String("string"),
EntityColumns: pulumi.StringArray{
pulumi.String("string"),
},
FilterCondition: pulumi.String("string"),
TimeseriesColumn: pulumi.String("string"),
TransformationSql: pulumi.String("string"),
},
},
ExtraOptions: pulumi.StringMap{
"string": pulumi.String("string"),
},
KeySchema: &databricks.FeatureEngineeringKafkaConfigKeySchemaArgs{
JsonSchema: pulumi.String("string"),
},
ProviderConfig: &databricks.FeatureEngineeringKafkaConfigProviderConfigArgs{
WorkspaceId: pulumi.String("string"),
},
ValueSchema: &databricks.FeatureEngineeringKafkaConfigValueSchemaArgs{
JsonSchema: pulumi.String("string"),
},
})
resource "databricks_featureengineeringkafkaconfig" "featureEngineeringKafkaConfigResource" {
auth_config = {
mtls_config = {
key_password_ref = {
key = "string"
scope = "string"
}
keystore_location = "string"
keystore_password_ref = {
key = "string"
scope = "string"
}
truststore_location = "string"
truststore_password_ref = {
key = "string"
scope = "string"
}
disable_hostname_verification = false
}
uc_service_credential_name = "string"
}
bootstrap_servers = "string"
subscription_mode = {
assign = "string"
subscribe = "string"
subscribe_pattern = "string"
}
backfill_source = {
delta_table_name = "string"
delta_table_source = {
full_name = "string"
dataframe_schema = "string"
entity_columns = ["string"]
filter_condition = "string"
timeseries_column = "string"
transformation_sql = "string"
}
}
extra_options = {
"string" = "string"
}
key_schema = {
json_schema = "string"
}
provider_config = {
workspace_id = "string"
}
value_schema = {
json_schema = "string"
}
}
var featureEngineeringKafkaConfigResource = new FeatureEngineeringKafkaConfig("featureEngineeringKafkaConfigResource", FeatureEngineeringKafkaConfigArgs.builder()
.authConfig(FeatureEngineeringKafkaConfigAuthConfigArgs.builder()
.mtlsConfig(FeatureEngineeringKafkaConfigAuthConfigMtlsConfigArgs.builder()
.keyPasswordRef(FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeyPasswordRefArgs.builder()
.key("string")
.scope("string")
.build())
.keystoreLocation("string")
.keystorePasswordRef(FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeystorePasswordRefArgs.builder()
.key("string")
.scope("string")
.build())
.truststoreLocation("string")
.truststorePasswordRef(FeatureEngineeringKafkaConfigAuthConfigMtlsConfigTruststorePasswordRefArgs.builder()
.key("string")
.scope("string")
.build())
.disableHostnameVerification(false)
.build())
.ucServiceCredentialName("string")
.build())
.bootstrapServers("string")
.subscriptionMode(FeatureEngineeringKafkaConfigSubscriptionModeArgs.builder()
.assign("string")
.subscribe("string")
.subscribePattern("string")
.build())
.backfillSource(FeatureEngineeringKafkaConfigBackfillSourceArgs.builder()
.deltaTableName("string")
.deltaTableSource(FeatureEngineeringKafkaConfigBackfillSourceDeltaTableSourceArgs.builder()
.fullName("string")
.dataframeSchema("string")
.entityColumns("string")
.filterCondition("string")
.timeseriesColumn("string")
.transformationSql("string")
.build())
.build())
.extraOptions(Map.of("string", "string"))
.keySchema(FeatureEngineeringKafkaConfigKeySchemaArgs.builder()
.jsonSchema("string")
.build())
.providerConfig(FeatureEngineeringKafkaConfigProviderConfigArgs.builder()
.workspaceId("string")
.build())
.valueSchema(FeatureEngineeringKafkaConfigValueSchemaArgs.builder()
.jsonSchema("string")
.build())
.build());
feature_engineering_kafka_config_resource = databricks.FeatureEngineeringKafkaConfig("featureEngineeringKafkaConfigResource",
auth_config={
"mtls_config": {
"key_password_ref": {
"key": "string",
"scope": "string",
},
"keystore_location": "string",
"keystore_password_ref": {
"key": "string",
"scope": "string",
},
"truststore_location": "string",
"truststore_password_ref": {
"key": "string",
"scope": "string",
},
"disable_hostname_verification": False,
},
"uc_service_credential_name": "string",
},
bootstrap_servers="string",
subscription_mode={
"assign": "string",
"subscribe": "string",
"subscribe_pattern": "string",
},
backfill_source={
"delta_table_name": "string",
"delta_table_source": {
"full_name": "string",
"dataframe_schema": "string",
"entity_columns": ["string"],
"filter_condition": "string",
"timeseries_column": "string",
"transformation_sql": "string",
},
},
extra_options={
"string": "string",
},
key_schema={
"json_schema": "string",
},
provider_config={
"workspace_id": "string",
},
value_schema={
"json_schema": "string",
})
const featureEngineeringKafkaConfigResource = new databricks.FeatureEngineeringKafkaConfig("featureEngineeringKafkaConfigResource", {
authConfig: {
mtlsConfig: {
keyPasswordRef: {
key: "string",
scope: "string",
},
keystoreLocation: "string",
keystorePasswordRef: {
key: "string",
scope: "string",
},
truststoreLocation: "string",
truststorePasswordRef: {
key: "string",
scope: "string",
},
disableHostnameVerification: false,
},
ucServiceCredentialName: "string",
},
bootstrapServers: "string",
subscriptionMode: {
assign: "string",
subscribe: "string",
subscribePattern: "string",
},
backfillSource: {
deltaTableName: "string",
deltaTableSource: {
fullName: "string",
dataframeSchema: "string",
entityColumns: ["string"],
filterCondition: "string",
timeseriesColumn: "string",
transformationSql: "string",
},
},
extraOptions: {
string: "string",
},
keySchema: {
jsonSchema: "string",
},
providerConfig: {
workspaceId: "string",
},
valueSchema: {
jsonSchema: "string",
},
});
type: databricks:FeatureEngineeringKafkaConfig
properties:
authConfig:
mtlsConfig:
disableHostnameVerification: false
keyPasswordRef:
key: string
scope: string
keystoreLocation: string
keystorePasswordRef:
key: string
scope: string
truststoreLocation: string
truststorePasswordRef:
key: string
scope: string
ucServiceCredentialName: string
backfillSource:
deltaTableName: string
deltaTableSource:
dataframeSchema: string
entityColumns:
- string
filterCondition: string
fullName: string
timeseriesColumn: string
transformationSql: string
bootstrapServers: string
extraOptions:
string: string
keySchema:
jsonSchema: string
providerConfig:
workspaceId: string
subscriptionMode:
assign: string
subscribe: string
subscribePattern: string
valueSchema:
jsonSchema: string
FeatureEngineeringKafkaConfig Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The FeatureEngineeringKafkaConfig resource accepts the following input properties:
- Auth
Config FeatureEngineering Kafka Config Auth Config - Authentication configuration for connection to topics
- Bootstrap
Servers string - A comma-separated list of host/port pairs pointing to Kafka cluster
- Subscription
Mode FeatureEngineering Kafka Config Subscription Mode - Options to configure which Kafka topics to pull data from
- Backfill
Source FeatureEngineering Kafka Config Backfill Source - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- Extra
Options Dictionary<string, string> - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- Key
Schema FeatureEngineering Kafka Config Key Schema - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- Provider
Config FeatureEngineering Kafka Config Provider Config - Configure the provider for management through account provider.
- Value
Schema FeatureEngineering Kafka Config Value Schema - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- Auth
Config FeatureEngineering Kafka Config Auth Config Args - Authentication configuration for connection to topics
- Bootstrap
Servers string - A comma-separated list of host/port pairs pointing to Kafka cluster
- Subscription
Mode FeatureEngineering Kafka Config Subscription Mode Args - Options to configure which Kafka topics to pull data from
- Backfill
Source FeatureEngineering Kafka Config Backfill Source Args - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- Extra
Options map[string]string - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- Key
Schema FeatureEngineering Kafka Config Key Schema Args - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- Provider
Config FeatureEngineering Kafka Config Provider Config Args - Configure the provider for management through account provider.
- Value
Schema FeatureEngineering Kafka Config Value Schema Args - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth_
config object - Authentication configuration for connection to topics
- bootstrap_
servers string - A comma-separated list of host/port pairs pointing to Kafka cluster
- subscription_
mode object - Options to configure which Kafka topics to pull data from
- backfill_
source object - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- extra_
options map(string) - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key_
schema object - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- provider_
config object - Configure the provider for management through account provider.
- value_
schema object - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth
Config FeatureEngineering Kafka Config Auth Config - Authentication configuration for connection to topics
- bootstrap
Servers String - A comma-separated list of host/port pairs pointing to Kafka cluster
- subscription
Mode FeatureEngineering Kafka Config Subscription Mode - Options to configure which Kafka topics to pull data from
- backfill
Source FeatureEngineering Kafka Config Backfill Source - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- extra
Options Map<String,String> - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key
Schema FeatureEngineering Kafka Config Key Schema - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- provider
Config FeatureEngineering Kafka Config Provider Config - Configure the provider for management through account provider.
- value
Schema FeatureEngineering Kafka Config Value Schema - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth
Config FeatureEngineering Kafka Config Auth Config - Authentication configuration for connection to topics
- bootstrap
Servers string - A comma-separated list of host/port pairs pointing to Kafka cluster
- subscription
Mode FeatureEngineering Kafka Config Subscription Mode - Options to configure which Kafka topics to pull data from
- backfill
Source FeatureEngineering Kafka Config Backfill Source - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- extra
Options {[key: string]: string} - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key
Schema FeatureEngineering Kafka Config Key Schema - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- provider
Config FeatureEngineering Kafka Config Provider Config - Configure the provider for management through account provider.
- value
Schema FeatureEngineering Kafka Config Value Schema - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth_
config FeatureEngineering Kafka Config Auth Config Args - Authentication configuration for connection to topics
- bootstrap_
servers str - A comma-separated list of host/port pairs pointing to Kafka cluster
- subscription_
mode FeatureEngineering Kafka Config Subscription Mode Args - Options to configure which Kafka topics to pull data from
- backfill_
source FeatureEngineering Kafka Config Backfill Source Args - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- extra_
options Mapping[str, str] - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key_
schema FeatureEngineering Kafka Config Key Schema Args - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- provider_
config FeatureEngineering Kafka Config Provider Config Args - Configure the provider for management through account provider.
- value_
schema FeatureEngineering Kafka Config Value Schema Args - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth
Config Property Map - Authentication configuration for connection to topics
- bootstrap
Servers String - A comma-separated list of host/port pairs pointing to Kafka cluster
- subscription
Mode Property Map - Options to configure which Kafka topics to pull data from
- backfill
Source Property Map - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- extra
Options Map<String> - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key
Schema Property Map - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- provider
Config Property Map - Configure the provider for management through account provider.
- value
Schema Property Map - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
Outputs
All input properties are implicitly available as output properties. Additionally, the FeatureEngineeringKafkaConfig resource produces the following output properties:
Look up Existing FeatureEngineeringKafkaConfig Resource
Get an existing FeatureEngineeringKafkaConfig resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: FeatureEngineeringKafkaConfigState, opts?: CustomResourceOptions): FeatureEngineeringKafkaConfig@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
auth_config: Optional[FeatureEngineeringKafkaConfigAuthConfigArgs] = None,
backfill_source: Optional[FeatureEngineeringKafkaConfigBackfillSourceArgs] = None,
bootstrap_servers: Optional[str] = None,
extra_options: Optional[Mapping[str, str]] = None,
key_schema: Optional[FeatureEngineeringKafkaConfigKeySchemaArgs] = None,
name: Optional[str] = None,
provider_config: Optional[FeatureEngineeringKafkaConfigProviderConfigArgs] = None,
subscription_mode: Optional[FeatureEngineeringKafkaConfigSubscriptionModeArgs] = None,
value_schema: Optional[FeatureEngineeringKafkaConfigValueSchemaArgs] = None) -> FeatureEngineeringKafkaConfigfunc GetFeatureEngineeringKafkaConfig(ctx *Context, name string, id IDInput, state *FeatureEngineeringKafkaConfigState, opts ...ResourceOption) (*FeatureEngineeringKafkaConfig, error)public static FeatureEngineeringKafkaConfig Get(string name, Input<string> id, FeatureEngineeringKafkaConfigState? state, CustomResourceOptions? opts = null)public static FeatureEngineeringKafkaConfig get(String name, Output<String> id, FeatureEngineeringKafkaConfigState state, CustomResourceOptions options)resources: _: type: databricks:FeatureEngineeringKafkaConfig get: id: ${id}import {
to = databricks_featureengineeringkafkaconfig.example
id = "${id}"
}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Auth
Config FeatureEngineering Kafka Config Auth Config - Authentication configuration for connection to topics
- Backfill
Source FeatureEngineering Kafka Config Backfill Source - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- Bootstrap
Servers string - A comma-separated list of host/port pairs pointing to Kafka cluster
- Extra
Options Dictionary<string, string> - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- Key
Schema FeatureEngineering Kafka Config Key Schema - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- Name string
- (string) - Name that uniquely identifies this Kafka config within the metastore. This will be the identifier used from the Feature object to reference these configs for a feature. Can be distinct from topic name
- Provider
Config FeatureEngineering Kafka Config Provider Config - Configure the provider for management through account provider.
- Subscription
Mode FeatureEngineering Kafka Config Subscription Mode - Options to configure which Kafka topics to pull data from
- Value
Schema FeatureEngineering Kafka Config Value Schema - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- Auth
Config FeatureEngineering Kafka Config Auth Config Args - Authentication configuration for connection to topics
- Backfill
Source FeatureEngineering Kafka Config Backfill Source Args - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- Bootstrap
Servers string - A comma-separated list of host/port pairs pointing to Kafka cluster
- Extra
Options map[string]string - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- Key
Schema FeatureEngineering Kafka Config Key Schema Args - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- Name string
- (string) - Name that uniquely identifies this Kafka config within the metastore. This will be the identifier used from the Feature object to reference these configs for a feature. Can be distinct from topic name
- Provider
Config FeatureEngineering Kafka Config Provider Config Args - Configure the provider for management through account provider.
- Subscription
Mode FeatureEngineering Kafka Config Subscription Mode Args - Options to configure which Kafka topics to pull data from
- Value
Schema FeatureEngineering Kafka Config Value Schema Args - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth_
config object - Authentication configuration for connection to topics
- backfill_
source object - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- bootstrap_
servers string - A comma-separated list of host/port pairs pointing to Kafka cluster
- extra_
options map(string) - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key_
schema object - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- name string
- (string) - Name that uniquely identifies this Kafka config within the metastore. This will be the identifier used from the Feature object to reference these configs for a feature. Can be distinct from topic name
- provider_
config object - Configure the provider for management through account provider.
- subscription_
mode object - Options to configure which Kafka topics to pull data from
- value_
schema object - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth
Config FeatureEngineering Kafka Config Auth Config - Authentication configuration for connection to topics
- backfill
Source FeatureEngineering Kafka Config Backfill Source - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- bootstrap
Servers String - A comma-separated list of host/port pairs pointing to Kafka cluster
- extra
Options Map<String,String> - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key
Schema FeatureEngineering Kafka Config Key Schema - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- name String
- (string) - Name that uniquely identifies this Kafka config within the metastore. This will be the identifier used from the Feature object to reference these configs for a feature. Can be distinct from topic name
- provider
Config FeatureEngineering Kafka Config Provider Config - Configure the provider for management through account provider.
- subscription
Mode FeatureEngineering Kafka Config Subscription Mode - Options to configure which Kafka topics to pull data from
- value
Schema FeatureEngineering Kafka Config Value Schema - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth
Config FeatureEngineering Kafka Config Auth Config - Authentication configuration for connection to topics
- backfill
Source FeatureEngineering Kafka Config Backfill Source - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- bootstrap
Servers string - A comma-separated list of host/port pairs pointing to Kafka cluster
- extra
Options {[key: string]: string} - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key
Schema FeatureEngineering Kafka Config Key Schema - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- name string
- (string) - Name that uniquely identifies this Kafka config within the metastore. This will be the identifier used from the Feature object to reference these configs for a feature. Can be distinct from topic name
- provider
Config FeatureEngineering Kafka Config Provider Config - Configure the provider for management through account provider.
- subscription
Mode FeatureEngineering Kafka Config Subscription Mode - Options to configure which Kafka topics to pull data from
- value
Schema FeatureEngineering Kafka Config Value Schema - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth_
config FeatureEngineering Kafka Config Auth Config Args - Authentication configuration for connection to topics
- backfill_
source FeatureEngineering Kafka Config Backfill Source Args - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- bootstrap_
servers str - A comma-separated list of host/port pairs pointing to Kafka cluster
- extra_
options Mapping[str, str] - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key_
schema FeatureEngineering Kafka Config Key Schema Args - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- name str
- (string) - Name that uniquely identifies this Kafka config within the metastore. This will be the identifier used from the Feature object to reference these configs for a feature. Can be distinct from topic name
- provider_
config FeatureEngineering Kafka Config Provider Config Args - Configure the provider for management through account provider.
- subscription_
mode FeatureEngineering Kafka Config Subscription Mode Args - Options to configure which Kafka topics to pull data from
- value_
schema FeatureEngineering Kafka Config Value Schema Args - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
- auth
Config Property Map - Authentication configuration for connection to topics
- backfill
Source Property Map - A user-provided and managed source for backfilling data. Historical data is used when creating a training set from streaming features linked to this Kafka config. In the future, a separate table will be maintained by Databricks for forward filling data. The schema for this source must match exactly that of the key and value schemas specified for this Kafka config
- bootstrap
Servers String - A comma-separated list of host/port pairs pointing to Kafka cluster
- extra
Options Map<String> - Catch-all for miscellaneous options. Keys should be source options or Kafka consumer options (kafka.*)
- key
Schema Property Map - Schema configuration for extracting message keys from topics. At least one of keySchema and valueSchema must be provided
- name String
- (string) - Name that uniquely identifies this Kafka config within the metastore. This will be the identifier used from the Feature object to reference these configs for a feature. Can be distinct from topic name
- provider
Config Property Map - Configure the provider for management through account provider.
- subscription
Mode Property Map - Options to configure which Kafka topics to pull data from
- value
Schema Property Map - Schema configuration for extracting message values from topics. At least one of keySchema and valueSchema must be provided
Supporting Types
FeatureEngineeringKafkaConfigAuthConfig, FeatureEngineeringKafkaConfigAuthConfigArgs
- Mtls
Config FeatureEngineering Kafka Config Auth Config Mtls Config - Mutual-TLS authentication. See MtlsConfig
- Uc
Service stringCredential Name - Name of the Unity Catalog service credential. This value will be set under the option databricks.serviceCredential
- Mtls
Config FeatureEngineering Kafka Config Auth Config Mtls Config - Mutual-TLS authentication. See MtlsConfig
- Uc
Service stringCredential Name - Name of the Unity Catalog service credential. This value will be set under the option databricks.serviceCredential
- mtls_
config object - Mutual-TLS authentication. See MtlsConfig
- uc_
service_ stringcredential_ name - Name of the Unity Catalog service credential. This value will be set under the option databricks.serviceCredential
- mtls
Config FeatureEngineering Kafka Config Auth Config Mtls Config - Mutual-TLS authentication. See MtlsConfig
- uc
Service StringCredential Name - Name of the Unity Catalog service credential. This value will be set under the option databricks.serviceCredential
- mtls
Config FeatureEngineering Kafka Config Auth Config Mtls Config - Mutual-TLS authentication. See MtlsConfig
- uc
Service stringCredential Name - Name of the Unity Catalog service credential. This value will be set under the option databricks.serviceCredential
- mtls_
config FeatureEngineering Kafka Config Auth Config Mtls Config - Mutual-TLS authentication. See MtlsConfig
- uc_
service_ strcredential_ name - Name of the Unity Catalog service credential. This value will be set under the option databricks.serviceCredential
- mtls
Config Property Map - Mutual-TLS authentication. See MtlsConfig
- uc
Service StringCredential Name - Name of the Unity Catalog service credential. This value will be set under the option databricks.serviceCredential
FeatureEngineeringKafkaConfigAuthConfigMtlsConfig, FeatureEngineeringKafkaConfigAuthConfigMtlsConfigArgs
- Key
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Key Password Ref - Secret-scope reference for the private key password. Often the same value as the keystore password (keytool's default), but provided as a separate field because Apache Kafka requires it as a distinct option (kafka.ssl.key.password)
- Keystore
Location string - Unity Catalog volume path to the JKS keystore file containing the client certificate and private key. e.g. "/Volumes////client.jks". The materialization compute must have read permission on this volume
- Keystore
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Keystore Password Ref - Secret-scope reference for the JKS keystore password
- Truststore
Location string - Unity Catalog volume path to the JKS truststore file containing the CA certificate(s) trusted to verify the Kafka broker's server certificate. e.g. "/Volumes////truststore.jks"
- Truststore
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Truststore Password Ref - Secret-scope reference for the JKS truststore password
- Disable
Hostname boolVerification Set to true only when the broker certificate's SAN intentionally does not match the connection endpoint — for example when reaching the cluster through a PrivateLink endpoint whose DNS name is not in the broker certificate. Skipping the hostname check removes a defense against man-in-the-middle attacks; do not enable casually. mTLS client authentication is unaffected by this option.
See the Apache Kafka SSL security guide for background on this check: https://kafka.apache.org/42/security/encryption-and-authentication-using-ssl/#host-name-verification
- Key
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Key Password Ref - Secret-scope reference for the private key password. Often the same value as the keystore password (keytool's default), but provided as a separate field because Apache Kafka requires it as a distinct option (kafka.ssl.key.password)
- Keystore
Location string - Unity Catalog volume path to the JKS keystore file containing the client certificate and private key. e.g. "/Volumes////client.jks". The materialization compute must have read permission on this volume
- Keystore
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Keystore Password Ref - Secret-scope reference for the JKS keystore password
- Truststore
Location string - Unity Catalog volume path to the JKS truststore file containing the CA certificate(s) trusted to verify the Kafka broker's server certificate. e.g. "/Volumes////truststore.jks"
- Truststore
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Truststore Password Ref - Secret-scope reference for the JKS truststore password
- Disable
Hostname boolVerification Set to true only when the broker certificate's SAN intentionally does not match the connection endpoint — for example when reaching the cluster through a PrivateLink endpoint whose DNS name is not in the broker certificate. Skipping the hostname check removes a defense against man-in-the-middle attacks; do not enable casually. mTLS client authentication is unaffected by this option.
See the Apache Kafka SSL security guide for background on this check: https://kafka.apache.org/42/security/encryption-and-authentication-using-ssl/#host-name-verification
- key_
password_ objectref - Secret-scope reference for the private key password. Often the same value as the keystore password (keytool's default), but provided as a separate field because Apache Kafka requires it as a distinct option (kafka.ssl.key.password)
- keystore_
location string - Unity Catalog volume path to the JKS keystore file containing the client certificate and private key. e.g. "/Volumes////client.jks". The materialization compute must have read permission on this volume
- keystore_
password_ objectref - Secret-scope reference for the JKS keystore password
- truststore_
location string - Unity Catalog volume path to the JKS truststore file containing the CA certificate(s) trusted to verify the Kafka broker's server certificate. e.g. "/Volumes////truststore.jks"
- truststore_
password_ objectref - Secret-scope reference for the JKS truststore password
- disable_
hostname_ boolverification Set to true only when the broker certificate's SAN intentionally does not match the connection endpoint — for example when reaching the cluster through a PrivateLink endpoint whose DNS name is not in the broker certificate. Skipping the hostname check removes a defense against man-in-the-middle attacks; do not enable casually. mTLS client authentication is unaffected by this option.
See the Apache Kafka SSL security guide for background on this check: https://kafka.apache.org/42/security/encryption-and-authentication-using-ssl/#host-name-verification
- key
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Key Password Ref - Secret-scope reference for the private key password. Often the same value as the keystore password (keytool's default), but provided as a separate field because Apache Kafka requires it as a distinct option (kafka.ssl.key.password)
- keystore
Location String - Unity Catalog volume path to the JKS keystore file containing the client certificate and private key. e.g. "/Volumes////client.jks". The materialization compute must have read permission on this volume
- keystore
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Keystore Password Ref - Secret-scope reference for the JKS keystore password
- truststore
Location String - Unity Catalog volume path to the JKS truststore file containing the CA certificate(s) trusted to verify the Kafka broker's server certificate. e.g. "/Volumes////truststore.jks"
- truststore
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Truststore Password Ref - Secret-scope reference for the JKS truststore password
- disable
Hostname BooleanVerification Set to true only when the broker certificate's SAN intentionally does not match the connection endpoint — for example when reaching the cluster through a PrivateLink endpoint whose DNS name is not in the broker certificate. Skipping the hostname check removes a defense against man-in-the-middle attacks; do not enable casually. mTLS client authentication is unaffected by this option.
See the Apache Kafka SSL security guide for background on this check: https://kafka.apache.org/42/security/encryption-and-authentication-using-ssl/#host-name-verification
- key
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Key Password Ref - Secret-scope reference for the private key password. Often the same value as the keystore password (keytool's default), but provided as a separate field because Apache Kafka requires it as a distinct option (kafka.ssl.key.password)
- keystore
Location string - Unity Catalog volume path to the JKS keystore file containing the client certificate and private key. e.g. "/Volumes////client.jks". The materialization compute must have read permission on this volume
- keystore
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Keystore Password Ref - Secret-scope reference for the JKS keystore password
- truststore
Location string - Unity Catalog volume path to the JKS truststore file containing the CA certificate(s) trusted to verify the Kafka broker's server certificate. e.g. "/Volumes////truststore.jks"
- truststore
Password FeatureRef Engineering Kafka Config Auth Config Mtls Config Truststore Password Ref - Secret-scope reference for the JKS truststore password
- disable
Hostname booleanVerification Set to true only when the broker certificate's SAN intentionally does not match the connection endpoint — for example when reaching the cluster through a PrivateLink endpoint whose DNS name is not in the broker certificate. Skipping the hostname check removes a defense against man-in-the-middle attacks; do not enable casually. mTLS client authentication is unaffected by this option.
See the Apache Kafka SSL security guide for background on this check: https://kafka.apache.org/42/security/encryption-and-authentication-using-ssl/#host-name-verification
- key_
password_ Featureref Engineering Kafka Config Auth Config Mtls Config Key Password Ref - Secret-scope reference for the private key password. Often the same value as the keystore password (keytool's default), but provided as a separate field because Apache Kafka requires it as a distinct option (kafka.ssl.key.password)
- keystore_
location str - Unity Catalog volume path to the JKS keystore file containing the client certificate and private key. e.g. "/Volumes////client.jks". The materialization compute must have read permission on this volume
- keystore_
password_ Featureref Engineering Kafka Config Auth Config Mtls Config Keystore Password Ref - Secret-scope reference for the JKS keystore password
- truststore_
location str - Unity Catalog volume path to the JKS truststore file containing the CA certificate(s) trusted to verify the Kafka broker's server certificate. e.g. "/Volumes////truststore.jks"
- truststore_
password_ Featureref Engineering Kafka Config Auth Config Mtls Config Truststore Password Ref - Secret-scope reference for the JKS truststore password
- disable_
hostname_ boolverification Set to true only when the broker certificate's SAN intentionally does not match the connection endpoint — for example when reaching the cluster through a PrivateLink endpoint whose DNS name is not in the broker certificate. Skipping the hostname check removes a defense against man-in-the-middle attacks; do not enable casually. mTLS client authentication is unaffected by this option.
See the Apache Kafka SSL security guide for background on this check: https://kafka.apache.org/42/security/encryption-and-authentication-using-ssl/#host-name-verification
- key
Password Property MapRef - Secret-scope reference for the private key password. Often the same value as the keystore password (keytool's default), but provided as a separate field because Apache Kafka requires it as a distinct option (kafka.ssl.key.password)
- keystore
Location String - Unity Catalog volume path to the JKS keystore file containing the client certificate and private key. e.g. "/Volumes////client.jks". The materialization compute must have read permission on this volume
- keystore
Password Property MapRef - Secret-scope reference for the JKS keystore password
- truststore
Location String - Unity Catalog volume path to the JKS truststore file containing the CA certificate(s) trusted to verify the Kafka broker's server certificate. e.g. "/Volumes////truststore.jks"
- truststore
Password Property MapRef - Secret-scope reference for the JKS truststore password
- disable
Hostname BooleanVerification Set to true only when the broker certificate's SAN intentionally does not match the connection endpoint — for example when reaching the cluster through a PrivateLink endpoint whose DNS name is not in the broker certificate. Skipping the hostname check removes a defense against man-in-the-middle attacks; do not enable casually. mTLS client authentication is unaffected by this option.
See the Apache Kafka SSL security guide for background on this check: https://kafka.apache.org/42/security/encryption-and-authentication-using-ssl/#host-name-verification
FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeyPasswordRef, FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeyPasswordRefArgs
FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeystorePasswordRef, FeatureEngineeringKafkaConfigAuthConfigMtlsConfigKeystorePasswordRefArgs
FeatureEngineeringKafkaConfigAuthConfigMtlsConfigTruststorePasswordRef, FeatureEngineeringKafkaConfigAuthConfigMtlsConfigTruststorePasswordRefArgs
FeatureEngineeringKafkaConfigBackfillSource, FeatureEngineeringKafkaConfigBackfillSourceArgs
- Delta
Table stringName - The full three-part name (catalog, schema, name) of the Delta table containing the historical data to backfill
- Delta
Table FeatureSource Engineering Kafka Config Backfill Source Delta Table Source - Deprecated: Use deltaTableName instead. Kept for backwards compatibility. The Delta table source containing the historical data to backfill. Only the delta table name is used for backfill, other fields are ignored
- Delta
Table stringName - The full three-part name (catalog, schema, name) of the Delta table containing the historical data to backfill
- Delta
Table FeatureSource Engineering Kafka Config Backfill Source Delta Table Source - Deprecated: Use deltaTableName instead. Kept for backwards compatibility. The Delta table source containing the historical data to backfill. Only the delta table name is used for backfill, other fields are ignored
- delta_
table_ stringname - The full three-part name (catalog, schema, name) of the Delta table containing the historical data to backfill
- delta_
table_ objectsource - Deprecated: Use deltaTableName instead. Kept for backwards compatibility. The Delta table source containing the historical data to backfill. Only the delta table name is used for backfill, other fields are ignored
- delta
Table StringName - The full three-part name (catalog, schema, name) of the Delta table containing the historical data to backfill
- delta
Table FeatureSource Engineering Kafka Config Backfill Source Delta Table Source - Deprecated: Use deltaTableName instead. Kept for backwards compatibility. The Delta table source containing the historical data to backfill. Only the delta table name is used for backfill, other fields are ignored
- delta
Table stringName - The full three-part name (catalog, schema, name) of the Delta table containing the historical data to backfill
- delta
Table FeatureSource Engineering Kafka Config Backfill Source Delta Table Source - Deprecated: Use deltaTableName instead. Kept for backwards compatibility. The Delta table source containing the historical data to backfill. Only the delta table name is used for backfill, other fields are ignored
- delta_
table_ strname - The full three-part name (catalog, schema, name) of the Delta table containing the historical data to backfill
- delta_
table_ Featuresource Engineering Kafka Config Backfill Source Delta Table Source - Deprecated: Use deltaTableName instead. Kept for backwards compatibility. The Delta table source containing the historical data to backfill. Only the delta table name is used for backfill, other fields are ignored
- delta
Table StringName - The full three-part name (catalog, schema, name) of the Delta table containing the historical data to backfill
- delta
Table Property MapSource - Deprecated: Use deltaTableName instead. Kept for backwards compatibility. The Delta table source containing the historical data to backfill. Only the delta table name is used for backfill, other fields are ignored
FeatureEngineeringKafkaConfigBackfillSourceDeltaTableSource, FeatureEngineeringKafkaConfigBackfillSourceDeltaTableSourceArgs
- Full
Name string - The full three-part (catalog, schema, table) name of the Delta table
- Dataframe
Schema string - Schema of the resulting dataframe after transformations, in Spark StructType JSON format (from df.schema.json()). Required if transformationSql is specified. Example: {"type":"struct","fields":[{"name":"colA","type":"integer","nullable":true,"metadata":{}},{"name":"colC","type":"integer","nullable":true,"metadata":{}}]}
- Entity
Columns List<string> - Deprecated: Use Feature.entity instead. Kept for backwards compatibility. The entity columns of the Delta table
- Filter
Condition string - Single WHERE clause to filter delta table before applying transformations. Will be row-wise evaluated, so should only include conditionals and projections
- Timeseries
Column string - Deprecated: Use Feature.timeseries_column instead. Kept for backwards compatibility. The timeseries column of the Delta table
- Transformation
Sql string - A single SQL SELECT expression applied after filter_condition.
Should contains all the columns needed (eg. "SELECT , colA + colB AS colC FROM x.y.z WHERE colA > 0" would have
transformationSql", colA + colB AS colC") If transformationSql is not provided, all columns of the delta table are present in the DataSource dataframe
- Full
Name string - The full three-part (catalog, schema, table) name of the Delta table
- Dataframe
Schema string - Schema of the resulting dataframe after transformations, in Spark StructType JSON format (from df.schema.json()). Required if transformationSql is specified. Example: {"type":"struct","fields":[{"name":"colA","type":"integer","nullable":true,"metadata":{}},{"name":"colC","type":"integer","nullable":true,"metadata":{}}]}
- Entity
Columns []string - Deprecated: Use Feature.entity instead. Kept for backwards compatibility. The entity columns of the Delta table
- Filter
Condition string - Single WHERE clause to filter delta table before applying transformations. Will be row-wise evaluated, so should only include conditionals and projections
- Timeseries
Column string - Deprecated: Use Feature.timeseries_column instead. Kept for backwards compatibility. The timeseries column of the Delta table
- Transformation
Sql string - A single SQL SELECT expression applied after filter_condition.
Should contains all the columns needed (eg. "SELECT , colA + colB AS colC FROM x.y.z WHERE colA > 0" would have
transformationSql", colA + colB AS colC") If transformationSql is not provided, all columns of the delta table are present in the DataSource dataframe
- full_
name string - The full three-part (catalog, schema, table) name of the Delta table
- dataframe_
schema string - Schema of the resulting dataframe after transformations, in Spark StructType JSON format (from df.schema.json()). Required if transformationSql is specified. Example: {"type":"struct","fields":[{"name":"colA","type":"integer","nullable":true,"metadata":{}},{"name":"colC","type":"integer","nullable":true,"metadata":{}}]}
- entity_
columns list(string) - Deprecated: Use Feature.entity instead. Kept for backwards compatibility. The entity columns of the Delta table
- filter_
condition string - Single WHERE clause to filter delta table before applying transformations. Will be row-wise evaluated, so should only include conditionals and projections
- timeseries_
column string - Deprecated: Use Feature.timeseries_column instead. Kept for backwards compatibility. The timeseries column of the Delta table
- transformation_
sql string - A single SQL SELECT expression applied after filter_condition.
Should contains all the columns needed (eg. "SELECT , colA + colB AS colC FROM x.y.z WHERE colA > 0" would have
transformationSql", colA + colB AS colC") If transformationSql is not provided, all columns of the delta table are present in the DataSource dataframe
- full
Name String - The full three-part (catalog, schema, table) name of the Delta table
- dataframe
Schema String - Schema of the resulting dataframe after transformations, in Spark StructType JSON format (from df.schema.json()). Required if transformationSql is specified. Example: {"type":"struct","fields":[{"name":"colA","type":"integer","nullable":true,"metadata":{}},{"name":"colC","type":"integer","nullable":true,"metadata":{}}]}
- entity
Columns List<String> - Deprecated: Use Feature.entity instead. Kept for backwards compatibility. The entity columns of the Delta table
- filter
Condition String - Single WHERE clause to filter delta table before applying transformations. Will be row-wise evaluated, so should only include conditionals and projections
- timeseries
Column String - Deprecated: Use Feature.timeseries_column instead. Kept for backwards compatibility. The timeseries column of the Delta table
- transformation
Sql String - A single SQL SELECT expression applied after filter_condition.
Should contains all the columns needed (eg. "SELECT , colA + colB AS colC FROM x.y.z WHERE colA > 0" would have
transformationSql", colA + colB AS colC") If transformationSql is not provided, all columns of the delta table are present in the DataSource dataframe
- full
Name string - The full three-part (catalog, schema, table) name of the Delta table
- dataframe
Schema string - Schema of the resulting dataframe after transformations, in Spark StructType JSON format (from df.schema.json()). Required if transformationSql is specified. Example: {"type":"struct","fields":[{"name":"colA","type":"integer","nullable":true,"metadata":{}},{"name":"colC","type":"integer","nullable":true,"metadata":{}}]}
- entity
Columns string[] - Deprecated: Use Feature.entity instead. Kept for backwards compatibility. The entity columns of the Delta table
- filter
Condition string - Single WHERE clause to filter delta table before applying transformations. Will be row-wise evaluated, so should only include conditionals and projections
- timeseries
Column string - Deprecated: Use Feature.timeseries_column instead. Kept for backwards compatibility. The timeseries column of the Delta table
- transformation
Sql string - A single SQL SELECT expression applied after filter_condition.
Should contains all the columns needed (eg. "SELECT , colA + colB AS colC FROM x.y.z WHERE colA > 0" would have
transformationSql", colA + colB AS colC") If transformationSql is not provided, all columns of the delta table are present in the DataSource dataframe
- full_
name str - The full three-part (catalog, schema, table) name of the Delta table
- dataframe_
schema str - Schema of the resulting dataframe after transformations, in Spark StructType JSON format (from df.schema.json()). Required if transformationSql is specified. Example: {"type":"struct","fields":[{"name":"colA","type":"integer","nullable":true,"metadata":{}},{"name":"colC","type":"integer","nullable":true,"metadata":{}}]}
- entity_
columns Sequence[str] - Deprecated: Use Feature.entity instead. Kept for backwards compatibility. The entity columns of the Delta table
- filter_
condition str - Single WHERE clause to filter delta table before applying transformations. Will be row-wise evaluated, so should only include conditionals and projections
- timeseries_
column str - Deprecated: Use Feature.timeseries_column instead. Kept for backwards compatibility. The timeseries column of the Delta table
- transformation_
sql str - A single SQL SELECT expression applied after filter_condition.
Should contains all the columns needed (eg. "SELECT , colA + colB AS colC FROM x.y.z WHERE colA > 0" would have
transformationSql", colA + colB AS colC") If transformationSql is not provided, all columns of the delta table are present in the DataSource dataframe
- full
Name String - The full three-part (catalog, schema, table) name of the Delta table
- dataframe
Schema String - Schema of the resulting dataframe after transformations, in Spark StructType JSON format (from df.schema.json()). Required if transformationSql is specified. Example: {"type":"struct","fields":[{"name":"colA","type":"integer","nullable":true,"metadata":{}},{"name":"colC","type":"integer","nullable":true,"metadata":{}}]}
- entity
Columns List<String> - Deprecated: Use Feature.entity instead. Kept for backwards compatibility. The entity columns of the Delta table
- filter
Condition String - Single WHERE clause to filter delta table before applying transformations. Will be row-wise evaluated, so should only include conditionals and projections
- timeseries
Column String - Deprecated: Use Feature.timeseries_column instead. Kept for backwards compatibility. The timeseries column of the Delta table
- transformation
Sql String - A single SQL SELECT expression applied after filter_condition.
Should contains all the columns needed (eg. "SELECT , colA + colB AS colC FROM x.y.z WHERE colA > 0" would have
transformationSql", colA + colB AS colC") If transformationSql is not provided, all columns of the delta table are present in the DataSource dataframe
FeatureEngineeringKafkaConfigKeySchema, FeatureEngineeringKafkaConfigKeySchemaArgs
- Json
Schema string - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- Json
Schema string - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json_
schema string - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json
Schema String - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json
Schema string - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json_
schema str - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json
Schema String - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
FeatureEngineeringKafkaConfigProviderConfig, FeatureEngineeringKafkaConfigProviderConfigArgs
- Workspace
Id string - Workspace ID which the resource belongs to. This workspace must be part of the account which the provider is configured with.
- Workspace
Id string - Workspace ID which the resource belongs to. This workspace must be part of the account which the provider is configured with.
- workspace_
id string - Workspace ID which the resource belongs to. This workspace must be part of the account which the provider is configured with.
- workspace
Id String - Workspace ID which the resource belongs to. This workspace must be part of the account which the provider is configured with.
- workspace
Id string - Workspace ID which the resource belongs to. This workspace must be part of the account which the provider is configured with.
- workspace_
id str - Workspace ID which the resource belongs to. This workspace must be part of the account which the provider is configured with.
- workspace
Id String - Workspace ID which the resource belongs to. This workspace must be part of the account which the provider is configured with.
FeatureEngineeringKafkaConfigSubscriptionMode, FeatureEngineeringKafkaConfigSubscriptionModeArgs
- Assign string
- A JSON string that contains the specific topic-partitions to consume from. For example, for '{"topicA":[0,1],"topicB":[2,4]}', topicA's 0'th and 1st partitions will be consumed from
- Subscribe string
- A comma-separated list of Kafka topics to read from. For example, 'topicA,topicB,topicC'
- Subscribe
Pattern string - A regular expression matching topics to subscribe to. For example, 'topic.*' will subscribe to all topics starting with 'topic'
- Assign string
- A JSON string that contains the specific topic-partitions to consume from. For example, for '{"topicA":[0,1],"topicB":[2,4]}', topicA's 0'th and 1st partitions will be consumed from
- Subscribe string
- A comma-separated list of Kafka topics to read from. For example, 'topicA,topicB,topicC'
- Subscribe
Pattern string - A regular expression matching topics to subscribe to. For example, 'topic.*' will subscribe to all topics starting with 'topic'
- assign string
- A JSON string that contains the specific topic-partitions to consume from. For example, for '{"topicA":[0,1],"topicB":[2,4]}', topicA's 0'th and 1st partitions will be consumed from
- subscribe string
- A comma-separated list of Kafka topics to read from. For example, 'topicA,topicB,topicC'
- subscribe_
pattern string - A regular expression matching topics to subscribe to. For example, 'topic.*' will subscribe to all topics starting with 'topic'
- assign String
- A JSON string that contains the specific topic-partitions to consume from. For example, for '{"topicA":[0,1],"topicB":[2,4]}', topicA's 0'th and 1st partitions will be consumed from
- subscribe String
- A comma-separated list of Kafka topics to read from. For example, 'topicA,topicB,topicC'
- subscribe
Pattern String - A regular expression matching topics to subscribe to. For example, 'topic.*' will subscribe to all topics starting with 'topic'
- assign string
- A JSON string that contains the specific topic-partitions to consume from. For example, for '{"topicA":[0,1],"topicB":[2,4]}', topicA's 0'th and 1st partitions will be consumed from
- subscribe string
- A comma-separated list of Kafka topics to read from. For example, 'topicA,topicB,topicC'
- subscribe
Pattern string - A regular expression matching topics to subscribe to. For example, 'topic.*' will subscribe to all topics starting with 'topic'
- assign str
- A JSON string that contains the specific topic-partitions to consume from. For example, for '{"topicA":[0,1],"topicB":[2,4]}', topicA's 0'th and 1st partitions will be consumed from
- subscribe str
- A comma-separated list of Kafka topics to read from. For example, 'topicA,topicB,topicC'
- subscribe_
pattern str - A regular expression matching topics to subscribe to. For example, 'topic.*' will subscribe to all topics starting with 'topic'
- assign String
- A JSON string that contains the specific topic-partitions to consume from. For example, for '{"topicA":[0,1],"topicB":[2,4]}', topicA's 0'th and 1st partitions will be consumed from
- subscribe String
- A comma-separated list of Kafka topics to read from. For example, 'topicA,topicB,topicC'
- subscribe
Pattern String - A regular expression matching topics to subscribe to. For example, 'topic.*' will subscribe to all topics starting with 'topic'
FeatureEngineeringKafkaConfigValueSchema, FeatureEngineeringKafkaConfigValueSchemaArgs
- Json
Schema string - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- Json
Schema string - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json_
schema string - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json
Schema String - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json
Schema string - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json_
schema str - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
- json
Schema String - Schema of the JSON object in standard IETF JSON schema format (https://json-schema.org/)
Package Details
- Repository
- databricks pulumi/pulumi-databricks
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
databricksTerraform Provider.
published on Friday, May 29, 2026 by Pulumi