[
https://issues.apache.org/jira/browse/FLINK-10050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620450#comment-16620450
]
ASF GitHub Bot commented on FLINK-10050:
----------------------------------------
EugeneYushin commented on issue #6646: [FLINK-10050] Support allowedLateness in
CoGroupedStreams
URL: https://github.com/apache/flink/pull/6646#issuecomment-422754323
I see one build from Travis has been finished with error:
```
10:15:13.087 [ERROR] Failed to execute goal on project
flink-storm-examples_2.11: Could not resolve dependencies for project
org.apache.flink:flink-storm-examples_2.11:jar:1.7-SNAPSHOT: Could not transfer
artifact org.apache.storm:storm-starter:jar:1.0.0 from/to central
(http://repo.maven.apache.org/maven2): GET request of:
org/apache/storm/storm-starter/1.0.0/storm-starter-1.0.0.jar from central
failed: Connection reset -> [Help 1]
```
Looks like it's not related to proposed changes.
What is the best way to deal with such kind of failures during CI?
Is there any way to rerun PR?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Support 'allowedLateness' in CoGroupedStreams
> ---------------------------------------------
>
> Key: FLINK-10050
> URL: https://issues.apache.org/jira/browse/FLINK-10050
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 1.5.1, 1.6.0
> Reporter: eugen yushin
> Priority: Major
> Labels: pull-request-available, ready-to-commit, windows
>
> WindowedStream has a support of 'allowedLateness' feature, while
> CoGroupedStreams are not. At the mean time, WindowedStream is an inner part
> of CoGroupedStreams and all main functionality (like evictor/trigger/...) is
> simply delegated to WindowedStream.
> There's no chance to operate with late arriving data from previous steps in
> cogroups (and joins). Consider the following flow:
> a. read data from source1 -> aggregate data with allowed lateness
> b. read data from source2 -> aggregate data with allowed lateness
> c. cogroup/join streams a and b, and compare aggregated values
> Step c doesn't accept any late data from steps a/b due to lack of
> `allowedLateness` API call in CoGroupedStreams.java.
> Scope: add method `WithWindow.allowedLateness` to Java API
> (flink-streaming-java) and extend scala API (flink-streaming-scala).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
