Uh oh!
There was an error while loading. Please reload this page.
Fixed spark version check for clusters defined in the same bundle - #2374
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| // So we can get the version from the cluster definition. | ||
| // It's defined in a form of resources.clusters.<cluster_key>.spark_version while the value here is | ||
| // ${resources.clusters.<cluster_key>.id} | ||
| if strings.HasPrefix(task.ExistingClusterId, "${") { |
There was a problem hiding this comment.
You don't need to have this check, you can directly use the ok value from dynvar.PureReferenceToPath
There was a problem hiding this comment.
Yeah, I know, just want to make the intention here a bit more clear when reading it
Notable changes: Starting this version CLI does not load bundle auth information when CLI command is executed inside the bundle directory with explicitly provided via `-p` flag profile. CLI: * Do not load host from bundle for CLI commands when profile flag is used ([#2335](#2335)). * Fixed accessing required path parameters in CLI generation when --json flag ([#2373](#2373)). Bundles: * Provide instructions for testing in the default-python template ([#2355](#2355)). * Remove `run_as` from the built-in templates ([#2044](#2044)). * Change warning about incomplete permissions section into a recommendation ([#2043](#2043)). * Refine `mode: production` diagnostic output ([#2236](#2236)). * Support serverless mode in default-python template (explicit prompt) ([#2377](#2377)). * Set default data_security_mode to "SINGLE_USER" in bundle templates ([#2372](#2372)). * Fixed spark version check for clusters defined in the same bundle ([#2374](#2374)). API Changes: * Added `databricks genie get-message-query-result-by-attachment` command. OpenAPI commit 99f644e72261ef5ecf8d74db20f4b7a1e09723cc (2025-02-11)
Notable changes: Starting this version CLI does not load bundle auth information when CLI command is executed inside the bundle directory with explicitly provided via `-p` flag profile. For more details see the related GitHub issue #1358 CLI: * Do not load host from bundle for CLI commands when profile flag is used ([#2335](#2335)). * Fixed accessing required path parameters in CLI generation when --json flag ([#2373](#2373)). Bundles: * Provide instructions for testing in the default-python template ([#2355](#2355)). * Remove `run_as` from the built-in templates ([#2044](#2044)). * Change warning about incomplete permissions section into a recommendation ([#2043](#2043)). * Refine `mode: production` diagnostic output ([#2236](#2236)). * Support serverless mode in default-python template (explicit prompt) ([#2377](#2377)). * Set default data_security_mode to "SINGLE_USER" in bundle templates ([#2372](#2372)). * Fixed spark version check for clusters defined in the same bundle ([#2374](#2374)). API Changes: * Added `databricks genie get-message-query-result-by-attachment` command. OpenAPI commit 99f644e72261ef5ecf8d74db20f4b7a1e09723cc (2025-02-11)
…tabricks#2374) ## Changes Previously using python wheel tasks in the tasks with compute referering to interactive cluster defied in the same bundle would produce a warning like below ``` GET /api/2.1/clusters/get?cluster_id=${resources.clusters.development_cluster.id} < HTTP/2.0 400 Bad Request < { < "error_code": "INVALID_PARAMETER_VALUE", < "message": "Cluster ${resources.clusters.development_cluster.id} does not exist" < } pid=14465 mutator=seq mutator=initialize mutator=seq mutator=PythonWrapperWarning sdk=true ``` This PR fixes it by making sure that we check spark version for such clusters based on its bundle configuration and don't make API calls ## Tests Added acceptance test
Notable changes: Starting this version CLI does not load bundle auth information when CLI command is executed inside the bundle directory with explicitly provided via `-p` flag profile. For more details see the related GitHub issue databricks#1358 CLI: * Do not load host from bundle for CLI commands when profile flag is used ([databricks#2335](databricks#2335)). * Fixed accessing required path parameters in CLI generation when --json flag ([databricks#2373](databricks#2373)). Bundles: * Provide instructions for testing in the default-python template ([databricks#2355](databricks#2355)). * Remove `run_as` from the built-in templates ([databricks#2044](databricks#2044)). * Change warning about incomplete permissions section into a recommendation ([databricks#2043](databricks#2043)). * Refine `mode: production` diagnostic output ([databricks#2236](databricks#2236)). * Support serverless mode in default-python template (explicit prompt) ([databricks#2377](databricks#2377)). * Set default data_security_mode to "SINGLE_USER" in bundle templates ([databricks#2372](databricks#2372)). * Fixed spark version check for clusters defined in the same bundle ([databricks#2374](databricks#2374)). API Changes: * Added `databricks genie get-message-query-result-by-attachment` command. OpenAPI commit 99f644e72261ef5ecf8d74db20f4b7a1e09723cc (2025-02-11)
) ## Changes Previously using python wheel tasks in the tasks with compute referering to interactive cluster defied in the same bundle would produce a warning like below ``` GET /api/2.1/clusters/get?cluster_id=${resources.clusters.development_cluster.id} < HTTP/2.0 400 Bad Request < { < "error_code": "INVALID_PARAMETER_VALUE", < "message": "Cluster ${resources.clusters.development_cluster.id} does not exist" < } pid=14465 mutator=seq mutator=initialize mutator=seq mutator=PythonWrapperWarning sdk=true ``` This PR fixes it by making sure that we check spark version for such clusters based on its bundle configuration and don't make API calls ## Tests Added acceptance test
Notable changes: Starting this version CLI does not load bundle auth information when CLI command is executed inside the bundle directory with explicitly provided via `-p` flag profile. For more details see the related GitHub issue #1358 CLI: * Do not load host from bundle for CLI commands when profile flag is used ([#2335](#2335)). * Fixed accessing required path parameters in CLI generation when --json flag ([#2373](#2373)). Bundles: * Provide instructions for testing in the default-python template ([#2355](#2355)). * Remove `run_as` from the built-in templates ([#2044](#2044)). * Change warning about incomplete permissions section into a recommendation ([#2043](#2043)). * Refine `mode: production` diagnostic output ([#2236](#2236)). * Support serverless mode in default-python template (explicit prompt) ([#2377](#2377)). * Set default data_security_mode to "SINGLE_USER" in bundle templates ([#2372](#2372)). * Fixed spark version check for clusters defined in the same bundle ([#2374](#2374)). API Changes: * Added `databricks genie get-message-query-result-by-attachment` command. OpenAPI commit 99f644e72261ef5ecf8d74db20f4b7a1e09723cc (2025-02-11)
Changes
Previously using python wheel tasks in the tasks with compute referering to interactive cluster defied in the same bundle would produce a warning like below
This PR fixes it by making sure that we check spark version for such clusters based on its bundle configuration and don't make API calls
Tests
Added acceptance test