hawq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yo...@apache.org
Subject [07/50] [abbrv] incubator-hawq-docs git commit: overview - include link to config doc, add polling prop name
Date Tue, 25 Apr 2017 00:04:00 GMT
overview - include link to config doc, add polling prop name


Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/bb708621
Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/bb708621
Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/bb708621

Branch: refs/heads/master
Commit: bb7086214c9d25e7ea0cf2f07294d297f90b97e7
Parents: f9f7d15
Author: Lisa Owen <lowen@pivotal.io>
Authored: Fri Mar 31 13:26:11 2017 -0700
Committer: Lisa Owen <lowen@pivotal.io>
Committed: Fri Mar 31 13:26:11 2017 -0700

----------------------------------------------------------------------
 markdown/ranger/ranger-overview.html.md.erb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/bb708621/markdown/ranger/ranger-overview.html.md.erb
----------------------------------------------------------------------
diff --git a/markdown/ranger/ranger-overview.html.md.erb b/markdown/ranger/ranger-overview.html.md.erb
index 55ef691..ef223e8 100644
--- a/markdown/ranger/ranger-overview.html.md.erb
+++ b/markdown/ranger/ranger-overview.html.md.erb
@@ -27,11 +27,11 @@ HAWQ supports using Apache Ranger for authorizing user access to HAWQ
resources.
 ## <a id="arch"></a>Policy Management Architecture
 Each HAWQ installation includes a Ranger plug-in service to support Ranger Policy management.
The Ranger plug-in service implements the Ranger REST API to bridge all requests between the
Ranger Policy Manager and a HAWQ instance. 
 
-HAWQ also provides a JAR library that enables the Ranger Policy Manager to lookup HAWQ metadata
(the names of databases, schemas, tables, and so forth) to populate the user interface and
assist in creating new policies. This JAR uses a JDBC connection to HAWQ, and requires a one-time
registration with the Ranger Policy Manager. 
+HAWQ also provides a JAR library that enables the Ranger Policy Manager to lookup HAWQ metadata
(the names of databases, schemas, tables, and so forth) to populate the user interface and
assist in creating new policies. This JAR uses a JDBC connection to HAWQ, and requires a one-time
registration with the Ranger Policy Manager. See [Configuring HAWQ to use Ranger Policy Management](ranger-integration-config.html).
 
-A single configuration parameter, `hawq_acl_type` determines whether HAWQ defers all policy
management to Ranger via the plug-in service, or whether HAWQ handles authorization natively
using catalog tables. By default, HAWQ uses SQL commands to create all access policies, and
the policy information is stored in catalog tables.  When you enable Ranger integration for
policy management, any authorization policies that you have configured in HAWQ using SQL no
longer apply to your installation; you must create new policies using the Ranger interface.
See [Creating HAWQ Authorization Policies in Ranger](ranger-policy-creation.html)
+A single configuration parameter, `hawq_acl_type` determines whether HAWQ defers all policy
management to Ranger via the plug-in service, or whether HAWQ handles authorization natively
using catalog tables. By default, HAWQ uses SQL commands to create all access policies, and
the policy information is stored in catalog tables.  When you enable Ranger integration for
policy management, any authorization policies that you have configured in HAWQ using SQL no
longer apply to your installation; you must create new policies using the Ranger interface.
See [Creating HAWQ Authorization Policies in Ranger](ranger-policy-creation.html).
 
-The Ranger plug-in service caches Ranger policies locally on each HAWQ node to avoid unnecessary
round trips between the HAWQ node and the Ranger Policy Manager server. You can use the configuration
parameter `that` to control how frequently the plug-in service contacts the Ranger Policy
Manager to refresh cached policies. See [Changing the Frequency of Policy Caching](ranger-integration-config.html#caching).
+The Ranger plug-in service caches Ranger policies locally on each HAWQ node to avoid unnecessary
round trips between the HAWQ node and the Ranger Policy Manager server. You can use the configuration
property `ranger.plugin.hawq.policy.pollIntervalMs` to control how frequently the plug-in
service contacts the Ranger Policy Manager to refresh cached policies. See [Changing the Frequency
of Policy Caching](ranger-integration-config.html#caching).
 
 ## <a id="limitations"></a>Limitations of Ranger Policy Management
 Neither Kerberos authentication nor SSL encryption is supported between a HAWQ node and the
Ranger plug-in service, or between the plug-in service and the Ranger Policy Manager.


Mime
View raw message