[
https://issues.apache.org/jira/browse/HIVE-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-5700:
-----------------------------------
Attachment: HIVE-5700.patch
preliminary patch. There's one unresolved comment for myself, I haven't fully
groked the insert processing yet, need to avoid normalizing if partition with
"wrong" date format already exists for insert overwrite. But insert code path
is rather convoluted. [~ashutoshc] can you take a look? This approach may allow
us to use string compares for dates and not depend on data stores converting
arbitrary strings accepted by java.
Otherwise I don't think date pushdown into SQL is really viable/robust enough.
> enforce single date format for partition column storage
> -------------------------------------------------------
>
> Key: HIVE-5700
> URL: https://issues.apache.org/jira/browse/HIVE-5700
> Project: Hive
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
> Attachments: HIVE-5700.patch
>
>
> "inspired" by HIVE-5286.
> Partition column for dates should be stored as either integer, or as fixed
> representation e.g. yyyy-mm-dd. External representation can remain varied as
> is.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
