Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-1234] Update documentation configuration to reflect new hadoop2 default profile. #295

Closed
wants to merge 1 commit into from

Conversation

rmetzger
Copy link
Contributor

Note: This is the same commit as this one for the "release-0.8" branch: rmetzger@1e9420b

…2 default profile.

Note: This is the same commit as this one for the "release-0.8" branch: 1e9420b
@StephanEwen
Copy link
Contributor

Great. Let's add this to master and to release-0.8.

@@ -90,16 +90,16 @@ Execute the following commands:
curl https://raw.githubusercontent.com/apache/incubator-flink/master/flink-quickstart/quickstart.sh | bash
~~~

3. Set the the version of Flink to `{{site.FLINK_VERSION_HADOOP_2_STABLE}}` in the `pom.xml` file. The quickstart.sh script sets the version to the `hadoop1` version of Flink. Since the `microsoft-hadoop-azure` has been written for Hadoop 2.2 (mapreduce-API) version, we need to use the appropriate Flink version.
3. Set the the version of Flink to `{{site.FLINK_VERSION_HADOOP2_STABLE}}` in the `pom.xml` file. The quickstart.sh script sets the version to the `hadoop1` version of Flink. Since the `microsoft-hadoop-azure` has been written for Hadoop 2.2 (mapreduce-API) version, we need to use the appropriate Flink version.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still true? Does the quickstart.sh set the version to hadoop1 of Flink? If yes, why?

@uce
Copy link
Contributor

uce commented Jan 12, 2015

Thanks. +1 to merge after 0.8.0 is out.

@uce
Copy link
Contributor

uce commented Jan 12, 2015

Just as a reminder: we have to check for the old variable names before merging. #292 for examples updates the docs as well and uses the old variable names.

@rmetzger
Copy link
Contributor Author

I'll merge #292 first and then fix the variable names as part of this pr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants