Questions about Trooper about trooper

[regunathb]

You are right, Trooper does allow you to deploy jobs (job binaries, config and dependency binaries) on the fly and not require a restart of the console/app. It also has the ability to propagate these deployments across a cluster, if you use the batch-HA mode.

All of these are however done on a per-job basis. We prefer it this way as we can maintain job specific config files, classpaths and eventually job-specific Spring application contexts.
The feature for uploading data files has been disabled/removed for this reason.

The good news however is that we use Spring MVC and Http GET/POST to retrieve/update job configurations and dependencies. It is therefore quite possible to add another method in the controller with appropriate @RequestMapping to receive and process a "fat" jar that follows the structure that you have described. The controller can unpack the jar and deploy jobs individually as is done currently.

Is this something you might consider implementing? The code is reasonably contained and is in org.trpr.platform.batch.impl.spring.web.JobConfigController

(https://github.com/regunathb/Trooper/blob/master/batch-core/src/main/java/org/trpr/platform/batch/impl/spring/web/JobConfigController.java)

[regunathb]

Closing this issue as it is not a feature we want to implement now.