[
https://issues.apache.org/jira/browse/PHOENIX-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244675#comment-14244675
]
Gabriel Reid commented on PHOENIX-1127:
---------------------------------------
I think your suggestion of overriding the default date format string is the
best option as a work around [~jamestaylor].
A separate default parse string for timestamp also sounds like a good plan --
do you think we need to worry about backwards compatibility much there? Ideally
I would want to set the DATE format string to a real date (i.e. without time
components), and do something along the same lines for TIME columns, but that
would probably be a bit too intrusive in terms of backwards compatibility.
The approach I'm thinking of to make this easier to do when importing data is
to have some kind of mechanism to pass config properties in to an invocation of
the CSV loader. I think this will actually already work for the bulk csv loader
if, for example, you supply "-Dphoenix.query.dateFormat=yyyy-MM-dd
HH:mm:ss.SSSS" as a parameter when starting. If we could do something something
similar with psql, do you think that would be adequate?
> 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)
