Azure / Azure/MachineLearningNotebooks
DataBricksStep has deprecated init_scripts incorrectly
- Linguagem predominante
- Jupyter Notebook
- Estrelas
- 4.4k
- Forks
- 2.6k
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
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.
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- azure, python
- Domínio
- cloud, machine-learning
- Tipo de issue
- Funcionalidade
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 38/100