Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

RESOURCE_ALREADY_EXISTS error when deploying bundle with version 1.21.0

已關閉
#7,216 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@Sankalp-Mittal 已經在處理了。

開始於 2026年10月28日。

  • #7218 來自 @Sankalp-Mittal —— 未關閉

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
go
領域
cli

研究方向

Start at the bundle deployment file upload path for databricks bundle deploy and inspect how it handles the workspace-files import request when overwrite=true. Reproduce with CLI 1.21.0 against an existing file and compare the request behavior with the working 1.16.1 version. Done means deployment updates the existing file without RESOURCE_ALREADY_EXISTS; linked pull request #7218 shows work is already underway.

由索引模型根據 Issue 內容生成。

描述

CLI
Describe the issue

When doing usual bundle deployment using cli, with version 1.21.0 an error is shown:
Uploading bundle files to /Users/userid/bundles/sem...
Error: Request failed for POST /Users/userid/bundles/sem/src/uk/LIVE/usecase/batching/every1h/file.sql: RESOURCE_ALREADY_EXISTS: Node named 'file.sql' already exists (400 )

Endpoint: POST https://adb-XXXXXXX.azuredatabricks.net/api/2.0/workspace-files/import-file/Users%2Fuserid%2Fbundles%2Fsem%2Fsrc%2Fuk%2FLIVE%2Fusecase%2Fbatching%2Fevery1h%2Ffile.sql?overwrite=true
HTTP Status: 400 Bad Request
API error_code:
API message: Request failed for POST /Users/userid/bundles/sem/src/uk/LIVE/usecase/batching/every1h/file.sql: RESOURCE_ALREADY_EXISTS: Node named 'file.sql' already exists

Steps to reproduce the behavior
  1. Run databricks bundle deploy -p myprofile -t mytarget
  2. See error: RESOURCE_ALREADY_EXISTS: Node named 'file.sql' already exists
Expected Behavior

Deployment successful, with resources updated:
When doing the same deploy, but using 1.16.1 version:
Uploading bundle files to /Users/userid/bundles/sem...
Updated jobs.prelive_sem.permissions
Updated jobs.sem_live_every1d.permissions
Updated jobs.sem_live_every1h.permissions
Updated jobs.sem_live_every2h.permissions
Updated jobs.sem_live_every30d.permissions
Updated jobs.sem_live_every3h.permissions
Updated jobs.sem_live_every7d.permissions
Files: 9 uploaded, 0 deleted
Resources: 0 created, 7 changed, 0 deleted, 7 unchanged

Actual Behavior

Databricks cli 1.21 seems has issue with overwrite=true flag set and doesn't update existing resources.

OS and CLI version

1.21.0 (docker container)
Linux and Windows

Is this a regression?

It works with previous container version (1.10.0)

Debug Logs

Output logs if you run the command with debug logs enabled. Example: databricks clusters list --log-level=debug. Redact if needed

主要語言
Go
星號
416
分支
256
平均合併
1 天 22 小時
30 天內合併 PR
206

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

databricks/cli 的其他 Issue

查看 databricks/cli 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。