-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update version to 2.2.0 for release #779
Conversation
can we wait for this push, we still have few commits in flight? (We can still push it but having version bump at ends helps) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR itself looks good, but let's merge it when we're ready with the release, thanks!
Sounds good. holding this PR until 1/29 at the latest |
Please rebase from master |
* [external contributor] Support config providers in validation by @swehner (snowflakedb#753) Co-authored-by: Stefan Wehner <[email protected]> * v2.1.2 release change in master (snowflakedb#757) git cherry-pick d4d0e87 * NO-SNOW: Expose the Ingest SDK MAX_CLIENT_LAG configuration in KC (snowflakedb#758) * Add authentication for max lag parameter and fix IT (snowflakedb#763) * SNOW-989387: Fix for java.lang.NoClassDefFoundError (snowflakedb#774) java.lang.NoClassDefFoundError: Could not initialize class net.snowflake.client.jdbc.internal.apache.arrow.memory.RootAllocator occurs when the JDBC driver tries to process the result of the offset migration query. This is a known long-standing issue in the JDBC driver so a workaround is introduced with this fix. * [SNOW-1015644] Update ingest sdk to 2.0.5 (snowflakedb#778) * SNOW-943288, SNOW-938379: Fix two schema evolution cases that could cause non-exactly once delivery (snowflakedb#775) Fix two exactly once delivery behavior issues with Snowpipe Streaming: - When there're gaps between offsets due to records being put into the DLQ or NULL records being skipped, the current logic doesn't work after a channel reopening event (e.g. schema evolution) since it expects continuous offsets in order to guarantee exactly once delivery, causing ingestion to stop. - When a flush is triggered by size or rowcount threshold, it's possible that only partial rows in the buffer are flushed and with a channel reopening event (e.g. schema evolution), currently the leftover rows in the buffer are still being considered which is causing the offset to be advanced and skip some offsets. The fix in this PR makes sure we won't flush any leftover rows in the buffer, they will all be skipped and discarded. The next batch should start from the expected offset after the offset reset as part of the channel reopening event. * resolves issue with generating and building java libary (snowflakedb#780) * [SNOW-88848] Update readme with Snowflake documentation (snowflakedb#781) * Update version to 2.2.0 for release (snowflakedb#779) * Downgrade JDBC to 3.13.30 (snowflakedb#783) * SNOW-922795 Added third-party-licenses to .zip distribution (snowflakedb#784) * PROD-39429 Add PR template (snowflakedb#786) --------- Co-authored-by: revi cheng <[email protected]> Co-authored-by: Stefan Wehner <[email protected]> Co-authored-by: Toby Zhang <[email protected]> Co-authored-by: Waleed Fateem <[email protected]> Co-authored-by: Greg Jachimko <[email protected]> Co-authored-by: Michał Bobowski <[email protected]> Co-authored-by: Jay Patel <[email protected]>
!! v2.2.0 will not be released until beginning of February 2024 !!
This commit updates the version to v2.2.0 which will contain everything before this commit in the master branch