[
https://issues.apache.org/jira/browse/FLINK-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266219#comment-14266219
]
Stephan Ewen commented on FLINK-1360:
-------------------------------------
Ah, I see. That problem is different. The types "Void" and "Long" are erased by
the java compiler.
When you extract types from candidates (not from function implementations or
so), the system needs an instance of the type. Try using :
{code}
env.fromCollection(Arrays.asList(new Tuple2<Void,Long>(null, 1L)),
TypeInfoParser.parse("Tuple2<Void,Long>"));
{code}
> Automatic type extraction for Void is missing
> ---------------------------------------------
>
> Key: FLINK-1360
> URL: https://issues.apache.org/jira/browse/FLINK-1360
> Project: Flink
> Issue Type: Bug
> Reporter: Felix Neutatz
> Priority: Minor
>
> DataSet<Tuple2<Void,Long>> data = env.fromElements(new
> Tuple2<Void,Long>(null, 1L));
> data.print();
> throws the following exception:
> Exception in thread "main"
> org.apache.flink.api.common.functions.InvalidTypesException: Automatic type
> extraction is not possible on candidates with null values. Please specify the
> types directly.
> at
> org.apache.flink.api.java.typeutils.TypeExtractor.privateGetForObject(TypeExtractor.java:1174)
> at
> org.apache.flink.api.java.typeutils.TypeExtractor.getForObject(TypeExtractor.java:1152)
> at
> org.apache.flink.api.java.ExecutionEnvironment.fromElements(ExecutionEnvironment.java:540)
> at
> org.apache.flink.hadoopcompatibility.mapreduce.example.ParquetOutput.main(ParquetOutput.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
