What is meant by materilisation in oozie coordinator?
Answers
Answered by
0
Actual time: The actual time indicates the time when something actually happens.
Nominal time: The nominal time specifies the time when something should happen. In theory the nominal time and the actual time should mach, however, in practice due to delays the actual time may occur later than the nominal time.
Dataset: Collection of data referred to by a logical name. A dataset normally has several instances of data and each one of them can be referred individually. Each dataset instance is represented by a unique set of URIs.
Synchronous Dataset: Synchronous datasets instances are generated at fixed time intervals and there is a dataset instance associated with each time interval. Synchronous dataset instances are identified by their nominal time. For example, in the case of a file system based dataset, the nominal time would be somewhere in the file path of the dataset instance: hdfs://foo:9000/usr/logs/2009/04/15/23/30.
Coordinator Action: A coordinator action is a workflow job that is started when a set of conditions are met (input dataset instances are available).
Coordinator Application: A coordinator application defines the conditions under which coordinator actions should be created (the frequency) and when the actions can be started. The coordinator application also defines a start and an end time. Normally, coordinator applications are parameterized. A Coordinator application is written in XML.
Coordinator Job: A coordinator job is an executable instance of a coordination definition. A job submission is done by submitting a job configuration that resolves all parameters in the application definition.
Data pipeline: A data pipeline is a connected set of coordinator applications that consume and produce interdependent datasets.
Coordinator Definition Language: The language used to describe datasets and coordinator applications.
Coordinator Engine: A system that executes coordinator jobs.
Nominal time: The nominal time specifies the time when something should happen. In theory the nominal time and the actual time should mach, however, in practice due to delays the actual time may occur later than the nominal time.
Dataset: Collection of data referred to by a logical name. A dataset normally has several instances of data and each one of them can be referred individually. Each dataset instance is represented by a unique set of URIs.
Synchronous Dataset: Synchronous datasets instances are generated at fixed time intervals and there is a dataset instance associated with each time interval. Synchronous dataset instances are identified by their nominal time. For example, in the case of a file system based dataset, the nominal time would be somewhere in the file path of the dataset instance: hdfs://foo:9000/usr/logs/2009/04/15/23/30.
Coordinator Action: A coordinator action is a workflow job that is started when a set of conditions are met (input dataset instances are available).
Coordinator Application: A coordinator application defines the conditions under which coordinator actions should be created (the frequency) and when the actions can be started. The coordinator application also defines a start and an end time. Normally, coordinator applications are parameterized. A Coordinator application is written in XML.
Coordinator Job: A coordinator job is an executable instance of a coordination definition. A job submission is done by submitting a job configuration that resolves all parameters in the application definition.
Data pipeline: A data pipeline is a connected set of coordinator applications that consume and produce interdependent datasets.
Coordinator Definition Language: The language used to describe datasets and coordinator applications.
Coordinator Engine: A system that executes coordinator jobs.
Similar questions