flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tzu-Li (Gordon) Tai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3852) Use a StreamExecutionEnvironment in the quickstart job skeleton
Date Wed, 11 May 2016 02:29:13 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279400#comment-15279400

Tzu-Li (Gordon) Tai commented on FLINK-3852:

Hi Mark,

I think replacing the StreamingJob skeleton as the main class doesn't match what this issue
is aiming for.

I see 2 approaches here:

1. BatchJob skeleton and StreamingJob skeleton within same quickstart module ( i.e. Batch
& Streaming Java / Batch & Streaming Scala)
In the javadoc within each skeleton, you can guide the user to use {noformat}./bin/flink run
-c <either BatchJob or StreamingJob> <quickstart jar> {noformat} as instructed
in https://ci.apache.org/projects/flink/flink-docs-release-1.0/apis/cli.html.
Instead of defining a mainClass in the shade plugin, comment the transformers for the mainClass
setting out with instructions that the user can add this back if they decide to simply use
{noformat}./bin/flink run <quickstart jar>{noformat} with either one of the skeletons
as main class entry point.

2. Have 4 separate quickstarts, i.e. Batch Java / Batch Scala / Streaming Java / Streaming
I like the first approach better, since it also has a natural way of letting the user know
that there are different submission options for a packaged Flink jar job.

> Use a StreamExecutionEnvironment in the quickstart job skeleton
> ---------------------------------------------------------------
>                 Key: FLINK-3852
>                 URL: https://issues.apache.org/jira/browse/FLINK-3852
>             Project: Flink
>          Issue Type: Task
>          Components: Quickstarts
>            Reporter: Robert Metzger
>              Labels: starter
> The Job skeleton created by the maven archetype "quickstart" is still setting up an ExecutionEnvironment,
not a StreamExecutionEnvironment.
> These days, most users are using Flink for streaming, so we should reflect that in the
quickstart as well.

This message was sent by Atlassian JIRA

View raw message