Skip to content

[HUDI-8401] Add config to support preference to old records#13416

Closed
linliu-code wants to merge 1 commit intoapache:masterfrom
linliu-code:HUDI-8401-revamp-1
Closed

[HUDI-8401] Add config to support preference to old records#13416
linliu-code wants to merge 1 commit intoapache:masterfrom
linliu-code:HUDI-8401-revamp-1

Conversation

@linliu-code
Copy link
Collaborator

Change Logs

When we want to support FirstValueAvroPayload by merge mode, we need to add this config to support the same logic.

Impact

Enable EVENT_TIME_ORDERING to support first value logic.

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

None.

Documentation Update

Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

  • The config description must be updated if new configs are added or the default value of the configs are changed
  • Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
    ticket number here and follow the instruction to make
    changes to the website.

Contributor's checklist

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

@github-actions github-actions bot added the size:S PR with lines of changes in (10, 100] label Jun 10, 2025
.withDocumentation("Whether to use positions in the block header for data blocks containing updates and delete blocks for merging.");

public static final ConfigProperty<Boolean> MERGE_PREFER_OLD_RECORD = ConfigProperty
.key("hoodie.merge.prefer.old.record")
Copy link
Contributor

Choose a reason for hiding this comment

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

hoodie.merge.event.time.first.value.enabled?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

right. Will do. Meanwhile, need to make it as table config.

Copy link
Contributor

Choose a reason for hiding this comment

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

another choice is to add a new merge mode.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think there is no need to add a new merge mode for this small variance; otherwise, we will see large number of merge modes later.

@hudi-bot
Copy link
Collaborator

CI report:

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

@danny0405
Copy link
Contributor

As discussed offline, the first value support would be removed first to payloads clean up, see #13420

@danny0405 danny0405 closed this Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:S PR with lines of changes in (10, 100]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants