[
https://issues.apache.org/jira/browse/SQOOP-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495650#comment-14495650
]
Sqoop QA bot commented on SQOOP-2299:
-------------------------------------
Testing file
[SQOOP-2299.patch|https://issues.apache.org/jira/secure/attachment/12725464/SQOOP-2299.patch]
against branch sqoop2 took 1:01:32.961466.
{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 675 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 22
tests)
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1280/console].
This message is automatically generated.
> Sqoop2: Store Context classes in repository
> -------------------------------------------
>
> Key: SQOOP-2299
> URL: https://issues.apache.org/jira/browse/SQOOP-2299
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.5
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2299.patch, SQOOP-2299.patch
>
>
> While looking into persisting state from incremental job (SQOOP-1803), I've
> uncover a Hadoop bug where any Hadoop 2 will return incorrect {{job.xml}}
> when using {{JobClient}} APIs to get job's details. The issue is harder to
> track as it was initially fixed in Hadoop 2.7.0 via MAPREDUCE-5875, but
> subsequently reverted because of MAPREDUCE-6288 and it's not clear to me
> when/if the fix will be provided. This is relevant to us as we are storing
> our {{Context}} classes in job conf. I've looked around why nobody seen this
> problem before and it seems that projects are generally persisting properties
> in their repositories rather then using Hadoop APIs to retrieve the
> {{Configuration}} object back.
> Thinking about it a bit more, I think that it would be useful to keep track
> of the context classes as they contain additional information that can be
> useful for debugging purpose. I'm not yet sure whether we should expose those
> objects over the REST interface as they can possibly contain sensitive
> information, but it seems useful to at least persist those.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
