Changing Executor implementations or configuration is far less invasive than changing the way tasks are submitted; Executor configuration is generally a one-time event and can easily be exposed for deployment-time configuration, whereas task submission code tends to be strewn throughout the program and harder to expose. It allows for parallelization of work across nodes. If the number of files exceeds this limit, the merge will proceed in several passes. See SkipBadRecords. This process is completely transparent to the application.
nest...