[GitHub] [hudi] yihua commented on pull request #8319: [HUDI-5934] Remove archival configs for metadata table
yihua commented on PR #8319: URL: https://github.com/apache/hudi/pull/8319#issuecomment-1518526370 Only Flink IT fails due to flakiness, which is irrelevant to the PR. Merging the PR. https://user-images.githubusercontent.com/2497195/233765937-6c41e3f2-e9d3-4598-a589-7c73b9b8f018.png";> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@hudi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hudi] yihua commented on pull request #8319: [HUDI-5934] Remove archival configs for metadata table
yihua commented on PR #8319: URL: https://github.com/apache/hudi/pull/8319#issuecomment-1518431864 @hudi-bot run azure -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@hudi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hudi] yihua commented on pull request #8319: [HUDI-5934] Remove archival configs for metadata table
yihua commented on PR #8319: URL: https://github.com/apache/hudi/pull/8319#issuecomment-1518430572 @hudi-bot run azure -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@hudi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hudi] yihua commented on pull request #8319: [HUDI-5934] Remove archival configs for metadata table
yihua commented on PR #8319: URL: https://github.com/apache/hudi/pull/8319#issuecomment-1489540341 > I guess, the question is, do users ever want to retain more commit in MDT compared to DT for investigation purposes for eg. @prashantwason : do you have any take here. or are we good to get rid of it. Retaining more commits in MDT is going to make MDT read slower, especially on cloud storage, as there are more instant files under `metadata/.hoodie` and loading active timeline takes more time. So I think it is reasonable to assume that data table's and metadata table's timelines go hand in hand. For investigation purposes, if there are more commits in MDT compared to DT, the corresponding commits in DT are in the archived timeline, which requires loading the archived timeline anyway. With this PR, we can still investigate all the commits in the archived timeline. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@hudi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
