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(iceberg): fix commit_checkpoint_interval for iceberg table with connector #19788

Conversation

chenzl25
Copy link
Contributor

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

What's changed and what's your intention?

  • Previously, we don't remove the commit_checkpoint_interval from the connector property which will result in a unknown field.

Checklist

  • I have written necessary rustdoc comments.
  • I have added necessary unit tests and integration tests.
  • I have added test labels as necessary.
  • I have added fuzzing tests or opened an issue to track them.
  • My PR contains breaking changes.
  • My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
  • My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

  • My PR needs documentation updates.
Release note

Copy link
Contributor

@StrikeW StrikeW left a comment

Choose a reason for hiding this comment

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

Why not make commit_checkpoint_interval to be a known field? I guess just need to add it to the config struct.

@chenzl25
Copy link
Contributor Author

Why not make commit_checkpoint_interval to be a known field? I guess just need to add it to the config struct.

Because I want to make it available in every source connector when creating a table with an iceberg engine, making it a known field will be invasive to every connector property, while it also doesn't make sense to make it a known field when the table is hummock table.

@graphite-app graphite-app bot requested a review from a team December 12, 2024 15:00
@chenzl25 chenzl25 requested a review from StrikeW December 13, 2024 05:04
Copy link
Contributor

@StrikeW StrikeW 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

// remove commit_checkpoint_interval from source options, otherwise it will be considered as an unknown field.
source
.as_mut()
.map(|x| x.with_properties.remove(COMMIT_CHECKPOINT_INTERVAL));
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess it will be persisted in the sink plan, so even remove it from the PbSource, it can still recovery correctly?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes.

@chenzl25 chenzl25 added this pull request to the merge queue Dec 13, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 13, 2024
@chenzl25 chenzl25 enabled auto-merge December 23, 2024 02:34
@chenzl25 chenzl25 added this pull request to the merge queue Dec 23, 2024
Merged via the queue into main with commit 3cd7241 Dec 23, 2024
29 of 30 checks passed
@chenzl25 chenzl25 deleted the dylan/fix_iceberg_table_commit_checkpoint_interval_with_connector branch December 23, 2024 03:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants