[
https://issues.apache.org/jira/browse/SQOOP-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254087#comment-14254087
]
ASF subversion and git services commented on SQOOP-1930:
--------------------------------------------------------
Commit 8cb7fc48abe4c1fdb80ed39cc0eeac7f8937f729 in sqoop's branch
refs/heads/sqoop2 from [~abec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=8cb7fc4 ]
SQOOP-1930: Sqoop2: Enforce a non empty schema name and column names
(Veena Basavaraj via Abraham Elmahrek)
> Sqoop2: Enforce a non empty schema name and column names
> --------------------------------------------------------
>
> Key: SQOOP-1930
> URL: https://issues.apache.org/jira/browse/SQOOP-1930
> Project: Sqoop
> Issue Type: Sub-task
> Components: sqoop2-framework
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: SQOOP-1930-v1.patch, SQOOP-1930-v2.patch,
> SQOOP-1930-v3.patch, SQOOP-1930-v4.patch
>
>
> In future it might lead to confusion to send back schema without names, have
> a non empty identifier is a good sanity check
> all added unit tests to check for non empty schema and column names
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
