[teiid-commits] teiid SVN: r3649 - in trunk: documentation/reference/src/main/docbook/en-US/content and 1 other directory.

[teiid-commits at lists.jboss.org]

Author: rareddy
Date: 2011-11-14 22:38:35 -0500 (Mon, 14 Nov 2011)
New Revision: 3649

Modified:
   trunk/build/kits/jboss-container/teiid-releasenotes.html
   trunk/documentation/reference/src/main/docbook/en-US/content/translators.xml
Log:
TEIID-1810: Adding Hive translator document

Modified: trunk/build/kits/jboss-container/teiid-releasenotes.html
===================================================================
--- trunk/build/kits/jboss-container/teiid-releasenotes.html	2011-11-15 01:42:44 UTC (rev 3648)
+++ trunk/build/kits/jboss-container/teiid-releasenotes.html	2011-11-15 03:38:35 UTC (rev 3649)
@@ -38,7 +38,8 @@
   <LI><B>View removal hint</B> - the NO_UNNEST hint now also applies to from clause views and subqueries.  It will instruct the planner to not perform view flattening.
   <LI><B>Non-blocking statement execution</B> - Teiid JDBC extensions TeiidStatement and TeiidPreparedStatement can be used to submit queries against embedded connections with a callback to process results in a non-blocking manner.
   <LI><B>NON_STRICT limit hint</B> - the NON_STRICT hint can be used with unordered limits to tell the optimizer to not inhibit push operations even if the results will not be consistent with the logical application of the limit.
-  <LI><B>Source Hints</B> - user and transformation queries can specify a meta source hint, e.g. SELECT /*+ sh my-oracle:'leading' */ * FROM TBL.  The hint information will be passed to the passed to the translator.  The Oracle translator will by default treat the source hint as an Oracle hint. 
+  <LI><B>Source Hints</B> - user and transformation queries can specify a meta source hint, e.g. SELECT /*+ sh my-oracle:'leading' */ * FROM TBL.  The hint information will be passed to the passed to the translator.  The Oracle translator will by default treat the source hint as an Oracle hint.
+  <LI><B>Hive Translator</B> - Hive translator has been added as technology preview.  
 </UL>
 
 <h2><a name="Compatibility">Compatibility Issues</a></h2>

Modified: trunk/documentation/reference/src/main/docbook/en-US/content/translators.xml
===================================================================
--- trunk/documentation/reference/src/main/docbook/en-US/content/translators.xml	2011-11-15 01:42:44 UTC (rev 3648)
+++ trunk/documentation/reference/src/main/docbook/en-US/content/translators.xml	2011-11-15 03:38:35 UTC (rev 3649)
@@ -259,8 +259,18 @@
                 </listitem>
                 <listitem>
                     <para>
-                    <emphasis>hive</emphasis> - For use with Hive database based on Hadoop
+                    <emphasis>hive</emphasis> - For use with Hive database based on Hadoop. Hive is a data warehousing 
+                    infrastructure based on the Hadoop. Hadoop provides massive scale out and fault tolerance capabilities 
+                    for data storage and processing (using the map-reduce programming paradigm) on commodity hardware.
                     </para>
+                    <para>Hive has limited support for data types as it supports integer varients, boolean, float, 
+                    double and string. It is does not have native support for time based types, xml or LOBs. These limitations
+                    are reflected in the translator capabilities. The view table can use these types, however the tranformation
+                    would need to specify the necessary transformations. Note that in those situations, the evaluations will be
+                    done in Teiid engine. Another limitation Hive has is, it only supports EQUI join, so using any other joins types
+                    on its source tables will result in in-effiecient queries. Currently there is no tooling support for metadata 
+                    import from Hive in Designer. To write criteria based on partitioned columns, they can be modeled 
+                    on source table, but do not include in selection columns.</para>
                 </listitem>
                 <listitem>
                     <para>