Repository: incubator-impala
Updated Branches:
  refs/heads/master cde19ab8c -> ecda49f3e


[DOCS] Add several items to "known issues" page

IMPALA-4432 is actually an incompatible change, so it gets
listed on the separate "Incompatible Changes" page.
Change-Id: Ibeed92e8f6603b858622b1d397d1f5cad810f4cf
Reviewed-on: http://gerrit.cloudera.org:8080/5809
Reviewed-by: Tim Armstrong <[email protected]>
Reviewed-by: Sailesh Mukil <[email protected]>
Reviewed-by: Michael Brown <[email protected]>
Tested-by: Impala Public Jenkins


Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/95c74b7c
Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/95c74b7c
Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/95c74b7c

Branch: refs/heads/master
Commit: 95c74b7c9d04bff84dd03275cc9137a8c6395bf8
Parents: cde19ab
Author: John Russell <[email protected]>
Authored: Fri Jan 27 10:03:47 2017 -0800
Committer: Impala Public Jenkins <[email protected]>
Committed: Fri Jun 2 15:32:14 2017 +0000

----------------------------------------------------------------------
 docs/topics/impala_incompatible_changes.xml | 14 +++-
 docs/topics/impala_known_issues.xml         | 94 +++++++++++++++++++++++-
 2 files changed, 106 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/95c74b7c/docs/topics/impala_incompatible_changes.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_incompatible_changes.xml 
b/docs/topics/impala_incompatible_changes.xml
index 3878c51..a21e026 100644
--- a/docs/topics/impala_incompatible_changes.xml
+++ b/docs/topics/impala_incompatible_changes.xml
@@ -152,9 +152,21 @@ under the License.
             The replication factor for Kudu tables must be an odd number.
           </p>
         </li>
+        <li>
+          <p rev="IMPALA-4432">
+            A UDF compiled into an LLVM IR bitcode module 
(<codeph>.bc</codeph>) might
+            encounter a runtime error when native code generation is turned 
off by
+            setting the query option <codeph>DISABLE_CODEGEN=1</codeph>.
+            This issue also applies when running a built-in or native UDF with
+            more than 20 arguments.
+            See <xref keyref="IMPALA-4432">IMPALA-4432</xref> for details.
+            As a workaround, either turn native code generation back on with 
the query option
+            <codeph>DISABLE_CODEGEN=0</codeph>, or use the regular UDF 
compilation path
+            that does not produce an IR module.
+          </p>
+        </li>
       </ul>
     </conbody>
-
   </concept>
 
   <concept rev="2.7.0" id="incompatible_changes_27x">

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/95c74b7c/docs/topics/impala_known_issues.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_known_issues.xml 
b/docs/topics/impala_known_issues.xml
index d13d23a..75c9d2d 100644
--- a/docs/topics/impala_known_issues.xml
+++ b/docs/topics/impala_known_issues.xml
@@ -62,7 +62,7 @@ under the License.
       <conbody>
         <p>
         </p>
-        <p><b>Bug:</b> <xref keyref="" scope="external" 
format="html"></xref></p>
+        <p><b>Bug:</b> <xref keyref=""></xref></p>
         <p><b>Severity:</b> High</p>
         <p><b>Resolution:</b> </p>
         <p><b>Workaround:</b> </p>
@@ -183,6 +183,19 @@ https://issues.apache.org/jira/browse/IMPALA-2144 - Don't 
have
 
       </conbody>
 
+    <concept id="IMPALA-4595">
+      <title>Linking IR UDF module to main module crashes Impala</title>
+      <conbody>
+        <p>
+          A UDF compiled as an LLVM module (<codeph>.ll</codeph>) could cause 
a crash
+          when executed.
+        </p>
+        <p><b>Bug:</b> <xref keyref="IMPALA-4595">IMPALA-4595</xref></p>
+        <p><b>Severity:</b> High</p>
+        <p><b>Resolution:</b> Fixed in <keyword keyref="impala28_full"/> and 
higher.</p>
+        <p><b>Workaround:</b> Compile the external UDFs to a 
<codeph>.so</codeph> library instead of a
+          <codeph>.ll</codeph> IR module.</p>
+      </conbody>
     </concept>
 
     <concept id="IMPALA-3069" rev="IMPALA-3069">
@@ -332,6 +345,21 @@ https://issues.apache.org/jira/browse/IMPALA-2144 - Don't 
have
 
     </conbody>
 
+    <concept id="IMPALA-4570">
+      <title>Impala shell tarball is not usable on systems with setuptools 
versions where '0.7' is a substring of the full version string</title>
+      <conbody>
+        <p>
+          For example, this issue could occur on a system using setuptools 
version 20.7.0.
+        </p>
+        <p><b>Bug:</b> <xref keyref="IMPALA-4570">IMPALA-4570</xref></p>
+        <p><b>Severity:</b> High</p>
+        <p><b>Resolution:</b> Fixed in <keyword keyref="impala28_full"/> and 
higher.</p>
+        <p><b>Workaround:</b> Change to a setuptools version that does not 
have <codeph>0.7</codeph> as
+          a substring.
+        </p>
+      </conbody>
+    </concept>
+
     <concept id="IMPALA-3133" rev="IMPALA-3133">
 
       <title>Unexpected privileges in show output</title>
