[7/7] drill git commit: remove upgrading bullet

[ts...@apache.org]

remove upgrading bullet


Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/d6c7d97a
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/d6c7d97a
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/d6c7d97a

Branch: refs/heads/gh-pages
Commit: d6c7d97a3e92e973f018a5e9f8201644b00a84b9
Parents: 707190d
Author: Kristine Hahn <kh...@maprtech.com>
Authored: Tue May 5 11:27:39 2015 -0700
Committer: Kristine Hahn <kh...@maprtech.com>
Committed: Tue May 5 11:27:39 2015 -0700

----------------------------------------------------------------------
 _docs/rn/070-0.9.0-rn.md | 1 -
 1 file changed, 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/d6c7d97a/_docs/rn/070-0.9.0-rn.md
----------------------------------------------------------------------
diff --git a/_docs/rn/070-0.9.0-rn.md b/_docs/rn/070-0.9.0-rn.md
index 761269d..edae5c8 100755
--- a/_docs/rn/070-0.9.0-rn.md
+++ b/_docs/rn/070-0.9.0-rn.md
@@ -4,7 +4,6 @@ parent: "Release Notes"
 ---
 It has been about a month since the release of Drill 0.8, which included [more than 240 improvements]({{ site.baseurl }}/blog/drill-0.8-released/). Today we're happy to announce the availability of Drill 0.9, providing additional enhancements and bug fixes. In fact, this release includes [200 resolved JIRAs](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820&version=12328813). Some of the noteworthy features in Drill 0.9 are:
 
-* **Upgrading** Remove the old version before upgrading, as described in "[Upgrading to the Latest Version of Apache Drill](http://doc.mapr.com/display/MapR/Upgrading+to+the+Latest+Version+of+Apache+Drill)."
 * **Authentication** ([DRILL-2674](https://issues.apache.org/jira/browse/DRILL-2674)). Drill now supports username/password authentication through the Java and C++ clients, as well as JDBC and ODBC. On the server-side, Drill leverages Linux PAM to securely validate the credentials. Users can choose to use an external user directory such as Active Directory or LDAP. To enable authentication, set the `security.user.auth` option in `drill-override.conf`.
 * **Impersonation** ([DRILL-2363](https://issues.apache.org/jira/browse/DRILL-2363)). Queries now execute and access resources using the identity of the user who submitted the query. Previously, all queries would run as the same user (eg, `drill`). With the new impersonation capability, the query will fail if the submitting user does not have permission to read the requested file(s) in the distributed file system. To enable impersonation, set the `drill.exec.impersonation` option in `drill-override.conf`.
 * **Ownership chaining**. Drill now allows views with different owners to be chained. This represents a very flexible access control solution. For example, an administrator with access to raw, sensitive data could create a view called `masked` which would expose only a subset of the data to other users. The administrator would enable users to read the `masked` view but not the raw data. Note that Drill provides an option `max_chained_user_hops` that specifies how many ownership changed are allowed in a chain, thereby providing administrators (or data stewards) more control over sharing of data.