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

fix(jdbc-sink): relax the check for UPDATE_DELETE op #17289

Merged
merged 3 commits into from
Jun 18, 2024

Conversation

StrikeW
Copy link
Contributor

@StrikeW StrikeW commented Jun 18, 2024

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

It should be safe to ignore the U- op in jdbc sink, since we use UPSERT to deliver events into downstream database which can resolve the inconsistent events.

related: #14031

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • I have added test labels as necessary. See details.
  • I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
  • My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
  • All checks passed in ./risedev check (or alias, ./risedev c)
  • My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)
  • My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

@StrikeW StrikeW added need-cherry-pick-release-1.9 need-cherry-pick-release-1.10 Open a cherry-pick PR to branch release-1.10 after the current PR is merged labels Jun 18, 2024
@github-actions github-actions bot added the type/fix Bug fix label Jun 18, 2024
@StrikeW StrikeW requested review from fuyufjh, st1page and wenym1 June 18, 2024 03:22
@BugenZhao BugenZhao requested a review from stdrc June 18, 2024 03:49
@StrikeW StrikeW force-pushed the siyuan/jdbc-sink-ignore-ud branch from cae66b8 to 4ae9444 Compare June 18, 2024 05:52
@StrikeW StrikeW enabled auto-merge June 18, 2024 05:57
@StrikeW StrikeW added this pull request to the merge queue Jun 18, 2024
Copy link
Contributor

@wenym1 wenym1 left a comment

Choose a reason for hiding this comment

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

Rest LGTM.

Just curious that when will we miss the upsert delete?

@@ -185,6 +185,9 @@ impl<F: LogStoreFactory> SinkExecutor<F> {
&& !self.sink_param.downstream_pk.is_empty();
// Don't compact chunk for blackhole sink for better benchmark performance.
let compact_chunk = !self.sink.is_blackhole();
tracing::info!("Sink info: sink_id: {} actor_id: {}, need_advance_delete: {}, re_construct_with_sink_pk: {}",
Copy link
Contributor

Choose a reason for hiding this comment

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

Can be tracing::info!(sink_id, actor_id, need_advanc_delete, re_construct_with_sink_pk, "sink info") to avoid manually generating the format string.

@st1page
Copy link
Contributor

st1page commented Jun 18, 2024

Just curious that when will we miss the upsert delete?

Not sure why, more context here https://risingwave-labs.slack.com/archives/C06F37346CR/p1718669258478389

Merged via the queue into main with commit ee06743 Jun 18, 2024
29 of 30 checks passed
@StrikeW StrikeW deleted the siyuan/jdbc-sink-ignore-ud branch June 18, 2024 06:45
@lmatz
Copy link
Contributor

lmatz commented Jun 18, 2024

I forgot to add the cherry-pick action for v1.10, I will relabel to trigger the action after #17301

@lmatz lmatz added need-cherry-pick-release-1.10 Open a cherry-pick PR to branch release-1.10 after the current PR is merged and removed need-cherry-pick-release-1.10 Open a cherry-pick PR to branch release-1.10 after the current PR is merged labels Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need-cherry-pick-release-1.10 Open a cherry-pick PR to branch release-1.10 after the current PR is merged type/fix Bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants