Azure / Azure/MachineLearningNotebooks
DataBricksStep has deprecated init_scripts incorrectly
- 主要語言
- Jupyter Notebook
- 星號
- 4.4k
- 分支
- 2.6k
- PR 合併指標
- 30 天內沒有已合併 PR
描述
The argument init_script is no longer working for DataBricksStep(). The docs cite the following reason.
init_scripts | [str]Deprecated. Databricks announced the init script stored in DBFS will stop work after Dec 1, 2023. To mitigate the issue, please 1) use global init scripts in databricks following https://learn.microsoft.com/azure/databricks/init-scripts/global 2) comment out the line of init_scripts in your AzureML databricks step.
However, init_scripts have not been deprecated by DataBricks. DataBricks has deprecated storing init_scripts in dbfs:/ location, and instead suggets to store them in Workspace folders. This is what DataBricks recommends for all clusters and is, in fact, the only possible way for Unity Catalog enabled DataBricks clusters as global init scripts does not work for them.
Please enable init_scripts parameter for the DataBricksStep() as the current way of using global init_scripts does not work for Unity Catalog enabled clusters.
貢獻指南
這個儲存庫沒有索引到貢獻指南
研究方向
Start by locating DataBricksStep and its init_scripts parameter handling, then compare the current documentation with the linked Databricks init-script guidance. The work is complete when Workspace-folder init scripts remain usable for Unity Catalog-enabled clusters and the deprecation guidance accurately describes DBFS storage rather than disabling init_scripts.
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- azure, python
- 領域
- cloud, machine-learning
- Issue 類型
- 功能
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 38/100