airflow.providers.amazon.aws.sensors.glacier
¶
Module Contents¶
Classes¶
Glacier jobs description. |
|
Glacier sensor for checking job state. This operator runs only in reschedule mode. |
- class airflow.providers.amazon.aws.sensors.glacier.JobStatus[source]¶
Bases:
enum.Enum
Glacier jobs description.
- class airflow.providers.amazon.aws.sensors.glacier.GlacierJobOperationSensor(*, vault_name, job_id, poke_interval=60 * 20, mode='reschedule', **kwargs)[source]¶
Bases:
airflow.providers.amazon.aws.sensors.base_aws.AwsBaseSensor
[airflow.providers.amazon.aws.hooks.glacier.GlacierHook
]Glacier sensor for checking job state. This operator runs only in reschedule mode.
See also
For more information on how to use this sensor, take a look at the guide: Wait on an Amazon Glacier job state
- Parameters
aws_conn_id – The reference to the AWS connection details
vault_name (str) – name of Glacier vault on which job is executed
job_id (str) – the job ID was returned by retrieve_inventory()
poke_interval (int) – Time in seconds that the job should wait in between each tries
mode (str) – How the sensor operates. Options are:
{ poke | reschedule }
, default ispoke
. When set topoke
the sensor is taking up a worker slot for its whole execution time and sleeps between pokes. Use this mode if the expected runtime of the sensor is short or if a short poke interval is required. Note that the sensor will hold onto a worker slot and a pool slot for the duration of the sensor’s runtime in this mode. When set toreschedule
the sensor task frees the worker slot when the criteria is not yet met and it’s rescheduled at a later time. Use this mode if the time before the criteria is met is expected to be quite long. The poke interval should be more than one minute to prevent too much load on the scheduler.
- template_fields: collections.abc.Sequence[str][source]¶