blob: b7a47aec67915665174071697b4ae4049a54c1b5 [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
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="num_scanner_threads">
<title>NUM_SCANNER_THREADS Query Option</title>
<titlealts audience="PDF"><navtitle>NUM_SCANNER_THREADS</navtitle></titlealts>
<prolog>
<metadata>
<data name="Category" value="Impala"/>
<data name="Category" value="Impala Query Options"/>
<data name="Category" value="Performance"/>
<data name="Category" value="Developers"/>
<data name="Category" value="Data Analysts"/>
</metadata>
</prolog>
<conbody>
<p>
<indexterm audience="hidden">NUM_SCANNER_THREADS query option</indexterm>
Maximum number of scanner threads (on each node) used for each query. By default, Impala uses as many cores
as are available (one thread per core). You might lower this value if queries are using excessive resources
on a busy cluster. Impala imposes a maximum value automatically, so a high value has no practical effect.
</p>
<p>
<b>Type:</b> numeric
</p>
<p>
<b>Default:</b> 0
</p>
</conbody>
</concept>