<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Impala table definition in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Impala-table-definition/m-p/66672#M13691</link>
    <description>&lt;P&gt;1. you can go ahead create external table directly to impala , i dont see any issue in there .&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; Use external table when multiple client tool want to have a centeralized data i, you have to decided whether your external table data&amp;nbsp; is going to be used by another external program outside hdfs for example pig etc&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. that totally depends on the future requirement but mostly people prefer&amp;nbsp; timestamps over string format when it comes to dates.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;note&amp;nbsp; - lo&lt;SPAN&gt;ading data into Parquet tables is a memory-intensive operation , you got to keep an eye on it .&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 24 Apr 2018 11:03:17 GMT</pubDate>
    <dc:creator>csguna</dc:creator>
    <dc:date>2018-04-24T11:03:17Z</dc:date>
  </channel>
</rss>

