airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Commented] (AIRFLOW-5567) Improved primitive for building Operators that benefit from reschedule mode
Date Sat, 28 Sep 2019 20:04:00 GMT


ASF GitHub Bot commented on AIRFLOW-5567:

jaketf commented on pull request #6210: [AIRFLOW-5567] prototype BaseAsyncOperator
   Make sure you have checked _all_ steps below.
   ### Jira
   - [ ] My PR addresses the following [Airflow Jira](
issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - In case you are fixing a typo in the documentation you can prepend your commit with
\[AIRFLOW-XXX\], code changes always need a Jira issue.
     - In case you are proposing a fundamental code change, you need to create an Airflow
Improvement Proposal ([AIP](
     - In case you are adding a dependency, check if the license complies with the [ASF 3rd
Party License Policy](
   ### Description
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
   ### Commits
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed
multiple commits if they address the same issue. In addition, my commits follow the guidelines
from "[How to write a good git commit message](":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   ### Documentation
   - [ ] In case of new functionality, my PR adds documentation that describes how to use
     - All the public functions and the classes in the PR contain docstrings that explain
what it does
     - If you implement backwards incompatible changes, please leave a note in the [](
so we can assign it to a appropriate release
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Improved primitive for building Operators that benefit from reschedule mode
> ---------------------------------------------------------------------------
>                 Key: AIRFLOW-5567
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: models, operators
>    Affects Versions: 1.10.5
>            Reporter: Jacob Ferriero
>            Assignee: Jacob Ferriero
>            Priority: Trivial
> Often times airflow operators (derived from BaseOperator) kick-off a long running tasks
and then waits / polls, blocking a worker slot until the long running task completes. This
can be problematic in environments with many long running tasks.
> BaseSensorOperator was improved by implementing `reschedule` mode to solve the similar
issue with long running sensors blocking a worker to poll for a long time.
> This issue is to track how we could provide a primitive that would make it easy to develop
operators for long running tasks that reschedule a `poll` operation rather than blocking in
their `execute` method.

This message was sent by Atlassian Jira

View raw message