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-7848] Fail comparisons between different typed ordering values #11961

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

Conversation

linliu-code
Copy link
Contributor

Change Logs

  1. Remove the function that allows the comparison between different types.
  2. Add a test to consolidate the behavior.

Impact

Remove ad hoc support for comparison between different types.

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

No.

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:M PR with lines of changes in (100, 300] label Sep 18, 2024
@linliu-code linliu-code force-pushed the HUDI-7848_verify_delete_record_ordering_value branch from 04be023 to 48d3582 Compare September 19, 2024 19:32
@linliu-code linliu-code changed the title [HUDI-7848][WIP] Fail the comparison between different typed ordering values [HUDI-7848] Fail comparisons between different typed ordering values Sep 19, 2024
Comment on lines +216 to +222
} catch (ClassCastException e) {
throw new HoodieException(String.format(
"Cannot compare values: %s(%s), %s(%s)",
incomingOrderingValue,
incomingOrderingValue.getClass(),
existingOrderingValue,
existingOrderingValue.getClass()));
Copy link
Contributor

Choose a reason for hiding this comment

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

In MergeIntoHoodieTableCommand you need to validate the input schema first. If the schema is incompatible, the error should be thrown there. Deferring error here does not help user as this is not the root cause.

@hudi-bot
Copy link

CI report:

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

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

Successfully merging this pull request may close these issues.

3 participants