Skip to content

Quartz3 Ideas

Jump to bottom
Zemian Deng edited this page Mar 1, 2019 · 1 revision

Quartz 3.0 Ideas

We will collect all the feature requests and planning ideas on this page for the next Quartz 3.0. Feel free to open an Issue to add or discuss any of these items.

  • Upgrade to latest JDK8 (Support JDK9/10/11?)

  • Cleanup codebase and keep repository slim with only quartz related code? (Can we remove/move terracotta specific implementation?)

  • Remove unused/infrequent used code/modules?

  • Make release process easier?

  • Make code contribution easier?

  • Keep at least one consistent and supported DB schema and generate other different DB provider schema instead of hard coded schema?

  • Add more out of box Quartz user experience? Like a QuartzServer that takes a configurable quartz.properties. A runnable webapp that uses quartz.

  • Tool that help generate Cron expression.

  • Allow user to see next fire times from triggers easier.

  • Rework DB store to not use BLOB but with JSON instead?

  • Add ClassLoader impl that allow user to add job classes after the server started?

  • A more simple user interface for common job scheduling. The quartz DSL is still too much to setup/do/learn to get just a simple job going.

  • A more clear API for client verse server?

  • Add Java Annotation as metadata for Job and Trigger?

  • Support Java new time package and related date types besides plain old java.util.Date?

  • Allow user to write custom Trigger easier?

  • Can we support multiple groups? How about remove Group and use Tags instead? This simplifies that job only needs one unique name. Tags should be optional and used for filtering/grouping purpose.

  • Allow user easier to customize thread pool and be able to bound job to each pool.

  • Allow jobs to be execute as "workflow"

  • Invalid/outdated/missing jobclass should not prevent scheduler to start up.

Clone this wiki locally