We need fast processing but don't need persistent jobrepository features.

If there's no way to configure automatic data cleanup, we could switch to a fast inmemory database like h2 (or file based to avoid memory consumption) in order to expose a way to remove data through some SQL cleanup task that we could automate. Wouldn't it be good if the framework directly gave some support?

Cheers
Davide