blob: 2d98b26b12938f83c5dc853ca2920cac3eea085e [file] [log] [blame]
<?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
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
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 rev="1.1" id="invalidate_metadata">
<title>INVALIDATE METADATA Statement</title>
<titlealts audience="PDF">
<navtitle>INVALIDATE METADATA</navtitle>
<data name="Category" value="Impala"/>
<data name="Category" value="SQL"/>
<data name="Category" value="DDL"/>
<data name="Category" value="ETL"/>
<data name="Category" value="Ingest"/>
<data name="Category" value="Metastore"/>
<data name="Category" value="Schemas"/>
<data name="Category" value="Tables"/>
<data name="Category" value="Developers"/>
<data name="Category" value="Data Analysts"/>
The <codeph>INVALIDATE METADATA</codeph> statement marks the metadata for one or all
tables as stale. The next time the Impala service performs a query against a table whose
metadata is invalidated, Impala reloads the associated metadata before the query proceeds.
As this is a very expensive operation compared to the incremental metadata update done by
the <codeph>REFRESH</codeph> statement, when possible, prefer <codeph>REFRESH</codeph>
rather than <codeph>INVALIDATE METADATA</codeph>.
<codeph>INVALIDATE METADATA</codeph> is required when the following changes are made
outside of Impala, in Hive and other Hive client, such as SparkSQL:
Metadata of existing tables changes.
New tables are added, and Impala will use the tables.
The <codeph>SERVER</codeph> or <codeph>DATABASE</codeph> level Sentry privileges are
Block metadata changes, but the files remain the same (HDFS rebalance).
UDF jars change.
Some tables are no longer queried, and you want to remove their metadata from the
catalog and coordinator caches to reduce memory requirements.
No <codeph>INVALIDATE METADATA</codeph> is needed when the changes are made by
See <xref href="impala_hadoop.xml#intro_metastore"/> for the information about the way
Impala uses metadata and how it shares the same metastore database as Hive.
Once issued, the <codeph>INVALIDATE METADATA</codeph> statement cannot be cancelled.
<p conref="../shared/impala_common.xml#common/syntax_blurb"/>
<codeblock>INVALIDATE METADATA [[<varname>db_name</varname>.]<varname>table_name</varname>]</codeblock>
If there is no table specified, the cached metadata for all tables is flushed and synced
with Hive Metastore (HMS). If tables were dropped from the HMS, they will be removed from
the catalog, and if new tables were added, they will show up in the catalog.
If you specify a table name, only the metadata for that one table is flushed and synced
with the HMS.
<p conref="../shared/impala_common.xml#common/usage_notes_blurb"/>
To return accurate query results, Impala need to keep the metadata current for the
databases and tables queried. Therefore, if some other entity modifies information used by
Impala in the metastore, the information cached by Impala must be updated via
<codeph>INVALIDATE METADATA</codeph> or <codeph>REFRESH</codeph>.
<p conref="../shared/impala_common.xml#common/refresh_vs_invalidate"/>
Use <codeph>REFRESH</codeph> after invalidating a specific table to separate the metadata
load from the first query that's run against that table.
<p conref="../shared/impala_common.xml#common/example_blurb"/>
<p rev="1.2.4">
This example illustrates creating a new database and new table in Hive, then doing an
<codeph>INVALIDATE METADATA</codeph> statement in Impala using the fully qualified table
name, after which both the new table and the new database are visible to Impala.
Before the <codeph>INVALIDATE METADATA</codeph> statement was issued, Impala would give a
<q>not found</q> error if you tried to refer to those database or table names.
<codeblock rev="1.2.4">$ hive
hive&gt; CREATE DATABASE new_db_from_hive;
hive&gt; CREATE TABLE new_db_from_hive.new_table_from_hive (x INT);
hive&gt; quit;
$ impala-shell
&gt; REFRESH new_db_from_hive.new_table_from_hive;
ERROR: AnalysisException: Database does not exist: new_db_from_hive
&gt; INVALIDATE METADATA new_db_from_hive.new_table_from_hive;
| new_db_from_hive |
&gt; SHOW TABLES IN new_db_from_hive;
| new_table_from_hive |
Use the <codeph>REFRESH</codeph> statement for incremental metadata update.
> REFRESH new_table_from_hive;
For more examples of using <codeph>INVALIDATE METADATA</codeph> with a combination of
Impala and Hive operations, see
<p conref="../shared/impala_common.xml#common/hdfs_blurb"/>
By default, the <codeph>INVALIDATE METADATA</codeph> command checks HDFS permissions of
the underlying data files and directories, caching this information so that a statement
can be cancelled immediately if for example the <codeph>impala</codeph> user does not have
permission to write to the data directory for the table. (This checking does not apply
when the <cmdname>catalogd</cmdname> configuration option
<codeph>--load_catalog_in_background</codeph> is set to <codeph>false</codeph>, which it
is by default.) Impala reports any lack of write permissions as an <codeph>INFO</codeph>
message in the log file.
If you change HDFS permissions to make data readable or writeable by the Impala user,
issue another <codeph>INVALIDATE METADATA</codeph> to make Impala aware of the change.
<p rev="kudu" conref="../shared/impala_common.xml#common/kudu_blurb"/>
<p conref="../shared/impala_common.xml#common/kudu_metadata_intro"/>
<p conref="../shared/impala_common.xml#common/kudu_metadata_details"/>
<p conref="../shared/impala_common.xml#common/related_info"/>
<xref href="impala_hadoop.xml#intro_metastore"/>,