ashb opened a new pull request, #44427:
URL: https://github.com/apache/airflow/pull/44427

   This also lays the groundwork for a more general purpose "workload" execution
   system, make a single interface for executors to run tasks and callbacks.
   
   Also in this PR we set up the supervise function to send Task logs to a file,
   and handle the task log template rendering in the scheduler before queueing
   the workload.
   
   Additionally we don't pass the activity directly to `supervise()` but instead
   the properties/fields of it to reduce the coupling between SDK and Executor.
   (More separation will appear in PRs over the next few weeks.)
   
   The big change of note here is that rather than sending an airflow command
   line to execute (`["airflow", "tasks", "run", ...]`) and going back in via 
the
   CLI parser we go directly to a special purpose function. Much simpler.
   
   It doesn't remove any of the old behaviour (CeleryExecutor still uses
   LocalTaskJob via the CLI parser etc.), nor does anything currently send
   callback requests via this new workload mechanism.
   
   The `airflow.executors.workloads` module currently needs to be shared between
   the Scheduler (or more specifically the Executor) and the "worker" side of
   things. In the future these will be separate python dists and this module 
will
   need to live somewhere else.
   
   Right now we check the if `executor.queue_workload` is different from the
   BaseExecutor version (which just raises an error right now) to see which
   executors support this new version. That check will be removed as soon as all
   the in-tree executors have been migrated.
   
   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to