[
https://issues.apache.org/jira/browse/PHOENIX-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid updated PHOENIX-1485:
----------------------------------
Attachment: PHOENIX-1485.patch
Patch to add an optional timezone parameter to TO_DATE, as well as a
configuration parameter for a global timezone to be used when parsing dates.
This should allow resolving the originally reported issue, as it will allow
doing time/date/timestamp parsing in the local timezone.
Documentation patch is still to come.
[~jamestaylor] I needed to make a change (which I believe is a fix) in
FunctionParseNode to allow everything to work after this change. It was in the
calculation of the number of required parameters for a function. Could you take
a look at that to make sure the change looks ok to you?
> Date columns should be displayed without timezone offset
> --------------------------------------------------------
>
> Key: PHOENIX-1485
> URL: https://issues.apache.org/jira/browse/PHOENIX-1485
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.1
> Reporter: noam bulvik
> Attachments: PHOENIX-1485.patch
>
>
> when date or timestamp column queried the value is the date with timezone
> offset. this is not how it is handled by other jdbc drivers like oracle and
> impala. and it seems strange that when I have text file with specific date
> and I use bulk loader to store it , when I will use select * .. I will get
> different dates then the one in the file (because of the time zone offset)
> by default the date should be displayed without any offset.
> it will be nice to have an option to add the timezone offset the option in
> the driver
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
