[ 
https://issues.apache.org/jira/browse/FLINK-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712056#comment-15712056
 ] 

ASF GitHub Bot commented on FLINK-5097:
---------------------------------------

Github user twalthr commented on the issue:

    https://github.com/apache/flink/pull/2842
  
    @vasia You are right. The `TypeExtractor` doesn't support functions with 
more than 2 inputs. That has never been required so far as the runtime 
operators always have two inputs. You could open an issue for that if this 
feature makes sense.
    
    `TypeExtractor.getMapReturnTypes` has support for Java 8 lambdas and checks 
for the `ResultTypeQueryable` interface first, so I would use the more specific 
`getXXXReturnTypes` (the plural has historic reasons) method if possible and 
the generic `createTypeInfo` method otherwise. Just make sure that you don't 
set the `allowMissing` flag otherwise you might get a `MissingTypeInfo` back.


> The TypeExtractor is missing input type information in some Graph methods
> -------------------------------------------------------------------------
>
>                 Key: FLINK-5097
>                 URL: https://issues.apache.org/jira/browse/FLINK-5097
>             Project: Flink
>          Issue Type: Bug
>          Components: Gelly
>            Reporter: Vasia Kalavri
>            Assignee: Vasia Kalavri
>
> The TypeExtractor is called without information about the input type in 
> {{mapVertices}} and {{mapEdges}} although this information can be easily 
> retrieved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to