GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1498
[DOCS] Fix dead link in docs/datasource_authorization.md
### What is this PR for?
A link for `the community interpreters` in
[here](http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/security/datasource_authorization.html#please-note)
is pointing to
`../manual/interpreterinstallation.md#available-community-managed-interpreters`
now. It should be
`../manual/interpreterinstallation.html#available-community-managed-interpreters`.
And recently added interpreter, `Apache Beam` is also added to [Available
community managed interpreters
list](http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/manual/interpreterinstallation.html#available-community-managed-interpreters).
### What type of PR is it?
Bug Fix & Documenation
### What is the Jira issue?
no Jira issue
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AhyoungRyu/zeppelin fix/deadlink
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1498.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 #1498
----
commit 0260d30594c6733e48f4571f89a47b51aefb5a02
Author: AhyoungRyu <[email protected]>
Date: 2016-10-09T01:46:43Z
Fix deadlink in datasource_authorization.md
commit acf25a7d13c6134bb98cdb3f67e9565085780c8a
Author: AhyoungRyu <[email protected]>
Date: 2016-10-09T01:47:07Z
Add beam interpreter to community interpreter list
commit 04fd8fc40d9cf3420b51286f370f5d829f9f5438
Author: AhyoungRyu <[email protected]>
Date: 2016-10-09T01:55:36Z
community interpreters -> community managed interpreters
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
