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

Sqoop QA bot commented on SQOOP-2133:
-------------------------------------

Testing file 
[SQOOP-2133.0.patch|https://issues.apache.org/jira/secure/attachment/12701472/SQOOP-2133.0.patch]
 against branch sqoop2 took 0:40:25.839159.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch add/modify test case
{color:green}SUCCESS:{color} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All fast unit tests passed (executed 262 tests)
{color:green}SUCCESS:{color} All slow unit tests passed (executed 1 tests)
{color:green}SUCCESS:{color} All fast integration tests passed (executed 15 
tests)
{color:green}SUCCESS:{color} All slow integration tests passed (executed 0 
tests)

Console output is available 
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1105/console].

This message is automatically generated.

> Sqoop2: Hdfs Intermediate Data Format
> -------------------------------------
>
>                 Key: SQOOP-2133
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2133
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-hdfs-connector
>    Affects Versions: 1.99.6
>            Reporter: Abraham Elmahrek
>            Assignee: Abraham Elmahrek
>             Fix For: 1.99.6
>
>         Attachments: SQOOP-2133.0.patch
>
>
> The HDFS connector has to do a lot of formatting and encoding operations 
> before writing to HDFS some times. It would be nice to have an IDF that 
> understood the different encodings and how to serialize/deserialize w/ these 
> different encodings. For example, in SQOOP-1579, the option to 
> escape/unescape data would be handled in this IDF.



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

Reply via email to