[
https://issues.apache.org/jira/browse/FLINK-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101779#comment-16101779
]
Greg Hogan commented on FLINK-6909:
-----------------------------------
Hi [~mdkamaruzzaman], judging by the extensive tooling provided at the Lombok
website it looks like `TypeExtractor` would need to be modified to parse and
interpret the Lombok annotations. The cost to do so is added complexity in a
vital and already very complex portion of the core Flink architecture. The
benefit of automatic POJO is available in any IDE and also using Lombok via the
provided [delombok tool|https://projectlombok.org/features/delombok] which
converts annotated classes to POJOs and can be integrated into one's project
builds.
> Flink should support Lombok POJO
> --------------------------------
>
> Key: FLINK-6909
> URL: https://issues.apache.org/jira/browse/FLINK-6909
> Project: Flink
> Issue Type: Wish
> Components: Type Serialization System
> Reporter: Md Kamaruzzaman
> Priority: Minor
> Fix For: 1.2.1
>
>
> Project lombok helps greatly to reduce boilerplate Java Code.
> It seems that Flink does not accept a lombok POJO as a valid pojo.
> e.g. Here is a POJO defined with lombok:
> @Getter
> @Setter
> @NoArgsConstructor
> public class SimplePojo
> Using this Pojo class to read from CSV file throws this exception:
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.flink.api.java.typeutils.GenericTypeInfo cannot be cast to
> org.apache.flink.api.java.typeutils.PojoTypeInfo
> It would be great if flink supports lombok POJO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
