Describe the issue
When deploying an ingestion pipeline via DAB the field serverless is being ignored. Hence it's not possible to set serverless: false to run on classic compute.
It does work when creating one manually from the Web app.
Configuration
resources:
pipelines:
test_ingestion:
name: Test ingestion
serverless: false
ingestion_definition:
connection_name: connection_oracle
source_type: ORACLE
schema: oracle_ingestion
channel: PREVIEW
catalog: bronze
Steps to reproduce the behavior
- Run
databricks bundle deploy ...
- Check deployment > serverless is missing from definition
Expected Behavior
Compute should not be serverless (example from manual creation)
Actual Behavior
Compute is set to serverless
OS and CLI version
Tested with following versions:
Is this a regression?
I don't know, it's our first time using ingestion pipeline.
Debug Logs
databricks validate --output json
The field is also ignored
test_ingestion": {
"catalog": "catalog",
"channel": "PREVIEW",
"deployment": {
{
"table": {
"destination_catalog": "catalog",
"destination_schema": "schema",
"source_catalog": "xxxx",
"source_schema": "xxxx",
"source_table": "xxxx",
"table_configuration": {
"query_based_connector_config": {
"cursor_columns": [
"EXTRACTION_LEARN_DATE"
]
}
}
}
}
],
"source_type": "ORACLE"
}
Describe the issue
When deploying an ingestion pipeline via DAB the field
serverlessis being ignored. Hence it's not possible to setserverless: falseto run on classic compute.It does work when creating one manually from the Web app.
Configuration
Steps to reproduce the behavior
databricks bundle deploy ...Expected Behavior
Compute should not be serverless (example from manual creation)
Actual Behavior
Compute is set to serverless
OS and CLI version
Tested with following versions:
Is this a regression?
I don't know, it's our first time using ingestion pipeline.
Debug Logs
databricks validate --output jsonThe field is also ignored