deepakpanda93 commented on issue #15785: URL: https://github.com/apache/hudi/issues/15785#issuecomment-5314801007
This issue was reviewed as part of the JIRA-migrated backlog triage. Findings: the underlying regression is fixed, and no documentation is needed for any currently supported release. The Hive sync performance problem — metastore sync always loading the archived timeline when a last-sync time was given, without caching it, causing read timeouts on cloud storage from request rate limiting — was introduced by #6662 (HUDI-4832) and fixed by #7561 (HUDI-5477). Checking `HoodieSyncClient` across release branches, the fix is absent in 0.12.1 and 0.12.2 and present from 0.12.3 onward, including 0.13.0, 0.14.2 and 1.2.0. In current master, `HoodieSyncClient.getWrittenPartitionsSince` (HoodieSyncClient.java:152) routes through `TimelineUtils.getCommitsTimelineAfter` (TimelineUtils.java:318), the API that PR #7561 added. So only 0.12.1 and 0.12.2 were ever affected. The requested note was indeed never added to those release notes — their Known Regressions sections cover HUDI-5863 and HUDI-3730 only — but both releases have been EOL for years, and a known regression documented against a version that does not have it would be misleading rather than helpful. Closing as fixed. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
