[
https://issues.apache.org/jira/browse/FLINK-20115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger updated FLINK-20115:
-----------------------------------
Description:
Test the following new features:
- https://issues.apache.org/jira/browse/FLINK-19316
- https://issues.apache.org/jira/browse/FLINK-19268
- https://issues.apache.org/jira/browse/FLINK-19758
The three issues can really only be tested in combination. FLINK-19316 is done
but missing documentation.
Write an example that uses a (new) FileSource, a (new) FileSink, some random
transformations
Run the example in BATCH mode
How ergonomic is the API/configuration?
Are there any weird log messages/exceptions in the JM/TM logs
Maybe try sth that doesn't work on BATCH execution, such as iterations/feedback
edges.
----
[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, and once you are finished, please write a short summary of
all things you have tested.
was:
Test the following new features:
- https://issues.apache.org/jira/browse/FLINK-19316
- https://issues.apache.org/jira/browse/FLINK-19268
- https://issues.apache.org/jira/browse/FLINK-19758
The three issues can really only be tested in combination. FLINK-19316 is done
but missing documentation.
Write an example that uses a (new) FileSource, a (new) FileSink, some random
transformations
Run the example in BATCH mode
How ergonomic is the API/configuration?
Are there any weird log messages/exceptions in the JM/TM logs
Maybe try sth that doesn't work on BATCH execution, such as iterations/feedback
edges.
> Test Batch execution for the DataStream API
> --------------------------------------------
>
> Key: FLINK-20115
> URL: https://issues.apache.org/jira/browse/FLINK-20115
> Project: Flink
> Issue Type: Sub-task
> Components: API / DataStream
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Assignee: Till Rohrmann
> Priority: Critical
> Fix For: 1.12.0
>
>
> Test the following new features:
> - https://issues.apache.org/jira/browse/FLINK-19316
> - https://issues.apache.org/jira/browse/FLINK-19268
> - https://issues.apache.org/jira/browse/FLINK-19758
> The three issues can really only be tested in combination. FLINK-19316 is
> done but missing documentation.
> Write an example that uses a (new) FileSource, a (new) FileSink, some random
> transformations
> Run the example in BATCH mode
> How ergonomic is the API/configuration?
> Are there any weird log messages/exceptions in the JM/TM logs
> Maybe try sth that doesn't work on BATCH execution, such as
> iterations/feedback edges.
> ----
> [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, and once you are finished, please write a short summary
> of all things you have tested.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
