[
https://issues.apache.org/jira/browse/STREAMS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171580#comment-17171580
]
Steve Blackmon commented on STREAMS-671:
----------------------------------------
this is kind of a doozy, it seems flink can not handle POJO DataStreams that
use joda DateTimes in any of the objects without losing them somewhere along
the way, and also warns about POJO containing additionalProperties maps like
are generated by streams-plugin-pojo.
I researched ways of registering the joda dates to make them work but none
fixed the problem. so my proposed solution to this is to switch the twitter
pojos to use java.util.Date which flink handles flawlessly. and to build them
without additionalProperties maps, which are not needed when the schema is
fully defined as it is for this mature module.
> flink twitter examples output files do not contain date-time fields
> -------------------------------------------------------------------
>
> Key: STREAMS-671
> URL: https://issues.apache.org/jira/browse/STREAMS-671
> Project: Streams
> Issue Type: Bug
> Reporter: Steve Blackmon
> Assignee: Steve Blackmon
> Priority: Major
>
> flink twitter examples output files do not contain date-time fields
> this is likely a by-product of Flink's default treatment of JodaTime objects
> in pojos
> add more tests that check pipeline output files and fix the date time issue
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
