mirror of
https://github.com/apache/impala.git
synced 2026-01-06 06:01:03 -05:00
c4ee03a7e5
Initial experiment to see how the doc looks & builds when the biggest, most obvious pieces of Cloudera Manager-related content are suppressed: - Primarily entire subtopics. - In some cases, individual notes, paragraphs, and list items. - Also the CM reference in the reused "cancel" text which showed up many times throughout the SQL syntax section. Just hiding in the output for now, rather than removing from source, because we might find there's generic material we need to hoist out of the CM-related subtopics. Was planning to use audience="hidden" to hide, but since that CR hasn't landed in master yet, still using audience="Cloudera" for the moment, and will switch attribute values later. A little rewording of titles and suppressing smaller elements such as paragraphs where the CM aspect didn't apply to the entire subtopic. Change-Id: Ic799f77bc758a1cf40c53fa412bf02d852901a69 Reviewed-on: http://gerrit.cloudera.org:8080/5607 Reviewed-by: Jim Apple <jbapple-impala@apache.org> Tested-by: John Russell <jrussell@cloudera.com>
75 lines
3.4 KiB
XML
75 lines
3.4 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!--
|
|
Licensed to the Apache Software Foundation (ASF) under one
|
|
or more contributor license agreements. See the NOTICE file
|
|
distributed with this work for additional information
|
|
regarding copyright ownership. The ASF licenses this file
|
|
to you under the Apache License, Version 2.0 (the
|
|
"License"); you may not use this file except in compliance
|
|
with the License. You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing,
|
|
software distributed under the License is distributed on an
|
|
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
KIND, either express or implied. See the License for the
|
|
specific language governing permissions and limitations
|
|
under the License.
|
|
-->
|
|
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
|
|
<concept id="cm_installation" audience="Cloudera">
|
|
|
|
<title>Installing Impala with Cloudera Manager</title>
|
|
<prolog>
|
|
<metadata>
|
|
<data name="Category" value="Impala"/>
|
|
<data name="Category" value="Installing"/>
|
|
<data name="Category" value="Cloudera Manager"/>
|
|
<data name="Category" value="Administrators"/>
|
|
</metadata>
|
|
</prolog>
|
|
|
|
<conbody>
|
|
|
|
<p>
|
|
Before installing Impala through the Cloudera Manager interface, make sure all applicable nodes have the
|
|
appropriate hardware configuration and levels of operating system and CDH. See
|
|
<xref href="impala_prereqs.xml#prereqs"/> for details.
|
|
</p>
|
|
|
|
<note rev="1.2.0">
|
|
<p rev="1.2.0">
|
|
To install the latest Impala under CDH 4, upgrade Cloudera Manager to 4.8 or higher. Cloudera Manager 4.8 is
|
|
the first release that can manage the Impala catalog service introduced in Impala 1.2. Cloudera Manager 4.8
|
|
requires this service to be present, so if you upgrade to Cloudera Manager 4.8, also upgrade Impala to the
|
|
most recent version at the same time.
|
|
<!-- Not so relevant now for 1.1.1, but maybe someday we'll capture all this history in a compatibility grid.
|
|
Upgrade to Cloudera Manager 4.6.2 or higher to enable Cloudera Manager to
|
|
handle access control for the Impala web UI, available by default through
|
|
port 25000 on each Impala host.
|
|
-->
|
|
</p>
|
|
</note>
|
|
|
|
<p>
|
|
For information on installing Impala in a Cloudera Manager-managed environment, see
|
|
<xref audience="integrated" href="cm_ig_install_impala.xml"/><xref audience="standalone" href="http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_install_impala.html" scope="external" format="html">Installing Impala</xref>.
|
|
</p>
|
|
|
|
<p>
|
|
Managing your Impala installation through Cloudera Manager has a number of advantages. For example, when you
|
|
make configuration changes to CDH components using Cloudera Manager, it automatically applies changes to the
|
|
copies of configuration files, such as <codeph>hive-site.xml</codeph>, that Impala keeps under
|
|
<filepath>/etc/impala/conf</filepath>. It also sets up the Hive Metastore service that is required for
|
|
Impala running under CDH 4.1.
|
|
</p>
|
|
|
|
<p>
|
|
In some cases, depending on the level of Impala, CDH, and Cloudera Manager, you might need to add particular
|
|
component configuration details in some of the free-form option fields on the Impala configuration pages
|
|
within Cloudera Manager. <ph conref="../shared/impala_common.xml#common/safety_valve"/>
|
|
</p>
|
|
</conbody>
|
|
</concept>
|