Skip to content
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

Revert "NO-SNOW Enable single buffering in Snowpipe Streaming by default (#924)" #981

Merged

Conversation

sfc-gh-mbobowski
Copy link
Contributor

This reverts commit f0e5f23.

Overview

We decided to not enable this setting by default in 2.5.0 release because we are not sure what is the impact on the first read performance.

Pre-review checklist

  • This change should be part of a Behavior Change Release. See go/behavior-change.
  • This change has passed Merge gate tests
  • Snowpipe Changes
  • Snowpipe Streaming Changes
  • This change is TEST-ONLY
  • This change is README/Javadocs only
  • This change is protected by a config parameter <PARAMETER_NAME> eg snowflake.ingestion.method.
    • Yes - Added end to end and Unit Tests.
    • No - Suggest why it is not param protected
  • Is his change protected by parameter <PARAMETER_NAME> on the server side?
    • The parameter/feature is not yet active in production (partial rollout or PrPr, see Changes for Unreleased Features and Fixes).
    • If there is an issue, it can be safely mitigated by turning the parameter off. This is also verified by a test (See go/ppp).

@sfc-gh-mbobowski sfc-gh-mbobowski requested a review from a team as a code owner October 29, 2024 22:33
@@ -495,7 +495,6 @@ public void testStreamingEmptyFlushTime() {
IngestionMethodConfig.SNOWPIPE_STREAMING.toString());
config.put(Utils.SF_ROLE, "ACCOUNTADMIN");
config.remove(SnowflakeSinkConnectorConfig.BUFFER_FLUSH_TIME_SEC);
config.put(SNOWPIPE_STREAMING_ENABLE_SINGLE_BUFFER, "false");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we could keep that, it will be later easier to set the default back to true

Copy link
Contributor

@sfc-gh-wtrefon sfc-gh-wtrefon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, just consider keeping config.put(SNOWPIPE_STREAMING_ENABLE_SINGLE_BUFFER, "false"); in the tests

@sfc-gh-rsawicki sfc-gh-rsawicki enabled auto-merge (squash) October 30, 2024 09:51
@@ -133,7 +133,7 @@ public class SnowflakeSinkConnectorConfig {
public static final String SNOWPIPE_STREAMING_ENABLE_SINGLE_BUFFER =
"snowflake.streaming.enable.single.buffer";

public static final boolean SNOWPIPE_STREAMING_ENABLE_SINGLE_BUFFER_DEFAULT = true;
public static final boolean SNOWPIPE_STREAMING_ENABLE_SINGLE_BUFFER_DEFAULT = false;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we decided not to introduce / change default values of the SDK flush timeout / flush size?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not in 2.5.0. We'll try to figure this out for the next release.

Copy link

@sfc-gh-dseweryn sfc-gh-dseweryn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, it's a revert 😓

@sfc-gh-rsawicki sfc-gh-rsawicki merged commit 0cc5c42 into master Oct 30, 2024
51 of 54 checks passed
@sfc-gh-rsawicki sfc-gh-rsawicki deleted the mbobowski-NO-SNOW-disable-single-buffer-by-default branch October 30, 2024 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants