You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Qian Xu (JIRA)" <ji...@apache.org> on 2015/01/09 04:37:34 UTC
[jira] [Updated] (SQOOP-1987) Sqoop2: Add a NullMatcher
[ https://issues.apache.org/jira/browse/SQOOP-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Qian Xu updated SQOOP-1987:
---------------------------
Affects Version/s: 1.99.5
> Sqoop2: Add a NullMatcher
> -------------------------
>
> Key: SQOOP-1987
> URL: https://issues.apache.org/jira/browse/SQOOP-1987
> Project: Sqoop
> Issue Type: Sub-task
> Affects Versions: 1.99.5
> Reporter: Qian Xu
> Assignee: Qian Xu
> Fix For: 2.0.0
>
>
> The {{MatcherFactory}} will create different matcher according to toSchema and fromSchema conditions.
> In {{LocationMatcher}}, it has a rule 0
> {code}
> public Object[] getMatchingData(Object[] fields) {
> if (getToSchema().isEmpty()) {
> // No destination schema found. No need to convert anything.
> return fields;
> }
> {code}
> I'm thinking we can create a third matcher {{NullMatcher}}, which simply return input fields as result.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)