docs: add write.intermediate.interval.seconds parameter for Redshift/Snowflake sinks#931
Open
docs: add write.intermediate.interval.seconds parameter for Redshift/Snowflake sinks#931
Conversation
…and Snowflake v2 sinks Co-authored-by: hzxa21 <5518566+hzxa21@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update documentation for copy into without barrier in Redshift
docs: add write.intermediate.interval.seconds parameter for Redshift/Snowflake sinks
Feb 3, 2026
hzxa21
approved these changes
Feb 4, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Redshift and Snowflake v2 sink documentation to describe the new two-tier write scheduling mechanism and the new write.intermediate.interval.seconds parameter.
Changes:
- Added
write.intermediate.interval.seconds(default 1800s) to the Redshift and Snowflake v2 sink option tables to document configurable intermediate storage write frequency. - Clarified that
write.target.interval.secondscontrols target table write/merge frequency, and expanded the upsert-mode descriptions to explain separate intervals for intermediate storage writes and target table merges.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
integrations/destinations/snowflake-v2.mdx |
Documents separate intervals for writing to S3-based intermediate storage and for merging into the Snowflake target table, including the new write.intermediate.interval.seconds parameter. |
integrations/destinations/redshift.mdx |
Mirrors the Snowflake v2 updates for Redshift, adding write.intermediate.interval.seconds and clarifying the role of write.target.interval.seconds in upsert mode. |
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
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.
Description
Documents the new two-tier write scheduling introduced for Redshift and Snowflake v2 sinks. The feature decouples COPY INTO operations from barriers, enabling independent control of intermediate storage writes and target table merges.
Parameter additions:
write.intermediate.interval.seconds(default: 1800s) - controls S3 write frequencywrite.target.interval.secondsdescription - clarifies it controls target table merge frequencyBehavior changes documented:
Both Redshift and Snowflake v2 documentation updated with consistent parameter tables and upsert mode explanations.
Related code PR
risingwavelabs/risingwave#23086
Related doc issue
https://github.com/risingwavelabs/risingwave-docs/issues/[issue-number]
Checklist
mint.jsonto include the page in the table of contents.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.