mik-laj opened a new pull request #7521: [AIRFLOW-6897] Simplify 
DagFileProcessorManager
URL: https://github.com/apache/airflow/pull/7521
 
 
   **Extract start_new_processes and prepare_file_path_queue**
   These functions are independent of each other, but as separate methods, they 
are easier to understand. A good methods name is the best documentation.
   I also changed to `_heartbeat_count` to `_no_run` because it better 
describes the role. This variable can increase without affecting heartbeat when 
DagFileProcessorManager is running in asynchronous mode.q
   **Move emit_metrics call**
   It is not related to generating file_path_queue, so it should be called by 
the caller.
   **Inline heartbeat method**
   This function does not make sense, because every time a full loop is 
performed.  It only hides the logic and makes it difficult to understand the 
code.
   **Move _kill_timed_out_processors to loop**
   It is not related to generating the collect_results method, so it should be 
called by the caller.
   
   Now I have the impression that the sequence of operations is much more easy 
to understand because it is only found in the start method.
   
   In this PR I do not want to change the sequence of operations. It is only 
refactoring without functional changes.
   
   ---
   Issue link: WILL BE INSERTED BY 
[boring-cyborg](https://github.com/kaxil/boring-cyborg)
   
   Make sure to mark the boxes below before creating PR: [x]
   
   - [X] Description above provides context of the change
   - [X] Commit message/PR title starts with `[AIRFLOW-NNNN]`. AIRFLOW-NNNN = 
JIRA ID<sup>*</sup>
   - [X] Unit tests coverage for changes (not needed for documentation changes)
   - [X] Commits follow "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)"
   - [X] Relevant documentation is updated including usage instructions.
   - [X] I will engage committers as explained in [Contribution Workflow 
Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
   
   <sup>*</sup> For document-only changes commit message can start with 
`[AIRFLOW-XXXX]`.
   
   ---
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   Read the [Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#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:
[email protected]


With regards,
Apache Git Services

Reply via email to