yes, if it is present in the core flink files it must work just as any
tuple in flink.
removing is not an option though; but moving is. The Python API uses it
(that's the reason Tuple0 was added in the first place).
On 01.08.2015 13:04, Matthias J. Sax wrote:
I see.
I think that it might be useful to have Tuple0, because in rare cases,
you only want to "notify" a downstream operators (taking about
streaming) that something happened but there is no actual data to be
processed. Furthermore, if Flink cannot deal with Tuple0 it should be
removed completely for consistency IMHO.
I will open a JIRA for it.
-Matthias
On 07/31/2015 10:44 PM, Chesnay Schepler wrote:
also, I'm not sure if I ever sent a Tuple0 through a program, it could
be that the system freaks out.
On 31.07.2015 22:40, Chesnay Schepler wrote:
there's no specific reason. it was added fairly recently by me (mid of
april), and you're most likely the second person to use it.
i didn't integrate into all our tuple related stuff because, well, i
never thought anyone would actually need it, so i saved myself the
trouble.
Hi,
is there any specific reason, why Tuple.getTupleClass(int arity) does
not support arity zero? There is a class Tuple0, but it cannot be
generator by Tuple.getTupleClass(...). Is it a missing feature (I would
like to have it).
-Matthias
