[
https://issues.apache.org/jira/browse/DRILL-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386668#comment-17386668
]
ASF GitHub Bot commented on DRILL-7926:
---------------------------------------
paul-rogers commented on pull request #2268:
URL: https://github.com/apache/drill/pull/2268#issuecomment-886014747
@dzamo, makes sense. Let's at least get a few good tests for this case, then
we can declare victory.
Note that zoneless times (DATE, TIME) should *never* be UTC, they are always
local by definition. They are the reason (I presume) that Drill treats
timestamps as local time: so we can convert between DATE, TIME and TIMESTAMP.
What Drill needs to clean up this mess is a UTC_TIMESTAMP type. There are
suggestions in the code that the original team wanted to add a "zoned
timestamp" type. But, such a monster would be too cumbersome for common use
since, typically, any given column has a known timezone or, more likely in
modern times, is in UTC.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> The " age " function is not working properly.
> ---------------------------------------------
>
> Key: DRILL-7926
> URL: https://issues.apache.org/jira/browse/DRILL-7926
> Project: Apache Drill
> Issue Type: Bug
> Components: Functions - Drill
> Affects Versions: 1.17.0, 1.18.0
> Reporter: Александр Глухов
> Priority: Blocker
> Attachments: image-2021-05-13-16-17-21-154.png, screenshot-1.png,
> screenshot-2.png
>
>
> The " age " function is not working properly.
> *Playback steps*
> {code:sql}
> select extract(year from m. "years") `years` from (select age('2021-05-13',
> '2007-07-02') `years") m{code}
> *Expected result* 13.
> *Actual result* 14.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
