[1st version] Enable tuple and NamedTuple

[Mecoli1219]

Tracking issue

• [Core feature] Tuple & NamedTuple Support flyte#5908
• flytekit - support NamedTuple as input type flyte#1337
• [BUG] dict type converts int values to float flyte#3158
• [BUG] Unable to compile task with (NamedTuple, str) as the output flyte#4358

Why are the changes needed?

Check out the RFC

What changes were proposed in this pull request?

• Run local test
• Run remote test
  Currently, the flyte Console doesn't support tuple type on UI, we will open another PR to address that.

How was this patch tested?

NamedTuple

import typing
from typing import NamedTuple

class TupleClass(NamedTuple):
    keyi: int
    keys: str

@task(container_image=image)
def nt_t1_1(a1: TupleClass, b1: str) -> typing.Tuple[TupleClass, str]:
    return TupleClass(a1[0], a1[1]), b1

@task(container_image=image)
def nt_t2_1(a2: TupleClass, b2: str) -> typing.Tuple[TupleClass, str]:
    return TupleClass(a2[0], b2), a2[1]

@workflow
def nt_wf1_1(b: str) -> typing.Tuple[TupleClass, str]:
    t, s = nt_t1_1(a1=TupleClass(12345, "NamedTupleData"), b1=b)
    return nt_t2_1(a2=TupleClass(t[0], t[1]), b2=s)

@workflow
def nt_wf2_1(b: str) -> typing.Tuple[TupleClass, str]:
    (at, bt), s = nt_t1_1(a1=TupleClass(12345, "NamedTupleData"), b1=b)
    return nt_t2_1(a2=TupleClass(at, bt), b2=s)

Tuple

@task
def t_t1(
    a1: typing.Tuple[int, str], b1: str
) -> typing.Tuple[typing.Tuple[int, str], str]:
    return (a1[0], a1[1]), b1

@task
def t_t2(
    a2: typing.Tuple[str, int], b2: str
) -> typing.Tuple[typing.Tuple[int, str], str]:
    return (a2[1], b2), a2[0]

@workflow
def t_wf1(b: str) -> typing.Tuple[typing.Tuple[int, str], str]:
    t, s = t_t1(a1=(54321, "tuple_data"), b1=b)
    return t_t2(a2=(t[1], t[0]), b2=s)

@workflow
def t_wf2(b: str) -> typing.Tuple[typing.Tuple[int, str], str]:
    (at, bt), s = t_t1(a1=(54321, "tuple_data"), b1=b)
    return t_t2(a2=(bt, at), b2=s)

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• [] All new and existing tests passed.
• All commits are signed-off.

The tests require IDL to be merged.

Related PRs

• RFC: [RFC] Tuple IDL flyte#5699
• IDL: [1st version] Add Tuple idl flyte#5720

Docs link

[kumare3]

woah!!!!!!!!
@Mecoli1219 you rock!

[pingsutw]

duplicated?

Suggested change

	This function is used to convert an output object to a tuple. This is used to convert the output object to a tuple
	This is used to convert the output object to a tuple

[pingsutw]

It would be great to have a unit test for it.

[pingsutw]

Do you think we need a separate transformer for NamedTuple? NamedTupleTransformer

[Mecoli1219]

I have discussed that in Section 6 Alternatives of this RFC: flyteorg/flyte#5699

In Flytekit, we can separate the NamedTuple and Tuple into two different transformers, and this will make the code more readable and maintainable. However, the main problem is that the NamedTuple is not a type in Python, it is a function that returns a type. Separating them will make the registries of the transformers more complex and harder to maintain.

[Mecoli1219]

Also, I have tried it before (maybe you can see that in some commits in this Pull Request), and it is really hard to maintain that.