cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Has the numUpdateRetryAttempts property been deprecated?

guangyi
Contributor III

I noticed there is a numUpdateRetryAttempts property mentioned in the the document https://learn.microsoft.com/en-us/azure/databricks/delta-live-tables/properties  used for configing the retry times of any DLT pipeline, but I cannot find it in the DLT pipeline creation API document https://docs.databricks.com/api/workspace/pipelines/create

Also if I added it into the asset yaml bundle file like 

 

   silver_pipeline:
      name:       
      clusters:
      photon: 
      pipelines.numUpdateRetryAttempts: 3

 

The validator gave me a warning about it is a unknown field 

So has the numUpdateRetryAttempts property been deprecated?

1 ACCEPTED SOLUTION

Accepted Solutions

VZLA
Databricks Employee
Databricks Employee

According to the Delta Live Tables properties reference, pipelines.numUpdateRetryAttempts is a recognized configuration parameter. It specifies the maximum number of attempts to retry an update before failing the update when a retryable failure occurs. This parameter is set as a key-value pair in the pipeline configuration and is applicable to triggered updates run in production mode. The default value for this property is five.

{
  "configuration": {
    "pipelines.numUpdateRetryAttempts": 5
  }
}

Or:

silver_pipeline:
  name: <your_pipeline_name>
  clusters:
    - <cluster_configuration>
  photon: <true_or_false>
  configuration:
    pipelines.numUpdateRetryAttempts: 3

Hope it helps!

View solution in original post

1 REPLY 1

VZLA
Databricks Employee
Databricks Employee

According to the Delta Live Tables properties reference, pipelines.numUpdateRetryAttempts is a recognized configuration parameter. It specifies the maximum number of attempts to retry an update before failing the update when a retryable failure occurs. This parameter is set as a key-value pair in the pipeline configuration and is applicable to triggered updates run in production mode. The default value for this property is five.

{
  "configuration": {
    "pipelines.numUpdateRetryAttempts": 5
  }
}

Or:

silver_pipeline:
  name: <your_pipeline_name>
  clusters:
    - <cluster_configuration>
  photon: <true_or_false>
  configuration:
    pipelines.numUpdateRetryAttempts: 3

Hope it helps!

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you won’t want to miss the chance to attend and share knowledge.

If there isn’t a group near you, start one and help create a community that brings people together.

Request a New Group