[
https://issues.apache.org/jira/browse/SQOOP-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935546#comment-14935546
]
Sqoop QA bot commented on SQOOP-2549:
-------------------------------------
Testing file
[SQOOP-2549.patch|https://issues.apache.org/jira/secure/attachment/12764269/SQOOP-2549.patch]
against branch sqoop2 took 1:00:44.892450.
{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 unit tests passed (executed 1434 tests)
{color:green}SUCCESS:{color} Test coverage did not decreased
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1740/artifact/patch-process/cobertura_report.txt])
{color:green}SUCCESS:{color} No new findbugs warnings
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1740/artifact/patch-process/findbugs_report.txt])
{color:green}SUCCESS:{color} All integration tests passed (executed 89 tests)
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1740/console].
This message is automatically generated.
> Sqoop2: Allow connector developers to mask certain keys in Maps when sending
> them back to clients
> -------------------------------------------------------------------------------------------------
>
> Key: SQOOP-2549
> URL: https://issues.apache.org/jira/browse/SQOOP-2549
> Project: Sqoop
> Issue Type: Bug
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2549.patch
>
>
> While working on SQOOP-2524, I've realized that whereas we do have
> {{sensitive}} property for entire {{@Input}} (which means it's value won't be
> send back to client), we don't have anything like that for individual map
> properties. Connector developer can still mask entire map, but that seems
> quite overkill for that use case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
