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

   This PR restructures the Mapped Operator and Mapped Task Group code to live 
in
   the Task SDK at definition time.
   
   The big thing this change _does not do_ is make it possible to execute mapped
   tasks via the Task Execution API server etc -- that is up next.
   
   There were some un-avoidable changes to the scheduler/expansion part of 
mapped
   tasks here. Of note:
   
   `BaseOperator.get_mapped_ti_count` has moved from an instance method on
   BaseOperator to be a class method. The reason for this was that with the move
   of more and more of the "definition time" code into the TaskSDK BaseOperator
   and AbstractOperator it is no longer possible to add DB-accessing code to a
   base class and have it apply to the subclasses. (i.e.
   `airflow.models.abstractoperator.AbstractOperator` is now _not always_ in the
   MRO for tasks. Eventually that class will be deleted, but not yet)
   
   On a similar vein XComArg's `get_task_map_length` is also moved to a single
   dispatch class method on the TaskMap model since now the definition time
   objects live in the TaskSDK, and there is no realistic way to get a per-type
   subclass with DB logic (i.e. it's very complex to end up with a
   PlainDBXComArg, a MapDBXComArg, etc. that we can attach the method too)
   
   For those who aren't aware, singledispatch (and singledispatchmethod) are a
   part of the standard library when the type of the first argument is used to
   determine which implementation to call. If you are familiar with C++ or Java
   this is very similar to method overloading, the one caveat is that it _only_
   examines the type of the first argument, not the full signature.
   
   <!--
    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