[
https://issues.apache.org/jira/browse/HIVE-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834502#comment-13834502
]
Teddy Choi commented on HIVE-5761:
----------------------------------
Or we can use a combined format. Each element of LongColumnVector contains 64
bits, but daysSinceEpoch requires only 32 bits. We can assign remaining 32 bits
to cache a parsed result in the alternative representation. When there are more
than one date-related function, it will use java.sql.Date just once per record.
As current implementation of java.sql.Date and java.util.Calendar parse all
fields at once and caches their results, it will not hurt performance much. :)
How do you think about it?
> Implement vectorized support for the DATE data type
> ---------------------------------------------------
>
> Key: HIVE-5761
> URL: https://issues.apache.org/jira/browse/HIVE-5761
> Project: Hive
> Issue Type: Sub-task
> Reporter: Eric Hanson
> Assignee: Teddy Choi
>
> Add support to allow queries referencing DATE columns and expression results
> to run efficiently in vectorized mode. This should re-use the code for the
> the integer/timestamp types to the extent possible and beneficial. Include
> unit tests and end-to-end tests. Consider re-using or extending existing
> end-to-end tests for vectorized integer and/or timestamp operations.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
