airflow.operators.python
¶
Module Contents¶
Classes¶
Executes a Python callable |
|
Allows a workflow to "branch" or follow a path following the execution |
|
Allows a pipeline to continue based on the result of a |
|
Allows one to run a function in a virtualenv that is created and destroyed |
Functions¶
|
Deprecated function that calls @task.python and allows users to turn a python function into |
Obtain the execution context for the currently executing operator without |
- airflow.operators.python.task(python_callable=None, multiple_outputs=None, **kwargs)[source]¶
Deprecated function that calls @task.python and allows users to turn a python function into an Airflow task. Please use the following instead:
from airflow.decorators import task
@task def my_task()
- Parameters
python_callable (Optional[Callable]) – A reference to an object that is callable
op_kwargs – a dictionary of keyword arguments that will get unpacked in your function (templated)
op_args – a list of positional arguments that will get unpacked when calling your callable (templated)
multiple_outputs (Optional[bool]) – if set, function return value will be unrolled to multiple XCom values. Dict will unroll to xcom values with keys as keys. Defaults to False.
- Returns
- class airflow.operators.python.PythonOperator(*, python_callable, op_args=None, op_kwargs=None, templates_dict=None, templates_exts=None, show_return_value_in_logs=True, **kwargs)[source]¶
Bases:
airflow.models.baseoperator.BaseOperator
Executes a Python callable
See also
For more information on how to use this operator, take a look at the guide: PythonOperator
When running your callable, Airflow will pass a set of keyword arguments that can be used in your function. This set of kwargs correspond exactly to what you can use in your jinja templates. For this to work, you need to define
**kwargs
in your function header, or you can add directly the keyword arguments you would like to get - for example with the below code your callable will get the values ofti
andnext_ds
context variables.With explicit arguments:
def my_python_callable(ti, next_ds): pass
With kwargs:
def my_python_callable(**kwargs): ti = kwargs["ti"] next_ds = kwargs["next_ds"]
- Parameters
python_callable (Callable) – A reference to an object that is callable
op_kwargs (Optional[Mapping[str, Any]]) – a dictionary of keyword arguments that will get unpacked in your function
op_args (Optional[Collection[Any]]) – a list of positional arguments that will get unpacked when calling your callable
templates_dict (Optional[Dict[str, Any]]) – a dictionary where the values are templates that will get templated by the Airflow engine sometime between
__init__
andexecute
takes place and are made available in your callable’s context after the template has been applied. (templated)templates_exts (Optional[Sequence[str]]) – a list of file extensions to resolve while processing templated fields, for examples
['.sql', '.hql']
show_return_value_in_logs (bool) – a bool value whether to show return_value logs. Defaults to True, which allows return value log output. It can be set to False to prevent log output of return value when you return huge data such as transmission a large amount of XCom to TaskAPI.
- class airflow.operators.python.BranchPythonOperator(*, python_callable, op_args=None, op_kwargs=None, templates_dict=None, templates_exts=None, show_return_value_in_logs=True, **kwargs)[source]¶
Bases:
PythonOperator
,airflow.models.skipmixin.SkipMixin
Allows a workflow to “branch” or follow a path following the execution of this task.
It derives the PythonOperator and expects a Python function that returns a single task_id or list of task_ids to follow. The task_id(s) returned should point to a task directly downstream from {self}. All other “branches” or directly downstream tasks are marked with a state of
skipped
so that these paths can’t move forward. Theskipped
states are propagated downstream to allow for the DAG state to fill up and the DAG run’s state to be inferred.
- class airflow.operators.python.ShortCircuitOperator(*, ignore_downstream_trigger_rules=True, **kwargs)[source]¶
Bases:
PythonOperator
,airflow.models.skipmixin.SkipMixin
Allows a pipeline to continue based on the result of a
python_callable
.The ShortCircuitOperator is derived from the PythonOperator and evaluates the result of a
python_callable
. If the returned result is False or a falsy value, the pipeline will be short-circuited. Downstream tasks will be marked with a state of “skipped” based on the short-circuiting mode configured. If the returned result is True or a truthy value, downstream tasks proceed as normal and anXCom
of the returned result is pushed.The short-circuiting can be configured to either respect or ignore the
trigger_rule
set for downstream tasks. Ifignore_downstream_trigger_rules
is set to True, the default setting, all downstream tasks are skipped without considering thetrigger_rule
defined for tasks. However, if this parameter is set to False, the direct downstream tasks are skipped but the specifiedtrigger_rule
for other subsequent downstream tasks are respected. In this mode, the operator assumes the direct downstream tasks were purposely meant to be skipped but perhaps not other subsequent tasks.See also
For more information on how to use this operator, take a look at the guide: ShortCircuitOperator
- Parameters
ignore_downstream_trigger_rules (bool) – If set to True, all downstream tasks from this operator task will be skipped. This is the default behavior. If set to False, the direct, downstream task(s) will be skipped but the
trigger_rule
defined for a other downstream tasks will be respected.
- class airflow.operators.python.PythonVirtualenvOperator(*, python_callable, requirements=None, python_version=None, use_dill=False, system_site_packages=True, pip_install_options=None, op_args=None, op_kwargs=None, string_args=None, templates_dict=None, templates_exts=None, **kwargs)[source]¶
Bases:
PythonOperator
Allows one to run a function in a virtualenv that is created and destroyed automatically (with certain caveats).
The function must be defined using def, and not be part of a class. All imports must happen inside the function and no variables outside of the scope may be referenced. A global scope variable named virtualenv_string_args will be available (populated by string_args). In addition, one can pass stuff through op_args and op_kwargs, and one can use a return value. Note that if your virtualenv runs in a different Python major version than Airflow, you cannot use return values, op_args, op_kwargs, or use any macros that are being provided to Airflow through plugins. You can use string_args though.
See also
For more information on how to use this operator, take a look at the guide: PythonVirtualenvOperator
- Parameters
python_callable (Callable) – A python function with no references to outside variables, defined with def, which will be run in a virtualenv
requirements (Union[None, Iterable[str], str]) – Either a list of requirement strings, or a (templated) “requirements file” as specified by pip.
python_version (Optional[Union[str, int, float]]) – The Python version to run the virtualenv with. Note that both 2 and 2.7 are acceptable forms.
use_dill (bool) – Whether to use dill to serialize the args and result (pickle is default). This allow more complex types but requires you to include dill in your requirements.
system_site_packages (bool) – Whether to include system_site_packages in your virtualenv. See virtualenv documentation for more information.
pip_install_options (Optional[List[str]]) – a list of pip install options when installing requirements See ‘pip install -h’ for available options
op_args (Optional[Collection[Any]]) – A list of positional arguments to pass to python_callable.
op_kwargs (Optional[Mapping[str, Any]]) – A dict of keyword arguments to pass to python_callable.
string_args (Optional[Iterable[str]]) – Strings that are present in the global var virtualenv_string_args, available to python_callable at runtime as a list[str]. Note that args are split by newline.
templates_dict (Optional[Dict]) – a dictionary where the values are templates that will get templated by the Airflow engine sometime between
__init__
andexecute
takes place and are made available in your callable’s context after the template has been appliedtemplates_exts (Optional[List[str]]) – a list of file extensions to resolve while processing templated fields, for examples
['.sql', '.hql']
- execute(context)[source]¶
This is the main method to derive when creating an operator. Context is the same dictionary used as when rendering jinja templates.
Refer to get_template_context for more context.
- airflow.operators.python.get_current_context()[source]¶
Obtain the execution context for the currently executing operator without altering user method’s signature. This is the simplest method of retrieving the execution context dictionary.
Old style:
def my_task(**context): ti = context["ti"]
New style:
from airflow.operators.python import get_current_context def my_task(): context = get_current_context() ti = context["ti"]
Current context will only have value if this method was called after an operator was starting to execute.