You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Notebook Migration] Support migrating R files/scripts #9385
Not every R analysis is a notebook; a lot of it is plain .R scripts. This issue tracks letting users convert a single R file into a Texera workflow of R UDFs, as the file part of #8009. It should behave the same way the Python file support from #8007 does, so a user gets a workflow, a notebook to look at, and click to highlight between them. Like R notebooks, it should be gated on the same R flag. When the flag is off, the option should be visible but disabled.
Proposed Solution or Design
The import modal gets an R File tab beside the Python File tab, with its own diagram and description, accepting .R and .r. The file is converted with the R script prompts from #8911, which show the source with line numbers and ask the model for the line ranges each UDF came from. The tool then derives the notebook cells from those ranges, exactly as the Python file path does. The dashboard routes an R file to the R script conversion, and a Python file uploaded on the R tab is rejected. The tab is disabled with the "R is not enabled on this deployment." tooltip when rNotebookMigrationEnabled is off. The work is in #8963.
Activity
zyratlo commentedon Nov 9, 2026
/parent-issue #8009
zyratlo commentedon Nov 9, 2026
/take
feat(notebook-migration): add r files to the import modal (apache#8963)