update known Snowflake issues #599
Conversation
|
@davidhcoe : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
Change sent to author
connectors/subsvc
powerquery/svc
labels
|
Learn Build status updates of commit 7ffd8a5: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 934727d: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
Learn Build status updates of commit f1ef194: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 3075bf8: ✅ Validation status: passed
For more details, please refer to the build report. |
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @DougKlopfenstein |
|
#sign-off |
prmerger-automator
bot
added
ready-to-merge
and removed
do-not-merge
|
@DougKlopfenstein - This PR contains one blocking issue on line 180: Content should describe only what is possible with the released product to avoid confusion or mistrust if future features are delayed or canceled. Could you/we delete or rewrite the following phrase? "A fix is planned for late 2025/early 2026." #hold-off |
prmerger-automator
bot
added
do-not-merge
|
Adding @davidhcoe to make the changes. |
Co-authored-by: Shannon Leavitt <[email protected]>
|
Learn Build status updates of commit 548b6d5: ✅ Validation status: passed
For more details, please refer to the build report. |
I removed the dates. |
|
Learn Build status updates of commit 5338a6e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@DougKlopfenstein - When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
#sign-off |
prmerger-automator
bot
added
ready-to-merge
and removed
do-not-merge
There was a problem hiding this comment.
Pull Request Overview
Updates the Snowflake connector documentation to revise migration timeline details and add a new known issue about increased memory usage. The PR removes the specific November 2025 migration deadline and updates instructions for reverting to the legacy connector.
- Removes the specific November 2025 date for completing the 2.0 implementation migration
- Updates self-mitigation instructions from specifying Implementation="1.0" to removing Implementation="2.0"
- Adds a new known issue about increased memory consumption that can cause resource governing errors
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| The Snowflake connector implementation 2.0 is built using the open-source [Arrow Database Connectivity](https://arrow.apache.org/docs/format/ADBC.html) (ADBC) driver. ADBC provides a set of standard interfaces for interacting with Arrow data, which is especially efficient at fetching large datasets with minimal overhead and no serialization or copying. The ADBC driver also incorporates security enhancements such as memory safety and garbage collection. Additionally, collaboration with the open-source community enables more rapid updates, utilizing modern tools and secure development lifecycle (SDL) processes. | ||
|
|
||
| To enable you to take advantage of these performance and security enhancements, starting July 2025, all the newly created connections automatically uses the 2.0 implementation. In addition, we'll gradually transition existing customers to the 2.0 implementation in phases, with updates being applied to different regions through November 2025. During this period, you can test the 2.0 implementation by updating your existing queries and adding the `Implementation="2.0"` flag in `Snowflake.Databases` as follows. After the transition, connections that do not specify an implementation will be automatically updated to the 2.0 implementation. | ||
| To enable you to take advantage of these performance and security enhancements, starting July 2025, all the newly created connections automatically uses the 2.0 implementation. In addition, we'll gradually transition existing customers to the 2.0 implementation in phases. We will share more details in late 2025/early 2026. During this period, you can test the 2.0 implementation by updating your existing queries and adding the `Implementation="2.0"` flag in `Snowflake.Databases` as follows. After the transition, connections that do not specify an implementation will be automatically updated to the 2.0 implementation. |
There was a problem hiding this comment.
| To enable you to take advantage of these performance and security enhancements, starting July 2025, all the newly created connections automatically uses the 2.0 implementation. In addition, we'll gradually transition existing customers to the 2.0 implementation in phases. We will share more details in late 2025/early 2026. During this period, you can test the 2.0 implementation by updating your existing queries and adding the `Implementation="2.0"` flag in `Snowflake.Databases` as follows. After the transition, connections that do not specify an implementation will be automatically updated to the 2.0 implementation. | |
| To enable you to take advantage of these performance and security enhancements, starting July 2025, all the newly created connections automatically uses the 2.0 implementation. In addition, we'll gradually transition existing customers to the 2.0 implementation in phases. We will share more details in late 2025/early 2026. During this period, you can test the 2.0 implementation by updating your existing queries and adding the `Implementation="2.0"` flag in `Snowflake.Databases` as follows. After the transition, connections that do not specify an implementation will be automatically updated to the 2.0 implementation. |
@DougKlopfenstein @davidhcoe "We will share more details in late 2025/early 2026" still constitutes as a future promise. We don't want to lose trust by stating a date if we end up not meeting it. #hold-off
prmerger-automator
bot
added
do-not-merge
|
You typed hold-off, but the PR wasn't signed off, so nothing was changed. |
5 participants
Updates details about known issues for Snowflake and removes the November 2025 date for migrating to 2.0.