Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

<https://github.com/flyteorg/flyte/issues/3784|#3784 [Core feature] Support tasks with a`NamedTuple` output to be wrapped in `map_task`>
Issue created by <https://github.com/redartera|redartera>
*Motivation: Why do you think this is important?*

Map tasks are a convenient way to branch a task out in parallel in a node-efficient way compared to dynamic tasks.

However, `map_task` is restricted to single-input single-output tasks. There is interest in multi-input map tasks, and using a <https://github.com/DataClass|@DataClass> object is a way to get around it (as long as inputs are JSON-serializable).

For the outputs, a task producing a `NamedTuple` cannot be used with map_task, and we have to use `@dynamic` instead. This issue suggests to support tasks outputting a`NamedTuple` to be wrapped within `map_task`.

*Goal: What should the final outcome look like, ideally?*

Allow tasks outputting a `NamedTuple` to be used within `map_task`.

*Describe alternatives you've considered*

Using `@dynamic`

*Propose: Link/Inline OR Additional context*

_No response_

*Are you sure this issue hasn't been raised already?*

☑︎ Yes

*Have you read the Code of Conduct?*

☑︎ Yes
<https://github.com/flyteorg/flyte|flyteorg/flyte>