[
https://issues.apache.org/jira/browse/SQOOP-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734587#comment-14734587
]
Jarek Jarcec Cecho commented on SQOOP-2554:
-------------------------------------------
This is a tricky one. I've seen users having whitespace and other special
characters in the column names which would break after applying this patch. I
think that the proper solution to this problem is to introduce a new
Configuration type for {{List<String>}} similarly as we have for {{Map<String,
String>}}. This way, user can specify each column name separately and we don't
have do any parsing and hence we wouldn't get any limitations. I've seen this
particular issue while working on SQOOP-2243 as well, but did not yet created a
JIRA for it. Would you agree that it's a better solution [~dian.fu]?
> Sqoop2: Enforce the element column in FromJobConfig of JDBC connector is a
> comma separated list
> -----------------------------------------------------------------------------------------------
>
> Key: SQOOP-2554
> URL: https://issues.apache.org/jira/browse/SQOOP-2554
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.6
> Reporter: Dian Fu
> Assignee: Dian Fu
> Fix For: 1.99.7
>
> Attachments: SQOOP-2554.1.patch
>
>
> We should enforce the column specified by user for JDBC connector is a comma
> separated list, such as "column1, column2". Illegal inputs such as "column1
> column2" should be denied.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
