mirror of
https://github.com/apache/impala.git
synced 2026-01-07 00:02:28 -05:00
3be0f122a5
These are refugees from doc_prototype. They can be rendered with the DITA Open Toolkit version 2.3.3 by: /tmp/dita-ot-2.3.3/bin/dita \ -i impala.ditamap \ -f html5 \ -o $(mktemp -d) \ -filter impala_html.ditaval Change-Id: I8861e99adc446f659a04463ca78c79200669484f Reviewed-on: http://gerrit.cloudera.org:8080/5014 Reviewed-by: John Russell <jrussell@cloudera.com> Tested-by: John Russell <jrussell@cloudera.com>
25 lines
940 B
XML
25 lines
940 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
|
|
<concept id="security_install">
|
|
|
|
<title>Installation Considerations for Impala Security</title>
|
|
<prolog>
|
|
<metadata>
|
|
<data name="Category" value="Security"/>
|
|
<data name="Category" value="Impala"/>
|
|
<data name="Category" value="Administrators"/>
|
|
</metadata>
|
|
</prolog>
|
|
|
|
<conbody>
|
|
|
|
<p>
|
|
Impala 1.1 comes set up with all the software and settings needed to enable security when you run the
|
|
<cmdname>impalad</cmdname> daemon with the new security-related options (<codeph>-server_name</codeph> and
|
|
<codeph>-authorization_policy_file</codeph>). You do not need to change any environment variables or install
|
|
any additional JAR files. In a cluster managed by Cloudera Manager, you do not need to change any settings in
|
|
Cloudera Manager.
|
|
</p>
|
|
</conbody>
|
|
</concept>
|