Spring Batch custom completion policy for dynamic chunk size
Context We have a batch job that replicates localized country names (i.e. translations of country names to different languages) to our DB from the external one. The idea was to process all localized country names for a single country in 1 chunk (i.e. first chunk - all translations for Andorra, next chunk - all translations for U.A.E., etc.). We use JdbcCursorItemReader for reading external data + some oracle analytic functions to provide total number of translations available for the country: something like select country_code, language_code, localized_name, COUNT(1) OVER(PARTITION BY c_lng