[ 
https://issues.apache.org/jira/browse/AIRFLOW-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989035#comment-16989035
 ] 

ASF GitHub Bot commented on AIRFLOW-6181:
-----------------------------------------

nuclearpinguin commented on pull request #6740: [AIRFLOW-6181] Add 
InProcessExecutor
URL: https://github.com/apache/airflow/pull/6740
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow 
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references 
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-6181
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI 
changes:
   
   Together with guys from Databand we created a new executor that is meant to 
be used mainly for debugging and DAG development purposes. This executor 
executes single task instance at time and is able to work with SQL Lite and 
sensors. 
   
   Using this executor you can debug tour DAGs from IDE 🚀
   ![Screenshot 2019-12-05 at 18 42 
09](https://user-images.githubusercontent.com/9528307/70260382-6f676d00-1790-11ea-9c5a-44d42cabbb02.png)
   ![Screenshot 2019-12-05 at 18 54 
32](https://user-images.githubusercontent.com/9528307/70260493-b35a7200-1790-11ea-8eba-13a8dc0fac4d.png)
   
   
   ### 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](http://chris.beams.io/posts/git-commit/)":
     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 it.
     - 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 [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) 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:
[email protected]


> Add InProcessExecutor
> ---------------------
>
>                 Key: AIRFLOW-6181
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6181
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: executors
>    Affects Versions: 2.0.0, 1.10.7
>            Reporter: Tomasz Urbaszek
>            Priority: Major
>
> The InProcessExecutor is meant as a debug tool and can be used from IDE.
>  It is a single process executor that queues TaskInstances
>  and executes them by running _run_raw_task method.
> Due to it's nature the executor can be sued with SQL Lite database. When used
>  with sensors the executor will change sensor mode to reschedule to do not
>  block the execution of DAG.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to