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: 

Cant find reason but suddenly new Jobs are getting huge job id numbers. example 945270539673815

JBear
New Contributor III

Created Job ID is suddenly started to make huge numbers, and that is now making problems in Terraform plan, cause int is too big

Error: strconv.ParseInt: parsing "945270539673815": value out of range

Im new on the board and pretty new with Databricks so bare with me, if more information is needed please ask ill try to answer with my best know how.

Databricks is running on Azure.

1 ACCEPTED SOLUTION

Accepted Solutions

JBear
New Contributor III

Got it working again i thing problem was old version of providers and terraform Now running on following version and everything is ok now

Terraform v1.1.6

on windows_amd64

+ provider registry.terraform.io/databrickslabs/databricks v0.5.0

+ provider registry.terraform.io/hashicorp/azuread v1.6.0

+ provider registry.terraform.io/hashicorp/azurerm v2.98.0

+ provider registry.terraform.io/hashicorp/random v3.1.0

View solution in original post

4 REPLIES 4

JBear
New Contributor III

Im using Terraform 1.0.10 i will try next to update providers and terraform and see if it helps

JBear
New Contributor III

Got it working again i thing problem was old version of providers and terraform Now running on following version and everything is ok now

Terraform v1.1.6

on windows_amd64

+ provider registry.terraform.io/databrickslabs/databricks v0.5.0

+ provider registry.terraform.io/hashicorp/azuread v1.6.0

+ provider registry.terraform.io/hashicorp/azurerm v2.98.0

+ provider registry.terraform.io/hashicorp/random v3.1.0

BilalAslamDbrx
Databricks Employee
Databricks Employee

For posterity -- you are seeing large Job IDs because of an update to our internal database. We did this because our jobs service is scaling out massively, and the old ID scheme wasn't going to work for much longer.

Anonymous
Not applicable

Hi @Jere Karhu​ , In case you are using the Job/Run id in API, please be advised that you will need to change the client-side logic to process int64/long and expect a random number. In some cases, you just need to change the declared type in their source code to long and do not count on ids being sequential or sorted.

Previously the job/run id was sequential and could be sorted.

Current sample job URL - https://sample.cloud.databricks.com/?o=3329755207123451#job/281680268617720/run/6615691

(here the job/run id has improved to be a bigger/longer number)

Previous sample job URL - https://sample.cloud.databricks.com/?o=3329755207123451#job/5/run/6615597

It is mitigated in version 0.5.3. The below link points to the main Terraform Registry page suggests you use the latest version of the terraform provider.

https://registry.terraform.io/providers/databrickslabs/databricks/latest/docs

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