[ https://issues.apache.org/jira/browse/FLINK-12004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Wysakowicz closed FLINK-12004. ------------------------------------ Fix Version/s: 1.11.0 Resolution: Implemented Implemented in fb12bcfaa82e10fb85e5f4c45e5d9ab503a3d891 > Consider about POJO using method chaining when extract TypeInformation > ---------------------------------------------------------------------- > > Key: FLINK-12004 > URL: https://issues.apache.org/jira/browse/FLINK-12004 > Project: Flink > Issue Type: Improvement > Components: API / DataStream, API / Type Serialization System > Affects Versions: 1.7.2 > Reporter: jiawei chen > Assignee: jiawei chen > Priority: Major > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > I have a POJO class using method chaining such as : > {code:java} > public static class CustomChainingPojoType { > private String myField1; > private int myField2; > public CustomChainingPojoType() { > } > public CustomChainingPojoType setMyField1(String myField1) { > this.myField1 = myField1; > return this; > } > public CustomChainingPojoType setMyField2(int myField2) { > this.myField2 = myField2; > return this; > } > public String getMyField1() { > return myField1; > } > public int getMyField2() { > return myField2; > } > }{code} > > It can not be analyze as POJO in TypeExtractor because the set method return > type is not Void, How about add a condition that return type can be class > self. > -- This message was sent by Atlassian Jira (v8.3.4#803005)