nsivabalan opened a new pull request, #12939: URL: https://github.com/apache/hudi/pull/12939
### Change Logs For sort partitioner which was introduced [recently](https://github.com/onehouseinc/hudi-internal/commit/2510486e01ce8d60c300186fec40fd9f9391ab01), the parallelism was not set rightly. Or in other words, we were using the targetParalleism which was determined based on incoming df's num spark partitions. But here, we are only looking at record keys and HoodieFilegroup. We are fixing the same in this patch. Fix: We determine the total comparisons that we might do w/ the bloom and divide that by the bloom.index.keys.per.bucket configured. This will ensure each spark partition will receive the configured number of entries. We do have a follow up ticket https://issues.apache.org/jira/browse/HUDI-9137 to completely determine the spark partitions dynamically instead of relying on keys.per.bucket config. ### Impact Nicely sized spark partitions with sort partitioner ### Risk level (write none, low medium or high below) low ### 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](https://hudi.apache.org/contribute/developer-setup#website) to make changes to the website._ ### Contributor's checklist - [ ] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [ ] Change Logs and Impact were stated clearly - [ ] Adequate tests were added if applicable - [ ] CI passed -- 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]
