Clarify Cloud UDF dependency handling and version updates#6410
Merged
Conversation
Add two notes to the Cloud UDF guide based on user feedback in Slack: - requirements.txt is the recommended way to install Python dependencies; bundling directly in the ZIP requires cached packages for both CPU architectures - the Edit panel only manages service assignment; changing a UDF's code requires creating a new version Refs DOC-833 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
Reduce admonition pile-up on the page: the dependency-handling and "Edit vs. create new version" guidance read better as body text and were crowding the genuine caveats. Convert both from :::note callouts to prose, leaving only the warranted admonitions. Refs DOC-833 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Blargian
approved these changes
Jun 22, 2026
|
Docs PR opened: ClickHouse/mintlify-docs-dev#239 Clarified that ClickHouse Cloud auto-installs Python UDF dependencies from requirements.txt and that the Edit panel doesn't replace deployed code. |
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.
Closes DOC-833.
Adds two clarifications to the Cloud UDF guide based on user feedback in Slack (testing in staging):
requirements.txtis the recommended way to install Python dependencies, which ClickHouse Cloud prepares for you. Bundling dependencies directly in the ZIP is possible but requires cached packages for both CPU architectures.The reference ↔ Cloud cross-link and the stale preview-badge fix are handled separately in ClickHouse/ClickHouse#107748, since the reference page is synced from that repo.
The
deterministicbehavior and network-access flag are intentionally not documented yet — both have open questions with eng (tracked in DOC-833).🤖 Generated with Claude Code
Note
Low Risk
Documentation-only changes to the Cloud UDF guide with no product or runtime behavior changes.
Overview
Updates the ClickHouse Cloud user-defined functions guide with two clarifications from staging feedback.
The Python dependencies section now states that
requirements.txtis the recommended path because Cloud installs packages for you, and that bundling wheels in the ZIP requires cached packages for both CPU architectures, makingrequirements.txtsimpler.The Create a new version section adds a note that Edit only changes service assignment—re-uploading code there does not update deployed UDF code; code changes require Create new version.
Reviewed by Cursor Bugbot for commit 2b89904. Bugbot is set up for automated code reviews on this repo. Configure here.