[
https://issues.apache.org/jira/browse/HIVE-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998489#comment-15998489
]
Lukas Waldmann commented on HIVE-13652:
---------------------------------------
I just wonder, if by using LinkedHashMap we don't introduce just another
vulnerability there as order of items in the HashMap is not defined and if ever
hashing algo change than again we may get completely different order?
> Import table change order of dynamic partitions
> -----------------------------------------------
>
> Key: HIVE-13652
> URL: https://issues.apache.org/jira/browse/HIVE-13652
> Project: Hive
> Issue Type: Bug
> Components: Import/Export, repl
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Lukas Waldmann
> Assignee: Sankar Hariappan
> Labels: DR, replication
> Attachments: HIVE-13652.01.patch,
> ReplLoad_PartitionOrder_AfterFix_Log.png,
> ReplLoad_PartitionOrder_BeforeFix_Log.png
>
>
> Table with multiple dynamic partitions like year,month, day exported using
> "export table" command is imported (using "import table") such a way that
> order of partitions is changed to day, month, year.
> Export DB: Hive 0.14
> Import DB: Hive 1.2.1000.2.4.0.0-169
> Tables created as:
> create table T1
> ( ... ) PARTITIONED BY (period_year string, period_month string, period_day
> string) STORED AS ORC TBLPROPERTIES ("orc.compress"="SNAPPY");
> export command:
> export table t1 to 'path'
> import command:
> import table t1 from 'path'
> HDFS file structure on both original table location and export path keeps the
> original partition order ../year/month/day
> HDFS file structure after import is .../day/month/year
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
