sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sqoop QA bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2235) Sqoop2: Move PrefixContext back to mapreduce execution engine
Date Mon, 23 Mar 2015 23:41:52 GMT

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

Sqoop QA bot commented on SQOOP-2235:

Testing file [SQOOP-2235.patch|https://issues.apache.org/jira/secure/attachment/12705642/SQOOP-2235.patch]
against branch sqoop2 took 0:54:49.952659.

{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 670 tests)
{color:green}SUCCESS:{color} All slow unit tests passed (executed 1 tests)
{color:green}SUCCESS:{color} All fast integration tests passed (executed 46 tests)
{color:green}SUCCESS:{color} All slow integration tests passed (executed 20 tests)

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

This message is automatically generated.

> Sqoop2: Move PrefixContext back to mapreduce execution engine
> -------------------------------------------------------------
>                 Key: SQOOP-2235
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2235
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.5
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.6
>         Attachments: SQOOP-2235.patch
> When we introduced HDFS connector we moved PrefixContext class out of it's mapreduce
engine and put it into common as HDFS connector has been historically depending on this class.
We've fixed that recently, so I would like to put the class back where it belongs.

This message was sent by Atlassian JIRA

View raw message