You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by as...@apache.org on 2020/01/09 12:19:39 UTC
[oozie] branch master updated: OOZIE-3579 [docs] Fix typos in
coordinator documentation (qsbao via asalamon74)
This is an automated email from the ASF dual-hosted git repository.
asalamon74 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/oozie.git
The following commit(s) were added to refs/heads/master by this push:
new 458bf0b OOZIE-3579 [docs] Fix typos in coordinator documentation (qsbao via asalamon74)
458bf0b is described below
commit 458bf0ba422a2a502860020e997190a9d91bd684
Author: Andras Salamon <as...@apache.org>
AuthorDate: Thu Jan 9 13:19:21 2020 +0100
OOZIE-3579 [docs] Fix typos in coordinator documentation (qsbao via asalamon74)
---
docs/src/site/markdown/CoordinatorFunctionalSpec.md | 15 +++++++++++----
release-log.txt | 1 +
2 files changed, 12 insertions(+), 4 deletions(-)
diff --git a/docs/src/site/markdown/CoordinatorFunctionalSpec.md b/docs/src/site/markdown/CoordinatorFunctionalSpec.md
index d31d1aa..5afc97e 100644
--- a/docs/src/site/markdown/CoordinatorFunctionalSpec.md
+++ b/docs/src/site/markdown/CoordinatorFunctionalSpec.md
@@ -1086,17 +1086,24 @@ The frequency of the `hourlyRevenue-coord` coordinator job is 1 hour, this means
### 6.3. Synchronous Coordinator Application Definition
-A synchronous coordinator definition is a is defined by a name, start time and end time, the frequency of creation of its coordinator actions, the input events, the output events and action control information:
+A synchronous coordinator definition is defined by a name, start time and end time, the frequency of creation of its coordinator
+actions, the input events, the output events and action control information:
* **<font color="#0000ff"> start: </font>** The start datetime for the job. Starting at this time actions will be materialized. Refer to section #3 'Datetime Representation' for syntax details.
* **<font color="#0000ff"> end: </font>** The end datetime for the job. When actions will stop being materialized. Refer to section #3 'Datetime Representation' for syntax details.
* **<font color="#0000ff"> timezone:</font>** The timezone of the coordinator application.
* **<font color="#0000ff"> frequency: </font>** The frequency, in minutes, to materialize actions. Refer to section #4 'Time Interval Representation' for syntax details.
* Control information:
- * **<font color="#0000ff"> timeout: </font>** The maximum time, in minutes, that a materialized action will be waiting for the additional conditions to be satisfied before being discarded. A timeout of `0` indicates that at the time of materialization all the other conditions must be satisfied, else the action will be discarded. A timeout of `0` indicates that if all the input events are not satisfied at the time of action materialization, the action should timeout immediately. A t [...]
+ * **<font color="#0000ff"> timeout: </font>** The maximum time, in minutes, that a materialized action will be waiting
+ for the additional conditions to be satisfied before being discarded. A timeout of `0` indicates that if all the input
+ events are not satisfied at the time of action materialization, the action should timeout immediately. A timeout of
+ `-1` indicates no timeout, the materialized action will wait forever for the other conditions to be satisfied. The
+ default value is `120` minutes. The timeout can only cause a `WAITING` action to transition to `TIMEDOUT`; once the
+ data dependency is satisified, a `WAITING` action transitions to `READY`, and the timeout no longer has any affect,
+ even if the action hasn't transitioned to `SUBMITTED` or `RUNNING` when it expires.
* **<font color="#0000ff"> concurrency: </font>** The maximum number of actions for this job that can be running at the same time. This value allows to materialize and submit multiple instances of the coordinator app, and allows operations to catchup on delayed processing. The default value is `1`.
* **<font color="#0000ff"> execution: </font>** Specifies the execution order if multiple instances of the coordinator job have satisfied their execution criteria. Valid values are:
- ** `FIFO` (oldest first) **default*.
+ * `FIFO` (oldest first) **default**.
* `LIFO` (newest first).
* `LAST_ONLY` (see explanation below).
* `NONE` (see explanation below).
@@ -1201,7 +1208,7 @@ before 5:19pm. Both actions will become `SKIPPED`, assuming they don't transitio
**<font color="#008000"> Examples: </font>**
-**1. A Coordinator Job that creates an executes a single coordinator action:**
+**1. A Coordinator Job that executes a single coordinator action:**
The following example describes a synchronous coordinator application that runs once a day for 1 day at the end of the day. It consumes an instance of a daily 'logs' dataset and produces an instance of a daily 'siteAccessStats' dataset.
diff --git a/release-log.txt b/release-log.txt
index 5acd705..999371e 100644
--- a/release-log.txt
+++ b/release-log.txt
@@ -1,5 +1,6 @@
-- Oozie 5.3.0 release (trunk - unreleased)
+OOZIE-3579 [docs] Fix typos in coordinator documentation (qsbao via asalamon74)
OOZIE-3066 Possibility to set retry-max globally (qsbao via asalamon74)
OOZIE-3578 MapReduce counters cannot be used over 120 (dionusos via pbacsko, gezapeti)
OOZIE-3573 Fix oozie-default.xml descriptions (arvaiadam via asalamon74)