[ 
https://issues.apache.org/jira/browse/PHOENIX-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

noam bulvik updated PHOENIX-1485:
---------------------------------
    Description: 
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 

  was: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)


> 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
>
> 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)

Reply via email to