Thanks Timo for the explanation and Wouter for reporting this. I've located two more instances of this in the Graph class and created FLINK5097. I'll ping you after I open the PR if that's OK.
-Vasia. On 18 November 2016 at 12:22, Timo Walther <twal...@apache.org> wrote: > Yes. I don't know if it solve this problem but in general if the input > type is known it should be passed for input type inference. > > Am 18/11/16 um 11:28 schrieb Vasiliki Kalavri: > > Hi Timo, > > thanks for looking into this! Are you referring to the 4th argument in [1]? > > Thanks, > -Vasia. > > [1]: https://github.com/apache/flink/blob/master/flink- > libraries/flink-gelly/src/main/java/org/apache/flink/graph/Graph.java#L506 > > On 18 November 2016 at 10:25, Timo Walther <twal...@apache.org> wrote: > >> I think I identified the problem. Input type inference can not be used >> because of missing information. >> >> @Vasia: Why is the TypeExtractor in Graph. mapVertices(mapper) called >> without information about the input type? Isn't the input of the >> MapFunction known at this point? ( vertices.getType()) >> >> Am 17/11/16 um 20:24 schrieb otherwise777: >> >> The one that's currently in my github will give you the error, >>> >>> In my other file i made a really ugly workaround by adding the element >>> in an >>> ArrayList<K> as a single item. >>> >>> >>> >>> -- >>> View this message in context: http://apache-flink-user-maili >>> ng-list-archive.2336050.n4.nabble.com/Type-of-TypeVariable-K >>> -in-class-could-not-be-determined-tp10173p10184.html >>> Sent from the Apache Flink User Mailing List archive. mailing list >>> archive at Nabble.com. >>> >> > > > -- > Freundliche Grüße / Kind Regards > > Timo Walther > > Follow me: @twalthrhttps://www.linkedin.com/in/twalthr > >
