update(snowflake): Separate Streaming connector and sink #3118
Conversation
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
There was a problem hiding this comment.
Pull Request Overview
This PR separates the Snowflake integration documentation by splitting the single connector approach into two distinct connector types: one for aggregated mode and another for streaming mode. This change improves clarity by providing dedicated setup instructions for each upload method.
- Replaces unified Snowflake connector configuration with separate Snowflake and Snowflake Streaming connectors
- Restructures the Sink creation process to clearly distinguish between aggregated and streaming upload modes
- Updates section organization to provide clearer step-by-step guidance for each mode
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| zh_CN/data-integration/snowflake.md | Chinese documentation update separating connector types and reorganizing Sink configuration sections |
| en_US/data-integration/snowflake.md | English documentation update with identical structural changes to match Chinese version |
Co-authored-by: Copilot <[email protected]>
thalesmg
reviewed
Aug 12, 2025
| - **Server Host**: The server host is the Snowflake endpoint URL, typically in the format `<Your Snowflake Organization ID>-<Your Snowflake Account Name>.snowflakecomputing.com`. You need to replace `<Your Snowflake Organization ID>-<Your Snowflake Account Name>` with the subdomain specific to your Snowflake instance. | ||
| - **Username**: (Optional) Enter the Snowflake user with a registered RSA public key if you configured it in `odbc.ini` (e.g. `snowpipeuser`). | ||
| - **Account**: Enter your Snowflake Organization ID and Snowflake account name separated by a dash (`-`), which is part of the URL you use to access the Snowflake platform and can be found in your Snowflake console. | ||
| - **Pipe User**: The name of a Snowflake user account that has a role with permissions to operate the target Pipe, for example, `snowpipeuser`. The role must have at least the `OPERATE` and `MONITOR` privileges. | ||
| - **Private Key Path**: The absolute file path to the private RSA key. EMQX uses this key to sign JWT tokens to authenticate itself with the Snowflake API. This path must be consistent across all nodes of the cluster. For example: |
There was a problem hiding this comment.
For the streaming connector, this is no longer a cluster-wide path but a regular secret (i.e., can be specified inline, or point to a file containing the secret with file://)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.