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

[HUDI-8219] add concurrent schema evolution conflict detection #11978

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Davis-Zhang-Onehouse
Copy link
Contributor

Change Logs

Please refer RFC-78 https://github.com/apache/hudi/pull/11977/files

Impact

Concurrent schema evolution will be protected instead of leaving the data in an inconsistent state

Risk level (write none, low medium or high below)

low given the behavior is exhaustively covered.

Documentation Update

Please refer RFC-78

Contributor's checklist

  • Read through contributor's guide
  • Change Logs and Impact were stated clearly
  • Adequate tests were added if applicable
  • CI passed

@Davis-Zhang-Onehouse Davis-Zhang-Onehouse changed the title [ENG-14385] add concurrent schema evolution conflict detection [HUDI-8219] add concurrent schema evolution conflict detection Sep 20, 2024
@github-actions github-actions bot added the size:M PR with lines of changes in (100, 300] label Sep 20, 2024
@github-actions github-actions bot added size:L PR with lines of changes in (300, 1000] and removed size:M PR with lines of changes in (100, 300] labels Sep 20, 2024
@hudi-bot
Copy link

CI report:

Bot commands @hudi-bot supports the following commands:
  • @hudi-bot run azure re-run the last Azure build

Copy link
Contributor

@yihua yihua left a comment

Choose a reason for hiding this comment

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

Blocked on my review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:L PR with lines of changes in (300, 1000]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants