[jira] [Commented] (SQOOP-1849) Using JODA for datetime means we only have 3 digit millisecond representation for fraction

["Gwen Shapira (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SQOOP-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238162#comment-14238162 ] 

Gwen Shapira commented on SQOOP-1849:
-------------------------------------

I think having millisecond accuracy and not supporting micros is fine.

Micros are not uniformly supported (for example Avro chose not to support miliseconds in AVRO-739) and I don't think millisecond accuracy is a blocker for anyone.  Users who really really need micros can always use free-form query to convert the date to long (micros since epoch).



> Using JODA for datetime means we only have 3 digit millisecond representation for fraction
> ------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-1849
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1849
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-framework
>            Reporter: Veena Basavaraj
>             Fix For: 1.99.5
>
>
> At this point it is important to define the right spec and how the date time will be represented.
> Note: We have spent a few weeks or more solving the issue with JODA, it would be advisable to do more research in future before we choose an library and highlight the quirks we may face.
> This issue resulted from https://issues.apache.org/jira/browse/SQOOP-1845
> There is some details in this ticket as well



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)