[
https://issues.apache.org/jira/browse/FLINK-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526404#comment-14526404
]
ASF GitHub Bot commented on FLINK-1595:
---------------------------------------
Github user mbalassi commented on the pull request:
https://github.com/apache/flink/pull/520#issuecomment-98628873
Hey,
Sorry for not attending to this for a long time. It needed a rebase for the
API of the chaining. Now that I have updated that the test throws the following
NPE:
Caused by: java.lang.NullPointerException
at
org.apache.flink.streaming.api.complex.ComplexIntegrationTest$MyTimestamp.getTimestamp(ComplexIntegrationTest.java:659)
at
org.apache.flink.streaming.api.complex.ComplexIntegrationTest$MyTimestamp.getTimestamp(ComplexIntegrationTest.java:654)
at
org.apache.flink.streaming.api.windowing.helper.TimestampWrapper.getTimestamp(TimestampWrapper.java:34)
at
org.apache.flink.streaming.api.windowing.windowbuffer.SlidingTimePreReducer.afterEmit(SlidingTimePreReducer.java:71)
at
org.apache.flink.streaming.api.windowing.windowbuffer.SlidingPreReducer.emitWindow(SlidingPreReducer.java:59)
... 7 more
It would be nice if we could separate the individual tests, so it is easier
to track an exception like that. Maybe a solution similar to
`MiltipleProgramsTestBase` for streaming would do the trick.
@szape, could you please do an update with these, then I'd merge it asap so
that it does not get outdated again. Thanks.
> Add a complex integration test for Streaming API
> ------------------------------------------------
>
> Key: FLINK-1595
> URL: https://issues.apache.org/jira/browse/FLINK-1595
> Project: Flink
> Issue Type: Task
> Components: Streaming
> Reporter: Gyula Fora
> Assignee: Péter Szabó
> Labels: Starter
>
> The streaming tests currently lack a sophisticated integration test that
> would test many api features at once.
> This should include different merging, partitioning, grouping, aggregation
> types, as well as windowing and connected operators.
> The results should be tested for correctness.
> A test like this would help identifying bugs that are hard to detect by
> unit-tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
