impala-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbap...@apache.org
Subject [33/51] [partial] incubator-impala git commit: IMPALA-4181 [DOCS] Publish rendered Impala documentation to ASF site
Date Wed, 12 Apr 2017 18:25:37 GMT
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/75c46918/docs/build/html/topics/impala_fixed_issues.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_fixed_issues.html b/docs/build/html/topics/impala_fixed_issues.html
new file mode 100644
index 0000000..9444528
--- /dev/null
+++ b/docs/build/html/topics/impala_fixed_issues.html
@@ -0,0 +1,5889 @@
+<!DOCTYPE html
+  SYSTEM "about:legacy-compat">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_release_notes.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="fixed_issues"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Fixed Issues in Apache Impala (incubating)</title></head><body id="fixed_issues"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+
+  <h1 class="title topictitle1" id="ariaid-title1"><span class="ph">Fixed Issues in Apache Impala (incubating)</span></h1>
+  
+
+  <div class="body conbody">
+
+    <p class="p">
+      The following sections describe the major issues fixed in each Impala release.
+    </p>
+
+    <p class="p">
+      For known issues that are currently unresolved, see <a class="xref" href="impala_known_issues.html#known_issues">Known Issues and Workarounds in Impala</a>.
+    </p>
+
+    <p class="p toc inpage"></p>
+  </div>
+
+
+
+  <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_release_notes.html">Impala Release Notes</a></div></div></nav><article class="topic concept nested1" aria-labelledby="ariaid-title2" id="fixed_issues__fixed_issues_280">
+
+    <h2 class="title topictitle2" id="ariaid-title2">Issues Fixed in <span class="keyword">Impala 2.8.0</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        For the full list of Impala fixed issues in <span class="keyword">Impala 2.8</span>, see
+        <a class="xref" href="https://issues.apache.org/jira/issues/?jql=type%20%3D%20bug%20and%20project%20%3D%20IMPALA%20AND%20resolution%20%3D%20fixed%20AND%20affectedVersion%20!%3D%20%22Impala%202.8.0%22%20AND%20fixVersion%20%3D%20%22Impala%202.8.0%22%20and%20not%20labels%20%3D%20broken-build%20order%20by%20priority%20desc" target="_blank">this report in the Impala JIRA tracker</a>.
+      </p>
+
+    </div>
+  </article>
+
+
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title3" id="fixed_issues__fixed_issues_270">
+
+    <h2 class="title topictitle2" id="ariaid-title3">Issues Fixed in <span class="keyword">Impala 2.7.0</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+
+        For the full list of Impala fixed issues in Impala 2.7.0, see
+        <a class="xref" href="https://issues.apache.org/jira/issues/?jql=%20type%20%3D%20bug%20and%20project%20%3D%20IMPALA%20AND%20resolution%20%3D%20fixed%20AND%20affectedVersion%20!%3D%20%22Impala%202.7.0%22%20AND%20fixVersion%20%3D%20%22Impala%202.7.0%22%20and%20not%20labels%20%3D%20broken-build%20order%20by%20priority%20desc" target="_blank">this report in the Impala JIRA tracker</a>.
+      </p>
+
+    </div>
+  </article>
+
+
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="fixed_issues__fixed_issues_263">
+    <h2 class="title topictitle2" id="ariaid-title4">Issues Fixed in <span class="keyword">Impala 2.6.3</span></h2>
+    <div class="body conbody">
+      <p class="p"></p>
+    </div>
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="fixed_issues__fixed_issues_262">
+    <h2 class="title topictitle2" id="ariaid-title5">Issues Fixed in <span class="keyword">Impala 2.6.2</span></h2>
+    <div class="body conbody">
+      <p class="p"></p>
+    </div>
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="fixed_issues__fixed_issues_260">
+
+    <h2 class="title topictitle2" id="ariaid-title6">Issues Fixed in <span class="keyword">Impala 2.6.0</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        The following list contains the most critical fixed issues
+        (<code class="ph codeph">priority='Blocker'</code>) from the JIRA system.
+        For the full list of fixed issues in <span class="keyword">Impala 2.6.0</span>, see
+        <a class="xref" href="https://issues.apache.org/jira/issues/?jql=%20type%20%3D%20bug%20and%20project%20%3D%20IMPALA%20AND%20resolution%20%3D%20fixed%20AND%20affectedVersion%20!%3D%20%22Impala%202.6.0%22%20AND%20fixVersion%20%3D%20%22Impala%202.6.0%22%20and%20not%20labels%20%3D%20broken-build%20order%20by%20priority%20desc" target="_blank">this report in the Impala JIRA tracker</a>.
+      </p>
+
+    </div>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title7" id="fixed_issues_260__IMPALA-3385">
+      <h3 class="title topictitle3" id="ariaid-title7">RuntimeState::error_log_ crashes</h3>
+      <div class="body conbody">
+      <p class="p">
+        A crash could occur, with stack trace pointing to <code class="ph codeph">impala::RuntimeState::ErrorLog</code>.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3385" target="_blank">IMPALA-3385</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title8" id="fixed_issues_260__IMPALA-3378">
+      <h3 class="title topictitle3" id="ariaid-title8">HiveUdfCall::Open() produces unsynchronized access to JniUtil::global_refs_ vector</h3>
+      <div class="body conbody">
+      <p class="p">
+        A crash could occur because of contention between multiple calls to Java UDFs.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3378" target="_blank">IMPALA-3378</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title9" id="fixed_issues_260__IMPALA-3379">
+      <h3 class="title topictitle3" id="ariaid-title9">HBaseTableWriter::CreatePutList() produces unsynchronized access to JniUtil::global_refs_ vector</h3>
+      <div class="body conbody">
+      <p class="p">
+        A crash could occur because of contention between multiple concurrent statements writing to HBase.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3379" target="_blank">IMPALA-3379</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title10" id="fixed_issues_260__IMPALA-3317">
+      <h3 class="title topictitle3" id="ariaid-title10">Stress test failure: sorter.cc:745] Check failed: i == 0 (1 vs. 0) </h3>
+      <div class="body conbody">
+      <p class="p">
+        A crash or wrong results could occur if the spill-to-disk mechanism encountered a zero-length string at
+        the very end of a data block.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3317" target="_blank">IMPALA-3317</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title11" id="fixed_issues_260__IMPALA-3311">
+      <h3 class="title topictitle3" id="ariaid-title11">String data coming out of agg can be corrupted by blocking operators</h3>
+      <div class="body conbody">
+      <p class="p">
+        If a query plan contains an aggregation node producing string values anywhere within a subplan
+        (that is,if in the SQL statement, the aggregate function appears within an inline view over a collection column),
+        the results of the aggregation may be incorrect.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3311" target="_blank">IMPALA-3311</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title12" id="fixed_issues_260__IMPALA-3269">
+      <h3 class="title topictitle3" id="ariaid-title12">CTAS with subquery throws AuthzException</h3>
+      <div class="body conbody">
+      <p class="p">
+        A <code class="ph codeph">CREATE TABLE AS SELECT</code> operation could fail with an authorization error,
+        due to a slight difference in the privilege checking for the CTAS operation.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3269" target="_blank">IMPALA-3269</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title13" id="fixed_issues_260__IMPALA-3237">
+      <h3 class="title topictitle3" id="ariaid-title13">Crash on inserting into table with binary and parquet</h3>
+      <div class="body conbody">
+      <p class="p">
+        Impala incorrectly allowed <code class="ph codeph">BINARY</code> to be specified as a column type,
+        resulting in a crash during a write to a Parquet table with a column of that type.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3237" target="_blank">IMPALA-3237</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title14" id="fixed_issues_260__IMPALA-3105">
+      <h3 class="title topictitle3" id="ariaid-title14">RowBatch::MaxTupleBufferSize() calculation incorrect, may lead to memory corruption</h3>
+      <div class="body conbody">
+      <p class="p">
+        A crash could occur while querying tables with very large rows, for example wide tables with many
+        columns or very large string values. This problem was identified in Impala 2.3, but had low
+        reproducibility in subsequent releases. The fix ensures the memory allocation size is correct.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3105" target="_blank">IMPALA-3105</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title15" id="fixed_issues_260__IMPALA-3494">
+      <h3 class="title topictitle3" id="ariaid-title15">Thrift buffer overflows when serialize more than 3355443200 bytes in impala</h3>
+      <div class="body conbody">
+      <p class="p">
+        A very large memory allocation within the <span class="keyword cmdname">catalogd</span> daemon could exceed an internal Thrift limit,
+        causing a crash.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3494" target="_blank">IMPALA-3494</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title16" id="fixed_issues_260__IMPALA-3314">
+      <h3 class="title topictitle3" id="ariaid-title16">Altering table partition's storage format is not working and crashing the daemon</h3>
+      <div class="body conbody">
+      <p class="p">
+        If a partitioned table used a file format other than Avro, and the file format of an individual partition
+        was changed to Avro, subsequent queries could encounter a crash.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3314" target="_blank">IMPALA-3314</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title17" id="fixed_issues_260__IMPALA-3798">
+      <h3 class="title topictitle3" id="ariaid-title17">Race condition may cause scanners to spin with runtime filters on Avro or Sequence files</h3>
+      <div class="body conbody">
+      <p class="p">
+        A timing problem during runtime filter processing could cause queries against Avro or SequenceFile tables
+        to hang.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3798" target="_blank">IMPALA-3798</a></p>
+      <p class="p"><strong class="ph b">Severity:</strong> High</p>
+      </div>
+    </article>
+
+  </article>
+
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title18" id="fixed_issues__fixed_issues_254">
+    <h2 class="title topictitle2" id="ariaid-title18">Issues Fixed in <span class="keyword">Impala 2.5.4</span></h2>
+    <div class="body conbody">
+      <p class="p"></p>
+    </div>
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title19" id="fixed_issues__fixed_issues_252">
+    <h2 class="title topictitle2" id="ariaid-title19">Issues Fixed in <span class="keyword">Impala 2.5.2</span></h2>
+    <div class="body conbody">
+      <p class="p"></p>
+    </div>
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title20" id="fixed_issues__fixed_issues_251">
+
+    <h2 class="title topictitle2" id="ariaid-title20">Issues Fixed in <span class="keyword">Impala 2.5.1</span></h2>
+
+    <div class="body conbody">
+      <p class="p"></p>
+    </div>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title21" id="fixed_issues__fixed_issues_250">
+
+    <h2 class="title topictitle2" id="ariaid-title21">Issues Fixed in <span class="keyword">Impala 2.5.0</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        The following list contains the most critical issues (<code class="ph codeph">priority='Blocker'</code>) from the JIRA system.
+        For the full list of fixed issues in <span class="keyword">Impala 2.5</span>, see
+        <a class="xref" href="https://issues.apache.org/jira/issues/?jql=%20type%20%3D%20bug%20and%20project%20%3D%20IMPALA%20AND%20resolution%20%3D%20fixed%20AND%20affectedVersion%20!%3D%20%22Impala%202.5.0%22%20AND%20fixVersion%20%3D%20%22Impala%202.5.0%22%20and%20not%20labels%20%3D%20broken-build%20order%20by%20priority%20desc" target="_blank">this report in the Impala JIRA tracker</a>.
+      </p>
+
+    </div>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title22" id="fixed_issues_250__IMPALA-2683">
+      <h3 class="title topictitle3" id="ariaid-title22">Stress test hit assert in LLVM: external function could not be resolved</h3>
+      <div class="body conbody">
+<p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2683" target="_blank">IMPALA-2683</a></p>
+<p class="p">The stress test was running a build with the TPC-H, TPC-DS, and TPC-H nested queries with scale factor 3.</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title23" id="fixed_issues_250__IMPALA-2365">
+      <h3 class="title topictitle3" id="ariaid-title23">Impalad is crashing if udf jar is not available in hdfs location for first time</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2365" target="_blank">IMPALA-2365</a></p>
+        <p class="p">
+          If a UDF JAR was not available in the HDFS location specified in the <code class="ph codeph">CREATE FUNCTION</code> statement,
+          the <span class="keyword cmdname">impalad</span> daemon could crash.
+        </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title24" id="fixed_issues_250__IMPALA-2535-570">
+      <h3 class="title topictitle3" id="ariaid-title24">PAGG hits mem_limit when switching to I/O buffers</h3>
+      <div class="body conbody">
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2535" target="_blank">IMPALA-2535</a></p>
+      <p class="p">
+        A join query could fail with an out-of-memory error despite the apparent presence of sufficient memory.
+        The cause was the internal ordering of operations that could cause a later phase of the query to
+        allocate memory required by an earlier phase of the query. The workaround was to either increase
+        or decrease the <code class="ph codeph">MEM_LIMIT</code> query option, because the issue would only occur for a specific
+        combination of memory limit and data volume.
+      </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title25" id="fixed_issues_250__IMPALA-2643-570">
+      <h3 class="title topictitle3" id="ariaid-title25">Prevent migrating incorrectly inferred identity predicates into inline views</h3>
+      <div class="body conbody">
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2643" target="_blank">IMPALA-2643</a></p>
+      <p class="p">
+        Referring to the same column twice in a view definition could cause the view to omit
+        rows where that column contained a <code class="ph codeph">NULL</code> value. This could cause
+        incorrect results due to an inaccurate <code class="ph codeph">COUNT(*)</code> value or rows missing
+        from the result set.
+      </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title26" id="fixed_issues_250__IMPALA-1459-570">
+      <h3 class="title topictitle3" id="ariaid-title26">Fix migration/assignment of On-clause predicates inside inline views</h3>
+      <div class="body conbody">
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1459" target="_blank">IMPALA-1459</a></p>
+      <p class="p">
+        Some combinations of <code class="ph codeph">ON</code> clauses in join queries could result in comparisons
+        being applied at the wrong stage of query processing, leading to incorrect results.
+        Wrong predicate assignment could happen under the following conditions:
+      </p>
+      <ul class="ul">
+        <li class="li">
+          The query includes an inline view that contains an outer join.
+        </li>
+        <li class="li">
+          That inline view is joined with another table in the enclosing query block.
+        </li>
+        <li class="li">
+          That join has an <code class="ph codeph">ON</code> clause containing a predicate that
+          only references columns originating from the outer-joined tables inside the inline view.
+        </li>
+      </ul>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title27" id="fixed_issues_250__IMPALA-2093">
+      <h3 class="title topictitle3" id="ariaid-title27">Wrong plan of NOT IN aggregate subquery when a constant is used in subquery predicate</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2093" target="_blank">IMPALA-2093</a></p>
+        <p class="p">
+          <code class="ph codeph">IN</code> subqueries might return wrong results if the left-hand side of the <code class="ph codeph">IN</code> is a constant.
+          For example:
+        </p>
+<pre class="pre codeblock"><code>
+select * from alltypestiny t1
+  where 10 not in (select sum(int_col) from alltypestiny);
+</code></pre>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title28" id="fixed_issues_250__IMPALA-2940">
+      <h3 class="title topictitle3" id="ariaid-title28">Parquet DictDecoders accumulate throughout query</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2940" target="_blank">IMPALA-2940</a></p>
+        <p class="p">
+          Parquet dictionary decoders can accumulate throughout query execution, leading to excessive memory usage. One decoder is created per-column per-split.
+        </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title29" id="fixed_issues_250__IMPALA-3056">
+      <h3 class="title topictitle3" id="ariaid-title29">Planner doesn't set the has_local_target field correctly</h3>
+      <div class="body conbody">
+<p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3056" target="_blank">IMPALA-3056</a></p>
+
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title30" id="fixed_issues_250__IMPALA-2742">
+      <h3 class="title topictitle3" id="ariaid-title30">MemPool allocation growth behavior</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2742" target="_blank">IMPALA-2742</a></p>
+        <p class="p">
+          Currently, the MemPool would always double the size of the last allocation.
+          This can lead to bad behavior if the MemPool transferred the ownership of all its data
+          except the last chunk. In the next allocation, the next allocated chunk would double
+          the size of this large chunk, which can be undesirable.
+        </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title31" id="fixed_issues_250__IMPALA-3035">
+      <h3 class="title topictitle3" id="ariaid-title31">Drop partition operations don't follow the catalog's locking protocol</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3035" target="_blank">IMPALA-3035</a></p>
+        <p class="p">
+          The <code class="ph codeph">CatalogOpExecutor.alterTableDropPartition()</code> function violates
+          the locking protocol used in the catalog that requires <code class="ph codeph">catalogLock_</code>
+          to be acquired before any table-level lock. That may cause deadlocks when <code class="ph codeph">ALTER TABLE DROP PARTITION</code>
+          is executed concurrently with other DDL operations.
+        </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title32" id="fixed_issues_250__IMPALA-2215">
+      <h3 class="title topictitle3" id="ariaid-title32">HAVING clause without aggregation not applied properly</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2215" target="_blank">IMPALA-2215</a></p>
+        <p class="p">
+          A query with a <code class="ph codeph">HAVING</code> clause but no <code class="ph codeph">GROUP BY</code> clause was not being rejected,
+          despite being invalid syntax. For example:
+        </p>
+
+<pre class="pre codeblock"><code>
+select case when 1=1 then 'didit' end as c1 from (select 1 as one) a having 1!=1;
+</code></pre>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title33" id="fixed_issues_250__IMPALA-2914">
+      <h3 class="title topictitle3" id="ariaid-title33">Hit DCHECK Check failed: HasDateOrTime()</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2914" target="_blank">IMPALA-2914</a></p>
+        <p class="p">
+          <code class="ph codeph">TimestampValue::ToTimestampVal()</code> requires a valid <code class="ph codeph">TimestampValue</code> as input.
+          This requirement was not enforced in some places, leading to serious errors.
+        </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title34" id="fixed_issues_250__IMPALA-2986">
+      <h3 class="title topictitle3" id="ariaid-title34">Aggregation spill loop gives up too early leading to mem limit exceeded errors</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2986" target="_blank">IMPALA-2986</a></p>
+        <p class="p">
+          An aggregation query could fail with an out-of-memory error, despite sufficient memory being reported as available.
+        </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title35" id="fixed_issues_250__IMPALA-2592">
+      <h3 class="title topictitle3" id="ariaid-title35">DataStreamSender::Channel::CloseInternal() does not close the channel on an error.</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2592" target="_blank">IMPALA-2592</a></p>
+        <p class="p">
+          Some queries do not close an internal communication channel on an error.
+          This will cause the node on the other side of the channel to wait indefinitely, causing the query to hang.
+          For example, this issue could happen on a Kerberos-enabled system if the credential cache was outdated.
+          Although the affected query hangs, the <span class="keyword cmdname">impalad</span> daemons continue processing other queries.
+        </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title36" id="fixed_issues_250__IMPALA-2184">
+      <h3 class="title topictitle3" id="ariaid-title36">Codegen does not catch exceptions in FROM_UNIXTIME()</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2184" target="_blank">IMPALA-2184</a></p>
+        <p class="p">
+          Querying for the min or max value of a timestamp cast from a bigint via <code class="ph codeph">from_unixtime()</code>
+          fails silently and crashes instances of <span class="keyword cmdname">impalad</span> when the input includes a value outside of the valid range.
+        </p>
+
+        <p class="p"><strong class="ph b">Workaround:</strong> Disable native code generation with:</p>
+<pre class="pre codeblock"><code>
+SET disable_codegen=true;
+</code></pre>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title37" id="fixed_issues_250__IMPALA-2788">
+      <h3 class="title topictitle3" id="ariaid-title37">Impala returns wrong result for function 'conv(bigint, from_base, to_base)'</h3>
+      <div class="body conbody">
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2788" target="_blank">IMPALA-2788</a></p>
+        <p class="p">
+          Impala returns wrong result for function <code class="ph codeph">conv()</code>.
+          Function <code class="ph codeph">conv(bigint, from_base, to_base)</code> returns an correct result,
+          while <code class="ph codeph">conv(string, from_base, to_base)</code> returns the correct value.
+          For example:
+        </p>
+
+<pre class="pre codeblock"><code>
+
+select 2061013007, conv(2061013007, 16, 10), conv('2061013007', 16, 10);
++------------+--------------------------+----------------------------+
+| 2061013007 | conv(2061013007, 16, 10) | conv('2061013007', 16, 10) |
++------------+--------------------------+----------------------------+
+| 2061013007 | 1627467783               | 139066421255               |
++------------+--------------------------+----------------------------+
+Fetched 1 row(s) in 0.65s
+
+select 2061013007, conv(cast(2061013007 as bigint), 16, 10), conv('2061013007', 16, 10);
++------------+------------------------------------------+----------------------------+
+| 2061013007 | conv(cast(2061013007 as bigint), 16, 10) | conv('2061013007', 16, 10) |
++------------+------------------------------------------+----------------------------+
+| 2061013007 | 1627467783                               | 139066421255               |
++------------+------------------------------------------+----------------------------+
+
+select 2061013007, conv(cast(2061013007 as string), 16, 10), conv('2061013007', 16, 10);
++------------+------------------------------------------+----------------------------+
+| 2061013007 | conv(cast(2061013007 as string), 16, 10) | conv('2061013007', 16, 10) |
++------------+------------------------------------------+----------------------------+
+| 2061013007 | 139066421255                             | 139066421255               |
++------------+------------------------------------------+----------------------------+
+
+select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 10), conv('2061013007', 16, 10);
++------------+-----------------------------------------------------------------+----------------------------+
+| 2061013007 | conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 10) | conv('2061013007', 16, 10) |
++------------+-----------------------------------------------------------------+----------------------------+
+| 2061013007 | 1627467783                                                      | 139066421255               |
++------------+-----------------------------------------------------------------+----------------------------+
+
+</code></pre>
+
+        <p class="p"><strong class="ph b">Workaround:</strong>
+          Cast the value to string and use <code class="ph codeph">conv(string, from_base, to_base)</code> for conversion.
+        </p>
+      </div>
+    </article>
+
+
+
+  </article>
+
+
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title38" id="fixed_issues__fixed_issues_241">
+
+    <h2 class="title topictitle2" id="ariaid-title38">Issues Fixed in <span class="keyword">Impala 2.4.1</span></h2>
+
+    <div class="body conbody">
+      <p class="p">
+      </p>
+    </div>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title39" id="fixed_issues__fixed_issues_240">
+
+    <h2 class="title topictitle2" id="ariaid-title39">Issues Fixed in <span class="keyword">Impala 2.4.0</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        The set of fixes for Impala in <span class="keyword">Impala 2.4.0</span> is the same as
+        in <span class="keyword">Impala 2.3.2</span>.
+        
+      </p>
+
+    </div>
+
+  </article>
+
+
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title40" id="fixed_issues__fixed_issues_234">
+
+    <h2 class="title topictitle2" id="ariaid-title40">Issues Fixed in <span class="keyword">Impala 2.3.4</span></h2>
+
+    <div class="body conbody">
+      <p class="p"></p>
+    </div>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title41" id="fixed_issues__fixed_issues_232">
+
+    <h2 class="title topictitle2" id="ariaid-title41">Issues Fixed in <span class="keyword">Impala 2.3.2</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        This section lists the most serious or frequently encountered customer
+        issues fixed in <span class="keyword">Impala 2.3.2</span>.
+      </p>
+
+    </div>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title42" id="fixed_issues_232__IMPALA-2829">
+      <h3 class="title topictitle3" id="ariaid-title42">SEGV in AnalyticEvalNode touching NULL input_stream_</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query involving an analytic function could encounter a serious error.
+        This issue was encountered infrequently, depending upon specific combinations
+        of queries and data.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2829" target="_blank">IMPALA-2829</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title43" id="fixed_issues_232__IMPALA-2722">
+      <h3 class="title topictitle3" id="ariaid-title43">Free local allocations per row batch in non-partitioned AGG and HJ</h3>
+      <div class="body conbody">
+      <p class="p">
+        An outer join query could fail unexpectedly with an out-of-memory error
+        when the <span class="q">"spill to disk"</span> mechanism was turned off.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2722" target="_blank">IMPALA-2722</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title44" id="fixed_issues_232__IMPALA-2612">
+      
+      <h3 class="title topictitle3" id="ariaid-title44">Free local allocations once for every row batch when building hash tables</h3>
+      <div class="body conbody">
+      <p class="p">
+        A join query could encounter a serious error due to an internal failure to allocate memory, which
+        resulted in dereferencing a <code class="ph codeph">NULL</code> pointer.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2612" target="_blank">IMPALA-2612</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title45" id="fixed_issues_232__IMPALA-2643">
+      <h3 class="title topictitle3" id="ariaid-title45">Prevent migrating incorrectly inferred identity predicates into inline views</h3>
+      <div class="body conbody">
+      <p class="p">
+        Referring to the same column twice in a view definition could cause the view to omit
+        rows where that column contained a <code class="ph codeph">NULL</code> value. This could cause
+        incorrect results due to an inaccurate <code class="ph codeph">COUNT(*)</code> value or rows missing
+        from the result set.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2643" target="_blank">IMPALA-2643</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title46" id="fixed_issues_232__IMPALA-2695">
+      <h3 class="title topictitle3" id="ariaid-title46">Fix GRANTs on URIs with uppercase letters</h3>
+      <div class="body conbody">
+      <p class="p">
+        A <code class="ph codeph">GRANT</code> statement for a URI could be ineffective if the URI
+        contained uppercase letters, for example in an uppercase directory name.
+        Subsequent statements, such as <code class="ph codeph">CREATE EXTERNAL TABLE</code>
+        with a <code class="ph codeph">LOCATION</code> clause, could fail with an authorization exception.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2695" target="_blank">IMPALA-2695</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="IMPALA-2664-552__IMPALA-2648-552" id="fixed_issues_232__IMPALA-2664-552">
+      <h3 class="title topictitle3" id="IMPALA-2664-552__IMPALA-2648-552">Avoid sending large partition stats objects over thrift</h3>
+      <div class="body conbody">
+      <p class="p">
+        The <span class="keyword cmdname">catalogd</span> daemon could encounter a serious error
+        when loading the incremental statistics metadata for tables with large
+        numbers of partitions and columns. The problem occurred when the
+        internal representation of metadata for the table exceeded 2
+        GB, for example in a table with 20K partitions and 77 columns. The fix causes a
+        <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> operation to fail if it
+        would produce metadata that exceeded the maximum size.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2664" target="_blank">IMPALA-2664</a>,
+        <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2648" target="_blank">IMPALA-2648</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title48" id="fixed_issues_232__IMPALA-2226">
+      <h3 class="title topictitle3" id="ariaid-title48">Throw AnalysisError if table properties are too large (for the Hive metastore)</h3>
+      <div class="body conbody">
+      <p class="p">
+        <code class="ph codeph">CREATE TABLE</code> or <code class="ph codeph">ALTER TABLE</code> statements could fail with
+        metastore database errors due to length limits on the <code class="ph codeph">SERDEPROPERTIES</code> and <code class="ph codeph">TBLPROPERTIES</code> clauses.
+        (The limit on key size is 256, while the limit on value size is 4000.) The fix makes Impala handle these error conditions
+        more cleanly, by detecting too-long values rather than passing them to the metastore database.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2226" target="_blank">IMPALA-2226</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title49" id="fixed_issues_232__IMPALA-2273-552">
+      <h3 class="title topictitle3" id="ariaid-title49">Make MAX_PAGE_HEADER_SIZE configurable</h3>
+      <div class="body conbody">
+      <p class="p">
+        Impala could fail to access Parquet data files with page headers larger than 8 MB, which could
+        occur, for example, if the minimum or maximum values for a column were long strings. The
+        fix adds a configuration setting <code class="ph codeph">--max_page_header_size</code>, which you can use to
+        increase the Impala size limit to a value higher than 8 MB.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2273" target="_blank">IMPALA-2273</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title50" id="fixed_issues_232__IMPALA-2473">
+      <h3 class="title topictitle3" id="ariaid-title50">reduce scanner memory usage</h3>
+      <div class="body conbody">
+      <p class="p">
+        Queries on Parquet tables could consume excessive memory (potentially multiple gigabytes) due to producing
+        large intermediate data values while evaluating groups of rows. The workaround was to reduce the size of
+        the <code class="ph codeph">NUM_SCANNER_THREADS</code> query option, the <code class="ph codeph">BATCH_SIZE</code> query option,
+        or both.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2473" target="_blank">IMPALA-2473</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title51" id="fixed_issues_232__IMPALA-2113">
+      <h3 class="title topictitle3" id="ariaid-title51">Handle error when distinct and aggregates are used with a having clause</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query that included a <code class="ph codeph">DISTINCT</code> operator and a <code class="ph codeph">HAVING</code> clause, but no
+        aggregate functions or <code class="ph codeph">GROUP BY</code>, would fail with an uninformative error message.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2113" target="_blank">IMPALA-2113</a></p>
+      
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title52" id="fixed_issues_232__IMPALA-2225">
+      <h3 class="title topictitle3" id="ariaid-title52">Handle error when star based select item and aggregate are incorrectly used</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query that included <code class="ph codeph">*</code> in the <code class="ph codeph">SELECT</code> list, in addition to an
+        aggregate function call, would fail with an uninformative message if the query had no
+        <code class="ph codeph">GROUP BY</code> clause.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2225" target="_blank">IMPALA-2225</a></p>
+      
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title53" id="fixed_issues_232__IMPALA-2731-552">
+      <h3 class="title topictitle3" id="ariaid-title53">Refactor MemPool usage in HBase scan node</h3>
+      <div class="body conbody">
+      <p class="p">
+        Queries involving HBase tables used substantially more memory than in earlier Impala versions.
+        The problem occurred starting in Impala 2.2.8, as a result of the changes for IMPALA-2284.
+        The fix for this issue involves removing a separate memory work area for HBase queries
+        and reusing other memory that was already allocated.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2731" target="_blank">IMPALA-2731</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title54" id="fixed_issues_232__IMPALA-1459-552">
+      <h3 class="title topictitle3" id="ariaid-title54">Fix migration/assignment of On-clause predicates inside inline views</h3>
+      <div class="body conbody">
+      <p class="p">
+        Some combinations of <code class="ph codeph">ON</code> clauses in join queries could result in comparisons
+        being applied at the wrong stage of query processing, leading to incorrect results.
+        Wrong predicate assignment could happen under the following conditions:
+      </p>
+      <ul class="ul">
+        <li class="li">
+          The query includes an inline view that contains an outer join.
+        </li>
+        <li class="li">
+          That inline view is joined with another table in the enclosing query block.
+        </li>
+        <li class="li">
+          That join has an <code class="ph codeph">ON</code> clause containing a predicate that
+          only references columns originating from the outer-joined tables inside the inline view.
+        </li>
+      </ul>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1459" target="_blank">IMPALA-1459</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title55" id="fixed_issues_232__IMPALA-2558">
+      <h3 class="title topictitle3" id="ariaid-title55">DCHECK in parquet scanner after block read error</h3>
+      <div class="body conbody">
+      <p class="p">
+        A debug build of Impala could encounter a serious error after encountering some kinds of I/O
+        errors for Parquet files. This issue only occurred in debug builds, not release builds.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2558" target="_blank">IMPALA-2558</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title56" id="fixed_issues_232__IMPALA-2535">
+      <h3 class="title topictitle3" id="ariaid-title56">PAGG hits mem_limit when switching to I/O buffers</h3>
+      <div class="body conbody">
+      <p class="p">
+        A join query could fail with an out-of-memory error despite the apparent presence of sufficient memory.
+        The cause was the internal ordering of operations that could cause a later phase of the query to
+        allocate memory required by an earlier phase of the query. The workaround was to either increase
+        or decrease the <code class="ph codeph">MEM_LIMIT</code> query option, because the issue would only occur for a specific
+        combination of memory limit and data volume.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2535" target="_blank">IMPALA-2535</a></p>
+      </div>
+    </article>
+
+    
+    
+    <article class="topic concept nested2" aria-labelledby="ariaid-title57" id="fixed_issues_232__IMPALA-2559">
+      <h3 class="title topictitle3" id="ariaid-title57">Fix check failed: sorter_runs_.back()-&gt;is_pinned_</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query could fail with an internal error while calculating the memory limit.
+        This was an infrequent condition uncovered during stress testing.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2559" target="_blank">IMPALA-2559</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title58" id="fixed_issues_232__IMPALA-2614">
+      <h3 class="title topictitle3" id="ariaid-title58">Don't ignore Status returned by DataStreamRecvr::CreateMerger()</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query could fail with an internal error while calculating the memory limit.
+        This was an infrequent condition uncovered during stress testing.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2614" target="_blank">IMPALA-2614</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2559" target="_blank">IMPALA-2559</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title59" id="fixed_issues_232__IMPALA-2591">
+      <h3 class="title topictitle3" id="ariaid-title59">DataStreamSender::Send() does not return an error status if SendBatch() failed</h3>
+      <div class="body conbody">
+      
+      <p class="p">
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2591" target="_blank">IMPALA-2591</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title60" id="fixed_issues_232__IMPALA-2598">
+      <h3 class="title topictitle3" id="ariaid-title60">Re-enable SSL and Kerberos on server-server</h3>
+      <div class="body conbody">
+      <p class="p">
+        These fixes lift the restriction on using SSL encryption and Kerberos authentication together
+        for internal communication between Impala components.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2598" target="_blank">IMPALA-2598</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2747" target="_blank">IMPALA-2747</a></p>
+      </div>
+    </article>
+
+
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title61" id="fixed_issues__fixed_issues_231">
+
+    <h2 class="title topictitle2" id="ariaid-title61">Issues Fixed in <span class="keyword">Impala 2.3.1</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        The version of Impala that is included with <span class="keyword">Impala 2.3.1</span> is identical to <span class="keyword">Impala 2.3.0</span>.
+        There are no new bug fixes, new features, or incompatible changes.
+      </p>
+
+    </div>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title62" id="fixed_issues__fixed_issues_230">
+
+    <h2 class="title topictitle2" id="ariaid-title62">Issues Fixed in <span class="keyword">Impala 2.3.0</span></h2>
+
+    <div class="body conbody">
+      <p class="p"> This section lists the most serious or frequently encountered customer
+        issues fixed in <span class="keyword">Impala 2.3</span>. Any issues already fixed in
+        <span class="keyword">Impala 2.2</span> maintenance releases (up through <span class="keyword">Impala 2.2.8</span>) are also included.
+        Those issues are listed under the respective <span class="keyword">Impala 2.2</span> sections and are
+        not repeated here.
+      </p>
+
+
+
+    </div>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title63" id="fixed_issues_230__serious_230">
+      <h3 class="title topictitle3" id="ariaid-title63">Fixes for Serious Errors</h3>
+      <div class="body conbody">
+      <p class="p">
+        A number of issues were resolved that could result in serious errors
+        when encountered. The most critical or commonly encountered are
+        listed here.
+      </p>
+      <p class="p"><strong class="ph b">Bugs:</strong>
+
+
+
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2168" target="_blank">IMPALA-2168</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2378" target="_blank">IMPALA-2378</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2369" target="_blank">IMPALA-2369</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2357" target="_blank">IMPALA-2357</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2319" target="_blank">IMPALA-2319</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2314" target="_blank">IMPALA-2314</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2016" target="_blank">IMPALA-2016</a>
+      </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title64" id="fixed_issues_230__correctness_230">
+      <h3 class="title topictitle3" id="ariaid-title64">Fixes for Correctness Errors</h3>
+      <div class="body conbody">
+      <p class="p">
+        A number of issues were resolved that could result in wrong results
+        when encountered. The most critical or commonly encountered are
+        listed here.
+      </p>
+      <p class="p"><strong class="ph b">Bugs:</strong>
+
+
+
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2192" target="_blank">IMPALA-2192</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2440" target="_blank">IMPALA-2440</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2090" target="_blank">IMPALA-2090</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2086" target="_blank">IMPALA-2086</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1947" target="_blank">IMPALA-1947</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1917" target="_blank">IMPALA-1917</a>
+      </p>
+      </div>
+    </article>
+
+  </article>
+
+
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title65" id="fixed_issues__fixed_issues_2210">
+
+    <h2 class="title topictitle2" id="ariaid-title65">Issues Fixed in <span class="keyword">Impala 2.2.10</span></h2>
+
+    <div class="body conbody">
+      <p class="p"></p>
+    </div>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title66" id="fixed_issues__fixed_issues_229">
+
+    <h2 class="title topictitle2" id="ariaid-title66">Issues Fixed in <span class="keyword">Impala 2.2.9</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        This section lists the most frequently encountered customer issues fixed in <span class="keyword">Impala 2.2.9</span>.
+      </p>
+
+    </div>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title67" id="fixed_issues_229__IMPALA-1917">
+      
+      <h3 class="title topictitle3" id="ariaid-title67">Query return empty result if it contains NullLiteral in inlineview</h3>
+      <div class="body conbody">
+      <p class="p">
+        If an inline view in a <code class="ph codeph">FROM</code> clause contained a <code class="ph codeph">NULL</code> literal,
+        the result set was empty.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1917" target="_blank">IMPALA-1917</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title68" id="fixed_issues_229__IMPALA-2731">
+      
+      <h3 class="title topictitle3" id="ariaid-title68">HBase scan node uses 2-4x memory after upgrade to Impala 2.2.8</h3>
+      <div class="body conbody">
+      <p class="p">
+        Queries involving HBase tables used substantially more memory than in earlier Impala versions.
+        The problem occurred starting in Impala 2.2.8, as a result of the changes for IMPALA-2284.
+        The fix for this issue involves removing a separate memory work area for HBase queries
+        and reusing other memory that was already allocated.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2731" target="_blank">IMPALA-2731</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title69" id="fixed_issues_229__IMPALA-1459">
+      <h3 class="title topictitle3" id="ariaid-title69">Fix migration/assignment of On-clause predicates inside inline views</h3>
+      <div class="body conbody">
+      
+      <p class="p">
+        Some combinations of <code class="ph codeph">ON</code> clauses in join queries could result in comparisons
+        being applied at the wrong stage of query processing, leading to incorrect results.
+        Wrong predicate assignment could happen under the following conditions:
+      </p>
+      <ul class="ul">
+        <li class="li">
+          The query includes an inline view that contains an outer join.
+        </li>
+        <li class="li">
+          That inline view is joined with another table in the enclosing query block.
+        </li>
+        <li class="li">
+          That join has an <code class="ph codeph">ON</code> clause containing a predicate that
+          only references columns originating from the outer-joined tables inside the inline view.
+        </li>
+      </ul>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1459" target="_blank">IMPALA-1459</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title70" id="fixed_issues_229__IMPALA-2446">
+      <h3 class="title topictitle3" id="ariaid-title70">Fix wrong predicate assignment in outer joins</h3>
+      <div class="body conbody">
+      <p class="p">
+        The join predicate for an <code class="ph codeph">OUTER JOIN</code> clause could be applied at the wrong stage
+        of query processing, leading to incorrect results.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2446" target="_blank">IMPALA-2446</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title71" id="fixed_issues_229__IMPALA-2648">
+      <h3 class="title topictitle3" id="ariaid-title71">Avoid sending large partition stats objects over thrift</h3>
+      <div class="body conbody">
+      <p class="p"> The <span class="keyword cmdname">catalogd</span> daemon could encounter a serious error when loading the
+          incremental statistics metadata for tables with large numbers of partitions and columns.
+          The problem occurred when the internal representation of metadata for the table exceeded 2
+          GB, for example in a table with 20K partitions and 77 columns. The fix causes a
+            <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> operation to fail if it would produce
+          metadata that exceeded the maximum size. </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2648" target="_blank">IMPALA-2648</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2664" target="_blank">IMPALA-2664</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title72" id="fixed_issues_229__IMPALA-1675">
+      <h3 class="title topictitle3" id="ariaid-title72">Avoid overflow when adding large intervals to TIMESTAMPs</h3>
+      <div class="body conbody">
+      <p class="p"> Adding or subtracting a large <code class="ph codeph">INTERVAL</code> value to a
+            <code class="ph codeph">TIMESTAMP</code> value could produce an incorrect result, with the value
+          wrapping instead of returning an out-of-range error. </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1675" target="_blank">IMPALA-1675</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title73" id="fixed_issues_229__IMPALA-1949">
+      <h3 class="title topictitle3" id="ariaid-title73">Analysis exception when a binary operator contains an IN operator with values</h3>
+      <div class="body conbody">
+      <p class="p">
+        An <code class="ph codeph">IN</code> operator with literal values could cause a statement to fail if used
+        as the argument to a binary operator, such as an equality test for a <code class="ph codeph">BOOLEAN</code> value.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1949" target="_blank">IMPALA-1949</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title74" id="fixed_issues_229__IMPALA-2273">
+    
+      <h3 class="title topictitle3" id="ariaid-title74">Make MAX_PAGE_HEADER_SIZE configurable</h3>
+      <div class="body conbody">
+      <p class="p"> Impala could fail to access Parquet data files with page headers larger than 8 MB, which
+          could occur, for example, if the minimum or maximum values for a column were long strings.
+          The fix adds a configuration setting <code class="ph codeph">--max_page_header_size</code>, which you
+          can use to increase the Impala size limit to a value higher than 8 MB. </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2273" target="_blank">IMPALA-2273</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title75" id="fixed_issues_229__IMPALA-2357">
+      <h3 class="title topictitle3" id="ariaid-title75">Fix spilling sorts with var-len slots that are NULL or empty.</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query that activated the spill-to-disk mechanism could fail if it contained a sort expression
+        involving certain combinations of fixed-length or variable-length types.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2357" target="_blank">IMPALA-2357</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title76" id="fixed_issues_229__block_pin_oom">
+      <h3 class="title topictitle3" id="ariaid-title76">Work-around IMPALA-2344: Fail query with OOM in case block-&gt;Pin() fails</h3>
+      <div class="body conbody">
+      <p class="p">
+        Some queries that activated the spill-to-disk mechanism could produce a serious error
+        if there was insufficient memory to set up internal work areas. Now those queries
+        produce normal out-of-memory errors instead.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2344" target="_blank">IMPALA-2344</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title77" id="fixed_issues_229__IMPALA-2252">
+      <h3 class="title topictitle3" id="ariaid-title77">Crash (likely race) tearing down BufferedBlockMgr on query failure</h3>
+      <div class="body conbody">
+      <p class="p">
+        A serious error could occur under rare circumstances, due to a race condition while freeing memory during heavily concurrent workloads.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2252" target="_blank">IMPALA-2252</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title78" id="fixed_issues_229__IMPALA-1746">
+      <h3 class="title topictitle3" id="ariaid-title78">QueryExecState doesn't check for query cancellation or errors</h3>
+      <div class="body conbody">
+      <p class="p">
+        A call to <code class="ph codeph">SetError()</code> in a user-defined function (UDF) would not cause the query to fail as expected.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1746" target="_blank">IMPALA-1746</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title79" id="fixed_issues_229__IMPALA-2533">
+      <h3 class="title topictitle3" id="ariaid-title79">Impala throws IllegalStateException when inserting data into a partition while select
+        subquery group by partition columns</h3>
+      <div class="body conbody">
+      <p class="p">
+        An <code class="ph codeph">INSERT ... SELECT</code> operation into a partitioned table could fail if the <code class="ph codeph">SELECT</code> query
+        included a <code class="ph codeph">GROUP BY</code> clause referring to the partition key columns.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2533" target="_blank">IMPALA-2533</a></p>
+      </div>
+    </article>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title80" id="fixed_issues__fixed_issues_228">
+
+    <h2 class="title topictitle2" id="ariaid-title80">Issues Fixed in <span class="keyword">Impala 2.2.8</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        This section lists the most frequently encountered customer issues fixed in <span class="keyword">Impala 2.2.8</span>.
+      </p>
+
+    </div>
+
+
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title81" id="fixed_issues_228__IMPALA-1136">
+      <h3 class="title topictitle3" id="ariaid-title81">Impala is unable to read hive tables created with the "STORED AS AVRO" clause</h3>
+      <div class="body conbody">
+      <p class="p">Impala could not read Avro tables created in Hive with the <code class="ph codeph">STORED AS AVRO</code> clause.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1136" target="_blank">IMPALA-1136</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2161" target="_blank">IMPALA-2161</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title82" id="fixed_issues_228__IMPALA-2213">
+      <h3 class="title topictitle3" id="ariaid-title82">make Parquet scanner fail query if the file size metadata is stale</h3>
+      <div class="body conbody">
+      <p class="p">If a Parquet file in HDFS was overwritten by a smaller file, Impala could encounter a serious error.
+      Issuing a <code class="ph codeph">INVALIDATE METADATA</code> statement before a subsequent query would avoid the error.
+      The fix allows Impala to handle such inconsistencies in Parquet file length cleanly regardless of whether the
+      table metadata is up-to-date.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2213" target="_blank">IMPALA-2213</a></p>
+      </div>
+    </article>
+
+     <article class="topic concept nested2" aria-labelledby="ariaid-title83" id="fixed_issues_228__IMPALA-2249">
+      <h3 class="title topictitle3" id="ariaid-title83">Avoid allocating StringBuffer &gt; 1GB in ScannerContext::Stream::GetBytesInternal()</h3>
+      <div class="body conbody">
+      <p class="p">Impala could encounter a serious error when reading compressed text files larger than 1 GB. The fix causes Impala
+      to issue an error message instead in this case.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2249" target="_blank">IMPALA-2249</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title84" id="fixed_issues_228__IMPALA-2284">
+      <h3 class="title topictitle3" id="ariaid-title84">Disallow long (1&lt;&lt;30) strings in group_concat()</h3>
+      <div class="body conbody">
+      <p class="p">A query using the <code class="ph codeph">group_concat()</code> function could encounter a serious error if the returned string value was larger than 1 GB.
+      Now the query fails with an error message in this case.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2284" target="_blank">IMPALA-2284</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title85" id="fixed_issues_228__IMPALA-2270">
+      <h3 class="title topictitle3" id="ariaid-title85">avoid FnvHash64to32 with empty inputs</h3>
+      <div class="body conbody">
+      <p class="p">An edge case in the algorithm used to distribute data among nodes could result in uneven distribution of work for some queries,
+      with all data sent to the same node.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2270" target="_blank">IMPALA-2270</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title86" id="fixed_issues_228__IMPALA-2348">
+      <h3 class="title topictitle3" id="ariaid-title86">The catalog does not close the connection to HMS during table invalidation</h3>
+      <div class="body conbody">
+      <p class="p">A communication error could occur between Impala and the Hive metastore database, causing Impala operations that update
+      table metadata to fail.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2348" target="_blank">IMPALA-2348</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title87" id="fixed_issues_228__IMPALA-2364-548">
+      <h3 class="title topictitle3" id="ariaid-title87">Wrong DCHECK in PHJ::ProcessProbeBatch</h3>
+      <div class="body conbody">
+      <p class="p">Certain queries could encounter a serious error if the spill-to-disk mechanism was activated.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2364" target="_blank">IMPALA-2364</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title88" id="fixed_issues_228__IMPALA-2165-548">
+      <h3 class="title topictitle3" id="ariaid-title88">Avoid cardinality 0 in scan nodes of small tables and low selectivity</h3>
+      <div class="body conbody">
+      <p class="p">Impala could generate a suboptimal query plan for some queries involving small tables.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2165" target="_blank">IMPALA-2165</a></p>
+      </div>
+    </article>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title89" id="fixed_issues__fixed_issues_227">
+
+    <h2 class="title topictitle2" id="ariaid-title89">Issues Fixed in <span class="keyword">Impala 2.2.7</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        This section lists the most frequently encountered customer issues fixed in <span class="keyword">Impala 2.2.7</span>.
+      </p>
+
+    </div>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title90" id="fixed_issues_227__IMPALA-1983">
+      <h3 class="title topictitle3" id="ariaid-title90">Warn if table stats are potentially corrupt.</h3>
+      <div class="body conbody">
+      <p class="p">
+        Impala warns if it detects a discrepancy in table statistics: a table considered to have zero rows even though there are data files present.
+        In this case, Impala also skips query optimizations that are normally applied to very small tables.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1983" target="_blank">IMPALA-1983:</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title91" id="fixed_issues_227__IMPALA-2266">
+      <h3 class="title topictitle3" id="ariaid-title91">Pass correct child node in 2nd phase merge aggregation.</h3>
+      <div class="body conbody">
+      <p class="p">A query could encounter a serious error if it included a particular combination of aggregate functions and inline views.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2266" target="_blank">IMPALA-2266</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title92" id="fixed_issues_227__IMPALA-2216">
+      <h3 class="title topictitle3" id="ariaid-title92">Set the output smap of an EmptySetNode produced from an empty inline view.</h3>
+      <div class="body conbody">
+      <p class="p">A query could encounter a serious error if it included an inline view whose subquery had no <code class="ph codeph">FROM</code> clause.</p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2216" target="_blank">IMPALA-2216</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title93" id="fixed_issues_227__IMPALA-2203">
+      <h3 class="title topictitle3" id="ariaid-title93">Set an InsertStmt's result exprs from the source statement's result exprs.</h3>
+      <div class="body conbody">
+      <p class="p">
+      A <code class="ph codeph">CREATE TABLE AS SELECT</code> or <code class="ph codeph">INSERT ... SELECT</code> statement could produce
+      different results than a <code class="ph codeph">SELECT</code> statement, for queries including a <code class="ph codeph">FULL JOIN</code> clause
+      and including literal values in the select list.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2203" target="_blank">IMPALA-2203</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title94" id="fixed_issues_227__IMPALA-2088">
+      <h3 class="title topictitle3" id="ariaid-title94">Fix planning of empty union operands with analytics.</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query could return incorrect results if it contained a <code class="ph codeph">UNION</code> clause,
+        calls to analytic functions, and a constant expression that evaluated to <code class="ph codeph">FALSE</code>.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2088" target="_blank">IMPALA-2088</a></p>
+      </div>
+    </article>
+
+
+
+
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title95" id="fixed_issues_227__IMPALA-2089">
+      <h3 class="title topictitle3" id="ariaid-title95">Retain eq predicates bound by grouping slots with complex grouping exprs.</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query containing an <code class="ph codeph">INNER JOIN</code> clause could return undesired rows.
+        Some predicate specified in the <code class="ph codeph">ON</code> clause could be omitted from the filtering operation.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2089" target="_blank">IMPALA-2089</a></p>
+      </div>
+    </article>
+
+
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title96" id="fixed_issues_227__IMPALA-2199">
+      <h3 class="title topictitle3" id="ariaid-title96">Row count not set for empty partition when spec is used with compute incremental stats</h3>
+      <div class="body conbody">
+      <p class="p">
+        A <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> statement could leave the row count for an emptyp partition as -1,
+        rather than initializing the row count to 0. The missing statistic value could result in reduced query performance.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2199" target="_blank">IMPALA-2199</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title97" id="fixed_issues_227__IMPALA-1898">
+      <h3 class="title topictitle3" id="ariaid-title97">Explicit aliases + ordinals analysis bug</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query could encounter a serious error if it included column aliases with the same names as table columns, and used
+        ordinal numbers in an <code class="ph codeph">ORDER BY</code> or <code class="ph codeph">GROUP BY</code> clause.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1898" target="_blank">IMPALA-1898</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title98" id="fixed_issues_227__IMPALA-1987">
+      <h3 class="title topictitle3" id="ariaid-title98">Fix TupleIsNullPredicate to return false if no tuples are nullable.</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query could return incorrect results if it included an outer join clause, inline views, and calls to functions such as <code class="ph codeph">coalesce()</code>
+        that can generate <code class="ph codeph">NULL</code> values.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1987" target="_blank">IMPALA-1987</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title99" id="fixed_issues_227__IMPALA-2178">
+      <h3 class="title topictitle3" id="ariaid-title99">fix Expr::ComputeResultsLayout() logic</h3>
+      <div class="body conbody">
+      <p class="p">
+        A query could return incorrect results if the table contained multiple <code class="ph codeph">CHAR</code> columns with length of 2 or less,
+        and the query included a <code class="ph codeph">GROUP BY</code> clause that referred to multiple such columns.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2178" target="_blank">IMPALA-2178</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title100" id="fixed_issues_227__IMPALA-1737">
+      <h3 class="title topictitle3" id="ariaid-title100">Substitute an InsertStmt's partition key exprs with the root node's smap.</h3>
+      <div class="body conbody">
+      <p class="p">
+        An <code class="ph codeph">INSERT</code> statement could encounter a serious error if the <code class="ph codeph">SELECT</code>
+        portion called an analytic function.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1737" target="_blank">IMPALA-1737</a></p>
+      </div>
+    </article>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title101" id="fixed_issues__fixed_issues_225">
+
+    <h2 class="title topictitle2" id="ariaid-title101">Issues Fixed in Impala <span class="keyword">Impala 2.2.5</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        This section lists the most frequently encountered customer issues fixed in <span class="keyword">Impala 2.2.5</span>.
+      </p>
+
+    </div>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title102" id="fixed_issues_225__IMPALA-2048">
+      <h3 class="title topictitle3" id="ariaid-title102">Impala DML/DDL operations corrupt table metadata leading to Hive query failures</h3>
+      <div class="body conbody">
+      <p class="p">
+        When the Impala <code class="ph codeph">COMPUTE STATS</code> statement was run on a partitioned Parquet table that was created in Hive, the table subsequently became inaccessible in Hive.
+        The table was still accessible to Impala. Regaining access in Hive required a workaround of creating a new table. The error displayed in Hive was:
+      </p>
+<pre class="pre codeblock"><code>Error: Error while compiling statement: FAILED: SemanticException Class not found: org.apache.impala.hive.serde.ParquetInputFormat (state=42000,code=40000)</code></pre>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2048" target="_blank">IMPALA-2048</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title103" id="fixed_issues_225__IMPALA-1929">
+      <h3 class="title topictitle3" id="ariaid-title103">Avoiding a DCHECK of NULL hash table in spilled right joins</h3>
+      
+      <div class="body conbody">
+      <p class="p">
+        A query could encounter a serious error if it contained a <code class="ph codeph">RIGHT OUTER</code>, <code class="ph codeph">RIGHT ANTI</code>, or <code class="ph codeph">FULL OUTER</code> join clause
+        and approached the memory limit on a host so that the <span class="q">"spill to disk"</span> mechanism was activated.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1929" target="_blank">IMPALA-1929</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title104" id="fixed_issues_225__IMPALA-2136">
+      <h3 class="title topictitle3" id="ariaid-title104">Bug in PrintTColumnValue caused wrong stats for TINYINT partition cols</h3>
+      
+      <div class="body conbody">
+      <p class="p">
+        Declaring a partition key column as a <code class="ph codeph">TINYINT</code> caused problems with the <code class="ph codeph">COMPUTE STATS</code> statement.
+        The associated partitions would always have zero estimated rows, leading to potential inefficient query plans.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2136" target="_blank">IMPALA-2136</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title105" id="fixed_issues_225__IMPALA-2018">
+      <h3 class="title topictitle3" id="ariaid-title105">Where clause does not propagate to joins inside nested views</h3>
+      
+      <div class="body conbody">
+      <p class="p">
+        A query that referred to a view whose query referred to another view containing a join, could return incorrect results.
+        <code class="ph codeph">WHERE</code> clauses for the outermost query were not always applied, causing the result
+        set to include additional rows that should have been filtered out.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2018" target="_blank">IMPALA-2018</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title106" id="fixed_issues_225__IMPALA-2064">
+      <h3 class="title topictitle3" id="ariaid-title106">Add effective_user() builtin</h3>
+      
+      <div class="body conbody">
+      <p class="p">
+        The <code class="ph codeph">user()</code> function returned the name of the logged-in user, which might not be the
+        same as the user name being checked for authorization if, for example, delegation was enabled.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2064" target="_blank">IMPALA-2064</a></p>
+      <p class="p"><strong class="ph b">Resolution:</strong> Rather than change the behavior of the <code class="ph codeph">user()</code> function,
+      the fix introduces an additional function <code class="ph codeph">effective_user()</code> that returns the user name that is checked during authorization.</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title107" id="fixed_issues_225__IMPALA-2125">
+      <h3 class="title topictitle3" id="ariaid-title107">Make UTC to local TimestampValue conversion faster.</h3>
+      
+      <div class="body conbody">
+      <p class="p">
+        Query performance was improved substantially for Parquet files containing <code class="ph codeph">TIMESTAMP</code>
+        data written by Hive, when the <code class="ph codeph">-convert_legacy_hive_parquet_utc_timestamps=true</code> setting
+        is in effect.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2125" target="_blank">IMPALA-2125</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title108" id="fixed_issues_225__IMPALA-2065">
+      <h3 class="title topictitle3" id="ariaid-title108">Workaround IMPALA-1619 in BufferedBlockMgr::ConsumeMemory()</h3>
+      
+      <div class="body conbody">
+      <p class="p">
+        A join query could encounter a serious error if the query
+        approached the memory limit on a host so that the <span class="q">"spill to disk"</span> mechanism was activated,
+        and data volume in the join was large enough that an internal memory buffer exceeded 1 GB in size on a particular host.
+        (Exceeding this limit would only happen for huge join queries, because Impala could split this intermediate data
+        into 16 parts during the join query, and the buffer only contains compact bookkeeping data rather than the actual
+        join column data.)
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2065" target="_blank">IMPALA-2065</a></p>
+      </div>
+    </article>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title109" id="fixed_issues__fixed_issues_223">
+
+    <h2 class="title topictitle2" id="ariaid-title109">Issues Fixed in <span class="keyword">Impala 2.2.3</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        This section lists the most frequently encountered customer issues fixed in <span class="keyword">Impala 2.2.3</span>.
+      </p>
+
+    </div>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title110" id="fixed_issues_223__isilon_support">
+      <h3 class="title topictitle3" id="ariaid-title110">Enable using Isilon as the underlying filesystem.</h3>
+      <div class="body conbody">
+      <p class="p">
+        Enabling Impala to work with the Isilon filesystem involves a number of
+        fixes to performance and flexibility for dealing with I/O using remote reads.
+        See <a class="xref" href="impala_isilon.html#impala_isilon">Using Impala with Isilon Storage</a> for details on using Impala and Isilon together.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1968" target="_blank">IMPALA-1968</a>,
+      <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1730" target="_blank">IMPALA-1730</a></p>
+      </div>
+    </article>
+
+
+
+
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title111" id="fixed_issues_223__IMPALA-1381">
+      <h3 class="title topictitle3" id="ariaid-title111">Expand set of supported timezones.</h3>
+      <div class="body conbody">
+      <p class="p">
+        The set of timezones recognized by Impala was expanded.
+        You can always find the latest list of supported timezones in the
+        Impala source code, in the file
+        <a class="xref" href="https://github.com/apache/incubator-impala/blob/master/be/src/exprs/timezone_db.cc" target="_blank">timezone_db.cc</a>.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1381" target="_blank">IMPALA-1381</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title112" id="fixed_issues_223__IMPALA-1963">
+      <h3 class="title topictitle3" id="ariaid-title112">Impala Timestamp ISO-8601 Support.</h3>
+      <div class="body conbody">
+      <p class="p">
+        Impala can now process <code class="ph codeph">TIMESTAMP</code> literals including a trailing <code class="ph codeph">z</code>,
+        signifying <span class="q">"Zulu"</span> time, a synonym for UTC.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1963" target="_blank">IMPALA-1963</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title113" id="fixed_issues_223__IMPALA-2008">
+      <h3 class="title topictitle3" id="ariaid-title113">Fix wrong warning when insert overwrite to empty table</h3>
+      <div class="body conbody">
+      <p class="p">
+        An <code class="ph codeph">INSERT OVERWRITE</code> operation would encounter an error
+        if the <code class="ph codeph">SELECT</code> portion of the statement returned zero
+        rows, such as with a <code class="ph codeph">LIMIT 0</code> clause.
+      </p>
+      <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2008" target="_blank">IMPALA-2008</a></p>
+      </div>
+    </article>
+
+    <article class="topic concept nested2" aria-labelledby="ariaid-title114" id="fixed_issues_223__IMPALA-1952">
+    
+    
+      <h3 class="title topictitle3" id="ariaid-title114">Expand parsing of decimals to include scientific notation</h3>
+      <div class="body conbody">
+      <p class="p">
+        <code class="ph codeph">DECIMAL</code> literals can now include <code class="ph codeph">e</code> scientific notati

<TRUNCATED>


Mime
View raw message