blob: c39463f0e591522c97aed45bdbfdce2c5bee4036 [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 id="query_lifetime">
<title>Impala Query Lifetime</title>
<data name="Category" value="Impala"/>
<data name="Category" value="Concepts"/>
<data name="Category" value="Querying"/>
<data name="Category" value="Developers"/>
<data name="Category" value="Data Analysts"/>
Impala queries progress through a series of stages from the time they are initiated to the time
they are completed. A query can also be cancelled before it is entirely finished, either
because of an explicit cancellation, or because of a timeout, out-of-memory, or other error condition.
Understanding the query lifecycle can help you manage the throughput and resource usage of Impala
queries, especially in a high-concurrency or multi-workload environment.
<p outputclass="toc"/>