Hi there,

as we all know the coordinator jobs  are materialized, when frequency is
given w/ a Cron expression, regardless of timezone attribute
<https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java#L471>,
considering only oozie.processing.timezone
<https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java#L801>
configuration entry. This is often very confusing for users.

I think following can be done:

   - in 4.4.0 timeframe: extend the Coordinator Functional Specification by
   mentioning this fact
   - in 5.0.0 timeframe:
      - alter functionality that timezone attribute is also considered when
      frequency is Cron based
      - make this behavior configurable
      - make this behavior switched off by default, in order all
previous <coordinator-app
      /> instances continue working

What are your thoughts?

Andras

Reply via email to