sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1829) Sqoop2: Define IDF object model
Date Tue, 09 Dec 2014 15:51:12 GMT

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

Jarek Jarcec Cecho commented on SQOOP-1829:

I would start with wiki or google doc, so that we can discuss it and then when we agree on
the final state, we can move it to {{rst}} format.

> Sqoop2: Define IDF object model
> -------------------------------
>                 Key: SQOOP-1829
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1829
>             Project: Sqoop
>          Issue Type: Sub-task
>    Affects Versions: 1.99.4
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Veena Basavaraj
>             Fix For: 1.99.5
> We've done quite decent job in defining Intermediate data format and how are certain
data types serialized into CSV-ish format ([defined on the wiki|https://cwiki.apache.org/confluence/display/SQOOP/Sqoop2+CSV+Intermediate+representation]
as part of SQOOP-515 and further revised in umbrella JIRA SQOOP-1350).
> We should create similar definition for our object representation. For example we've
recently uncovered bug when we were returning {{Date}} object when it's Joda representation
has been expected.

This message was sent by Atlassian JIRA

View raw message