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-6395) [AIP-28] Add AsyncExecutor option
Date Tue, 31 Dec 2019 23:59:00 GMT


ASF GitHub Bot commented on AIRFLOW-6395:

dazza-codes commented on pull request #6984: [WIP][AIRFLOW-6395] Add an asyncio compatible
dask executor [AIP-28]
   ## WIP status
   - this is a first sketch that requires a lot more work to evaluate
   - this is motivated by [AIP-28](
   - [ ] Description above provides context of the change
   - [ ] Commit message contains [\[AIRFLOW-XXXX\]](
or `[AIRFLOW-XXXX]` for document-only changes
   - [ ] Unit tests coverage for changes (not needed for documentation changes)
   - [ ] Commits follow "[How to write a good git commit message]("
   - [ ] Relevant documentation is updated including usage instructions.
   - [ ] I will engage committers as explained in [Contribution Workflow Example](
   In case of fundamental code change, Airflow Improvement Proposal ([AIP](
is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](
   In case of backwards incompatible changes please leave a note in [](
   Read the [Pull Request Guidelines](
for more information.
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:

> [AIP-28] Add AsyncExecutor option
> ---------------------------------
>                 Key: AIRFLOW-6395
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: core, executors, operators, scheduler
>    Affects Versions: 1.10.7
>            Reporter: Darren Weber
>            Priority: Minor
> Add an AsyncExecutor that is similar to LocalExecutor but designed to optimize for high
concurrency with async behavior for any blocking operations.  It requires an async ecosystem
and general flags for async operations on hooks, operators, and sensors.
> Further details can be developed in an AIP and this description can be updated with links
to relevant resources and discussion(s).
> - []

This message was sent by Atlassian Jira

View raw message