[
https://issues.apache.org/jira/browse/SQOOP-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270534#comment-14270534
]
Veena Basavaraj commented on SQOOP-1988:
----------------------------------------
The reason why I say we need a a design doc is exactly to answer this
question, what should a matcher do ? what it should not do. Unless we have this
question clearly answered, we will run into these edge cases more and more.
> Sqoop2: isNull handling should be moved to CSVIntermediateDataFormat
> --------------------------------------------------------------------
>
> Key: SQOOP-1988
> URL: https://issues.apache.org/jira/browse/SQOOP-1988
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Qian Xu
> Assignee: Qian Xu
> Fix For: 2.0.0
>
>
> Matcher should only match fields, not do any value modification (except when
> fallback to null ), Given argument {{fields}} should have converted null
> values.
> Currently it will convert {{null}} {{"NULL"}} {{"null"}} {{"'null'"}} and
> {{""}} to null. They are CSV relevant. As we do not have a knowledge of what
> intermediate data format is used, I'd remove the check and convert here.
> Another benefit is performance gain. Thanks [~jerrychenhf]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
