Hi all, We need a better name than partition for Dynamic Task Partitioning.
The main issue is that partition already strongly suggests asset/data partitions in Airflow, so using the same word here creates avoidable confusion for users and contributors. We’d like a term that is clear, intuitive, and doesn’t overlap with existing Airflow concepts. Some alternatives raised so far during the devcall: * batch (e.g. Dynamic Task Batching) * chunk (e.g. Dynamic Task Chunking) * slice (bit confusing but chose to still mention it anway) * shard * segment My current lean is towards chunk and batch. It feels familiar, readable in both code and docs, and avoids the existing partition/data-partition association. I’d love feedback on: * which term feels most natural * which term is least ambiguous * or whether there’s a better option we haven’t considered? One note: map was mentioned as well, but that seems too close to existing task.map() terminology. Please share thoughts, especially if you have concerns about any of the options above or a stronger suggestion for the long-term name. Naming is indeed hard 🙂 Kind regards, David
