Skip to content

[Notebook Migration] Support migrating R code #8009

Closed
3 of 3 issues completed
Closed

Description

@zyratlo

Feature Summary

The migration tool assumes Python throughout. The prompts in migration-prompts.ts describe the task as translating Python and teach the model Texera's Python tuple, table, and operator interfaces, and migration-llm.ts builds every generated operator from the PythonUDFV2 schema. We want to support R next after Jupyter notebook and Python.

Proposed Solution or Design

Extend the migration tool to accept R input and generate R UDF operators instead of Python ones.

The structural work is parameterizing by language what is currently hardcoded to Python:

  • The prompt set needs an R equivalent, teaching the model Texera's R UDF interface the way the current prompts teach the Python one.
  • Operator construction needs to select the R UDF descriptor rather than always using PythonUDFV2.
  • The tool needs to know which language it is looking at, whether from the file extension, the notebook kernel metadata, or an explicit choice in the import modal.

Everything else the tool does is language-agnostic and should carry over unchanged: the upload path, the cell-to-operator mapping and highlighting, the workflow assembly, and the delete path.

Related considerations to work out when this is picked up:

  • Whether a workflow can mix R and Python operators, and whether the tool should ever produce one.
  • How this composes with the plain-file and folder inputs added for Python, since those raise the same "what is a unit" question independently of language.

This is follow-up work after the Jupyter notebook migration tool is complete, and it builds on the Python input work. It is not scoped or designed yet.

Affected Area

Other

Activity

  1. added theissue type on Aug 26, 2026
  2. zyratlo commented on Aug 26, 2026

    @zyratlo
    ContributorAuthor

    /parent-issue #4301

  3. roshiiiz commented on Aug 30, 2026

    @roshiiiz
    Contributor

    /take

  4. zyratlo commented on Aug 30, 2026

    @zyratlo
    ContributorAuthor

    Hi @roshiiiz , thanks for being willing to contribute to Texera! For context, this sub-issue is part of a larger project I have been working on as a new tool to the codebase (see the parent issue #4301). This issue has a stacking dependency on top of #8007 and #8008, so it cannot be done until those are complete. I created this issue to plan out the scope of the project, and it is my fault that I forgot to take it as I already plan to develop this issue in the future. Sorry for the confusion!

  5. assigned and unassigned on Sep 1, 2026
  6. roshiiiz commented on Sep 2, 2026

    @roshiiiz
    Contributor

    Hi @roshiiiz , thanks for being willing to contribute to Texera! For context, this sub-issue is part of a larger project I have been working on as a new tool to the codebase (see the parent issue #4301). This issue has a stacking dependency on top of #8007 and #8008, so it cannot be done until those are complete. I created this issue to plan out the scope of the project, and it is my fault that I forgot to take it as I already plan to develop this issue in the future. Sorry for the confusion!

    Hi @zyratlo, no problem at all. Thanks for the context and the heads up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions