You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Mark Reddy (JIRA)" <ji...@apache.org> on 2016/05/10 22:58:12 UTC

[jira] [Commented] (FLINK-3852) Use a StreamExecutionEnvironment in the quickstart job skeleton

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

Mark Reddy commented on FLINK-3852:
-----------------------------------

I can take this. 

One quick question after taking an initial look. The shade plugin specifies a mainClass, if we create a BatchJob and a StreamingJob skeleton would I be correct in saying that the main class for the packaged jar would be StreamingJob?

If so, for clarity would it be best to remove the following javadoc from the BatchJob and only have it in the StreamingJob
{noformat}
 * You can also generate a .jar file that you can submit on your Flink
 * cluster.
 * Just type
 * 		mvn clean package
 * in the projects root directory.
 * You will find the jar in
 * 		target/flink-quickstart-0.1-SNAPSHOT-Sample.jar
{noformat}

> 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
(v6.3.4#6332)