[
https://issues.apache.org/jira/browse/FLINK-20118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234505#comment-17234505
]
Stephan Ewen commented on FLINK-20118:
--------------------------------------
There is an ITCase that does that. What would the e2e test add here? I would
not add e2e tests just for the sake of it, it blows up the testing times.
What aspects are currently not covered in the ITCase?
- TM / JM failures
- Classloading
I would suggest to have one e2e test that covers the classloading for new
sources. Could be with Kafka or File (probably Kafka is better, it has more
dependencies).
Then let's add a TM / JM killing to an ITCase for the file source.
> Test New File Source API - Continuous Streaming Execution
> ---------------------------------------------------------
>
> Key: FLINK-20118
> URL: https://issues.apache.org/jira/browse/FLINK-20118
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Common
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Assignee: Andrey Zagrebin
> Priority: Critical
> Fix For: 1.12.0
>
>
> ----
> [General Information about the Flink 1.12 release
> testing|https://cwiki.apache.org/confluence/display/FLINK/1.12+Release+-+Community+Testing]
> When testing a feature, consider the following aspects:
> - Is the documentation easy to understand
> - Are the error messages, log messages, APIs etc. easy to understand
> - Is the feature working as expected under normal conditions
> - Is the feature working / failing as expected with invalid input, induced
> errors etc.
> If you find a problem during testing, please file a ticket
> (Priority=Critical; Fix Version = 1.12.0), and link it in this testing ticket.
> During the testing keep us updated on tests conducted, or please write a
> short summary of all things you have tested in the end.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
