GitHub user rawkintrevo opened a pull request:

    https://github.com/apache/zeppelin/pull/1772

    [ZEPPELIN-1798][DOCS] Update docs with benv instead of env in Flink e…

    ### What is this PR for?
    
    Several Flink examples reference `env` instead of `benv` which was changed 
per [ZEPPELIN-1461](https://github.com/apache/zeppelin/pull/1409)
    
    Also update 
[http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/quickstart/install_with_flink_and_spark_cluster.html]
 to reference updated Flink Version
    
    ### What type of PR is it?
    Documentation
    
    ### Todos
    * [x] - Update  
https://zeppelin.apache.org/docs/0.6.2/interpreter/flink.html
    * [x] - Update 
http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/quickstart/install_with_flink_and_spark_cluster.html
    
    ### What is the Jira issue?
    [ZEPPELIN-1798](https://issues.apache.org/jira/browse/ZEPPELIN-1798)
    
    ### How should this be tested?
    No tests
    
    ### Screenshots (if appropriate)
    n/a
    ### Questions:
    * Does the licenses files need update?
    No
    * Is there breaking changes for older versions?
    No
    * Does this needs documentation?
    This IS documentation that should have been in earlier PR


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rawkintrevo/incubator-zeppelin ZEPPELIN-1798

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1772.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1772
    
----
commit 2ac80904fc84397e757153910bbae1c653fbf17b
Author: rawkintrevo <trevor.d.gr...@gmail.com>
Date:   2016-12-15T17:15:02Z

    [ZEPPELIN-1798][DOCS] Update docs with benv instead of env in Flink 
examples and bump versions cited

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to