[
https://issues.apache.org/jira/browse/IMPALA-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16907534#comment-16907534
]
H. Vetinari commented on IMPALA-1903:
-------------------------------------
Could someone link the reason for "Won't fix" from the dev mailing lists?
Otherwise, I'd like to reopen this (or a similar) issue.
(We like impala as a data query engine, and this issue is preventing us from
saving the data (thru spark) in the way that's most natural due to being unable
to read from Impala).
> Add support for partitions by timestamp
> ---------------------------------------
>
> Key: IMPALA-1903
> URL: https://issues.apache.org/jira/browse/IMPALA-1903
> Project: IMPALA
> Issue Type: New Feature
> Components: Frontend
> Affects Versions: Impala 2.2
> Reporter: Grant Sohn
> Assignee: Jim Apple
> Priority: Critical
> Labels: ramp-up, sql-language
>
> Timestamps or some time related parameter is a very common way data is
> partitioned. At Yahoo almost all the Hadoop ETL data was partitioned this
> way. This should be on par with nested data types as an important feature
> for Impala to have.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
