title: Hive Managed Table vs External Table : LOCATION directory
body: <p>I have been going through some HIVE books and tutorials. One of the book - Hadoop in Practice says </p>
  
  <blockquote>
    <p>When you create an
    external (unmanaged) table, Hive keeps the data in the directory specified by
    the LOCATION keyword intact. But if you were to execute the same CREATE command
    and drop the EXTERNAL keyword, the table would be a managed table,
    and Hive would move the contents of the LOCATION directory into /user/hive/
    warehouse/stocks, which may not be the behavior you expect.</p>
  </blockquote>
  
  <p>I created a managed table with LOCATION keyword. And then loaded data into the table from a HDFS file. But I could not see any directory created under /user/hive/warehouse. Rather the new directory was created in LOCATION mentioned. So I think if I create a MANAGED table with LOCATION mentioned then there is nothing created in Hive warehouse directory ? Is this understanding correct ?</p>
  
  <p>Also if the location of the input file during LOAD command is hdfs, then internal or external table both will move the data to their location. Is this understanding also correct ?</p>