@@ -536,6 +564,20 @@ https://issues.apache.org/jira/browse/IMPALA-2144 - Don't 
have
 
     </conbody>
 
+    <concept id="drop_table_purge_s3a">
+      <title>DROP TABLE PURGE on S3A table may not delete externally written 
files</title>
+      <conbody>
+        <p>
+          A <codeph>DROP TABLE PURGE</codeph> statement against an S3 table 
could leave the data files
+          behind, if the table directory and the data files were created with 
a combination of
+          <cmdname>hadoop fs</cmdname> and <cmdname>aws s3</cmdname> commands.
+        </p>
+        <p><b>Bug:</b> <xref keyref="IMPALA-3558">IMPALA-3558</xref></p>
+        <p><b>Severity:</b> High</p>
+        <p><b>Resolution:</b> The underlying issue with the S3A connector 
depends on the resolution of <xref 
href="https://issues.apache.org/jira/browse/HADOOP-13230"; format="html" 
scope="external">HADOOP-13230</xref>.</p>
+      </conbody>
+    </concept>
+
     <concept id="catalogd_heap">
 
       <title>Impala catalogd heap issues when upgrading to <keyword 
keyref="impala25"/></title>
@@ -744,6 +786,40 @@ https://issues.apache.org/jira/browse/IMPALA-2144 - Don't 
have
 
     </conbody>
 
+    <concept id="IMPALA-4513">
+      <title>ABS(n) where n is the lowest bound for the int types returns 
negative values</title>
+      <conbody>
+        <p>
+          If the <codeph>abs()</codeph> function evaluates a number that is 
right at the lower bound for
+          an integer data type, the positive result cannot be represented in 
the same type, and the
+          result is returned as a negative number. For example, 
<codeph>abs(-128)</codeph> returns -128
+          because the argument is interpreted as a <codeph>TINYINT</codeph> 
and the return value is also
+          a <codeph>TINYINT</codeph>.
+        </p>
+        <p><b>Bug:</b> <xref keyref="IMPALA-4513">IMPALA-4513</xref></p>
+        <p><b>Severity:</b> High</p>
+        <p><b>Workaround:</b> Cast the integer value to a larger type. For 
example, rewrite
+          <codeph>abs(<varname>tinyint_col</varname>)</codeph> as 
<codeph>abs(cast(<varname>tinyint_col</varname> as smallint))</codeph>.</p>
+      </conbody>
+    </concept>
+
+    <concept id="IMPALA-4266">
+      <title>Java udf expression returning string in group by can give 
incorrect results.</title>
+      <conbody>
+        <p>
+          If the <codeph>GROUP BY</codeph> clause included a call to a Java 
UDF that returned a string value,
+          the UDF could return an incorrect result.
+        </p>
+        <p><b>Bug:</b> <xref keyref="IMPALA-4266">IMPALA-4266</xref></p>
+        <p><b>Severity:</b> High</p>
+        <p><b>Resolution:</b> Fixed in <keyword keyref="impala28_full"/> and 
higher.</p>
+        <p><b>Workaround:</b> Rewrite the expression to concatenate the 
results of the Java UDF with an
+          empty string call. For example, rewrite 
<codeph>my_hive_udf()</codeph> as
+          <codeph>concat(my_hive_udf(), '')</codeph>.
+        </p>
+      </conbody>
+    </concept>
+
     <concept id="IMPALA-3084" rev="IMPALA-3084">
 
       <title>Incorrect assignment of NULL checking predicate through an outer 
join of a nested collection.</title>
@@ -1610,6 +1686,21 @@ ALTER TABLE table_name SET 
TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </conbody>
 
+    <concept id="IMPALA-4551">
+      <title>Set limits on size of expression trees</title>
+      <conbody>
+        <p>
+          Very deeply nested expressions within queries can exceed internal 
Impala limits,
+          leading to excessive memory usage.
+        </p>
+        <p><b>Bug:</b> <xref keyref="IMPALA-4551">IMPALA-4551</xref></p>
+        <p><b>Severity:</b> High</p>
+        <p><b>Resolution:</b> </p>
+        <p><b>Workaround:</b> Avoid queries with extremely large expression 
trees. Setting the query option
+          <codeph>disable_codegen=true</codeph> may reduce the impact, at a 
cost of longer query runtime.</p>
+      </conbody>
+    </concept>
+
     <concept id="IMPALA-77" rev="IMPALA-77">
 
 <!-- Not part of Alex's spreadsheet. Perhaps it really is a permanent 
limitation and nobody is tracking it? -->
@@ -1804,3 +1895,4 @@ ALTER TABLE table_name SET 
TBLPROPERTIES('EXTERNAL'='TRUE');
   </concept>
 
 </concept>
+</concept>

Reply via email to