IMPALA-6627: [DOCS] Hive incompatibility with serialization.null.format

Change-Id: Ic412c2fe2eba03d4493defee497656d6c74936f3
Reviewed-on: http://gerrit.cloudera.org:8080/9563
Reviewed-by: Alex Behm <alex.b...@cloudera.com>
Tested-by: Impala Public Jenkins


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

Branch: refs/heads/master
Commit: 6c264d8eb8b0973bc50fe32c0a18f6c011a00028
Parents: 4e12ba6
Author: Alex Rodoni <arod...@cloudera.com>
Authored: Thu Mar 8 19:11:50 2018 -0800
Committer: Impala Public Jenkins <impala-public-jenk...@gerrit.cloudera.org>
Committed: Sat Mar 10 01:31:13 2018 +0000

----------------------------------------------------------------------
 docs/topics/impala_langref_unsupported.xml | 8 ++++++++
 1 file changed, 8 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/impala/blob/6c264d8e/docs/topics/impala_langref_unsupported.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_langref_unsupported.xml 
b/docs/topics/impala_langref_unsupported.xml
index e1bcc68..effb1a8 100644
--- a/docs/topics/impala_langref_unsupported.xml
+++ b/docs/topics/impala_langref_unsupported.xml
@@ -185,6 +185,14 @@ under the License.
           with an Impala table.
         </li>
       </ul>
+      <p>
+        Impala respects the <codeph>serialization.null.format</codeph> table
+        property only for TEXT tables and ignores the property for Parquet and
+        other formats. Hive respects the 
<codeph>serialization.null.format</codeph>
+        property for Parquet and other formats and converts matching values
+        to NULL during the scan. See <xref keyref="text_data_files"/> for
+        using the table property in Impala.
+      </p>
     </conbody>
   </concept>
 

Reply via email to