[
https://issues.apache.org/jira/browse/SQOOP-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253961#comment-14253961
]
Sqoop QA bot commented on SQOOP-1930:
-------------------------------------
Testing file
[SQOOP-1930-v3.patch|https://issues.apache.org/jira/secure/attachment/12688398/SQOOP-1930-v3.patch]
against branch sqoop2 took 0:26:12.900553.
{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
{color:green}SUCCESS:{color} All integration tests passed
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/816/console].
This message is automatically generated.
> 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
>
>
> 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)
