[
https://issues.apache.org/jira/browse/PHOENIX-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243514#comment-14243514
]
James Taylor commented on PHOENIX-1127:
---------------------------------------
One way you can work around this limitation is to output the timestamp as a
BIGINT in Epoch time from Oracle. Then you can load this into Phoenix without
losing any precision. Another way would be to override our default date format
string in your hbase-sites.xml. See phoenix.query.dateFormat here
http://phoenix.apache.org/tuning.html
[~gabriel.reid] - any other ideas? If you have any spare cycles, this would be
a good, incremental improvement for our CSV loader. Might be as simple as
having a separate default parse string defined for Timestamp that preserves the
milliseconds.
> Cannot load Timestamp(6) from oracle Example: 10/7/2010 3:28:58.117127 PM.
> the only option currently is to load it as string and cannot apply andy date
> manupulations on that column.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-1127
> URL: https://issues.apache.org/jira/browse/PHOENIX-1127
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.0.0
> Environment: PROD
> Reporter: Deepak Gattala
> Fix For: 5.0.0
>
> Original Estimate: 360h
> Remaining Estimate: 360h
>
> cannot do any date manipulation because of this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
