Skip to content

[HUDI-8110] Throw an error for time travel query on MDT#11819

Closed
lokeshj1703 wants to merge 2 commits intoapache:masterfrom
lokeshj1703:HUDI-8110
Closed

[HUDI-8110] Throw an error for time travel query on MDT#11819
lokeshj1703 wants to merge 2 commits intoapache:masterfrom
lokeshj1703:HUDI-8110

Conversation

@lokeshj1703
Copy link
Collaborator

Change Logs

Spark datasource read on MDT (spark.read.format("hudi").option("as.of.instant", ..).load(mdt_base_path)) should throw an error indicating that this is not supported.

Impact

NA

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

low

Documentation Update

NA

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 Aug 23, 2024
Copy link
Contributor

@CTTY CTTY left a comment

Choose a reason for hiding this comment

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

Hi @lokeshj1703 ,
Thanks for contributing!
The changes look fine to me but was curious if there is any specific case that users or Hudi components may run time travel queries on MDT?

@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

@lokeshj1703
Copy link
Collaborator Author

@CTTY I think the time travel queries on MDT should be executed mainly for debugging purposes. The hudi components do not use time travel query on MDT.

@yihua
Copy link
Contributor

yihua commented Aug 29, 2024

We have the fix now, so closing this one.

@yihua yihua closed this Aug 29, 2024
@yihua
Copy link
Contributor

yihua commented Aug 29, 2024

The fix to time travel query on MDT: #11860

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.

4 participants