feat(backend): add the Python Notebook Migration Tool (backend only)#4437
Open
zyratlo wants to merge 5 commits intoapache:mainfrom
Open
feat(backend): add the Python Notebook Migration Tool (backend only)#4437zyratlo wants to merge 5 commits intoapache:mainfrom
zyratlo wants to merge 5 commits intoapache:mainfrom
Conversation
github-actions
Bot
added
dependencies
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this PR?
This PR introduces the backend portion of the Python Notebook Migration Tool, a new tool that converts a user-uploaded Python Jupyter notebook into a Texera workflow. New backend code includes:
notebook-migration-serviceJupyter docker-composewhich hosts the Jupyter server that renders the Jupyter notebook and has custom logic for the mapping featureDetails about the frontend are in a separate PR #4436 .
Any related issues, documentation, discussions?
Closes #4427
This PR closes the sub-issue related to the backend, the parent issue is #4301.
New tables in DB
Architecture Diagram (these can also be found on the parent issue)
How was this PR tested?
This project was built locally and manually tested to ensure functionality. Pre-existing tests, builds, and checks were ran and passed.
Was this PR authored or co-authored using generative AI tooling?
Generated-by: ChatGPT (GPT-5.3)