finally I got the mongo backend working, but I would like to submit some feature requests.
1) Currently it is only possible to use jobdata on triggers (but not on jobs). And I think jobs will therefore not be updated after execution (annontation @PersistJobDataAfterExecution).
So it would be great to store jobdata on jobs too and persist them if requested.
2) In the trigger the jobdata is just as base encoded string.
Since jobdatamap can only hold primitives anyway, why not store them as json/bson embedded object. this would have the big advandatege that the job data is searchable!
3) A really nice feature would be if you can make a new implementation of org.quartz.plugins.history.LoggingJobHistoryPlugin and org.quartz.plugins.history.LoggingTriggerHistoryPlugin to store the result in a time to live constraint collection.
finally I got the mongo backend working, but I would like to submit some feature requests.
1) Currently it is only possible to use jobdata on triggers (but not on jobs). And I think jobs will therefore not be updated after execution (annontation @PersistJobDataAfterExecution).
So it would be great to store jobdata on jobs too and persist them if requested.
2) In the trigger the jobdata is just as base encoded string.
Since jobdatamap can only hold primitives anyway, why not store them as json/bson embedded object. this would have the big advandatege that the job data is searchable!
3) A really nice feature would be if you can make a new implementation of org.quartz.plugins.history.LoggingJobHistoryPlugin and org.quartz.plugins.history.LoggingTriggerHistoryPlugin to store the result in a time to live constraint collection.