Upgrading Impala involves building or acquiring new Impala-related binaries, and then restarting Impala services.
Shut down all Impala-related daemons on all relevant hosts in the cluster:
impaladon each Impala node in your cluster:
$ sudo service impala-server stop
Stop any instances of the state store in your cluster:
$ sudo service impala-state-store stop
Stop any instances of the catalog service in your cluster:
$ sudo service impala-catalog stop
Follow the build procedure in the README.md file to produce new Impala binaries.
Replace the binaries for all Impala-related daemons on all relevant hosts in the cluster.
- Check if there are new recommended or required configuration settings to put into place in the configuration files, typically under /etc/impala/conf. See Post-Installation Configuration for Impala for settings related to performance and scalability.
Restart all Impala-related daemons on all relevant hosts in the cluster:
Restart the Impala state store service on the desired nodes in your cluster. Expect to see a process
statestoredif the service started successfully.
$ sudo service impala-state-store start $ ps ax | grep [s]tatestored 6819 ? Sl 0:07 /usr/lib/impala/sbin/statestored -log_dir=/var/log/impala -state_store_port=24000
Restart the state store service before the Impala server service to avoid "Not connected" errors when you run
Restart the Impala catalog service on whichever host it runs on in your cluster. Expect to see a
catalogdif the service started successfully.
$ sudo service impala-catalog restart $ ps ax | grep [c]atalogd 6068 ? Sl 4:06 /usr/lib/impala/sbin/catalogd
Restart the Impala daemon service on each node in your cluster. Expect to see a process named
impaladif the service started successfully.
$ sudo service impala-server start $ ps ax | grep [i]mpalad 7936 ? Sl 0:12 /usr/lib/impala/sbin/impalad -log_dir=/var/log/impala -state_store_port=24000 -state_store_host=127.0.0.1 -be_port=22000
- Restart the Impala state store service on the desired nodes in your cluster. Expect to see a process named
If the services did not start successfully (even though the
sudo service command might
[OK]), check for errors in the Impala log file, typically in
Impala Upgrade Considerations
List of Reserved Words Updated in Impala 3.0
The list of reserved words in Impala was updated in Impala 3.0. If you need to use a reserved word as an identifier, e.g. a table name, enclose the word in back-ticks.
catalogdstartup flag. Note that this startup option will be deprecated in a future release.
Decimal V2 Used by Default in Impala 3.0
In Impala, two different implementations of
types are supported. Starting in Impala 3.0,
DECIMAL V2 is used by default. See DECIMAL Type for detail information.
DECIMALtype for the backward compatibility of your queries, set the
DECIMAL_V2query option to
Behavior of Column Aliases Changed in Impala 3.0
To conform to the SQL standard, Impala no longer performs alias
substitution in the subexpressions of
ORDER BY. See Overview of Impala Aliases for examples of supported and unsupported aliases
Default PARQUET_ARRAY_RESOLUTION Changed in Impala 3.0
The default value for the
was changed to
THREE_LEVEL in Impala 3.0, to match the Parquet standard 3-level
See PARQUET_ARRAY_RESOLUTION Query Option (Impala 2.9 or higher only) for the information about the query option.
Enable Clustering Hint for Inserts
In Impala 3.0, the clustered hint is enabled by default. The hint adds a local sort by the partitioning columns to a query plan.
clustered hint is only effective for HDFS and
As in previous versions, the
prevents clustering. If a table has ordering columns defined, the
noclustered hint is ignored with a warning.
Deprecated Query Options Removed in Impala 3.0
Fine-grained Privileges Added in Impala 3.0
Starting in Impala 3.0, finer grained
privileges are enforced, such as the
ALTER privileges. In particular, running
INVALIDATE METADATA now
requires the new
REFRESH privilege. Users who did not
previously have the
ALL privilege will no longer be
able to run
METADATA after an upgrade. Those users need to have the
ALL privilege granted
See GRANT Statement (Impala 2.0 or higher only) for the new privileges, the scope, and other information about the new privileges.
refresh_after_connect Impala Shell Option Removed in Impala 3.0
refresh_after_connect option was
removed from Impala Shell in Impala 3.0
Default Setting Changes
|Release Changed||Setting||Default Value|