dstandish commented on code in PR #22867: URL: https://github.com/apache/airflow/pull/22867#discussion_r846483452
########## docs/apache-airflow/concepts/dynamic-task-mapping.rst: ########## @@ -0,0 +1,256 @@ + .. 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. + +==================== +Dynamic Task Mapping +==================== + +Dynamic Task Mapping allows a way for a workflow to create a number of tasks at runtime based upon current data, rather than the DAG author having to know in advance how many tasks would be needed. Review Comment: yeah i know that thought occured to me too but sometimes being precise can get clunky ... can think of it as a metaphor in a sense you could say that the dag is creating it because, it kindof is, that's the dynamic part of it... the pipeline is dynamic and it creates its own tasks, and whether it is scheduler or the "DAG" is sort of implementation detail. but yeah prob there's a way to make it both precise _and_ elegant 🤷 -- 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]
