[
https://issues.apache.org/jira/browse/SQOOP-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734607#comment-14734607
]
Jarek Jarcec Cecho commented on SQOOP-2539:
-------------------------------------------
The last pre-commit hook failure is my bad - I've decided to go ahead commit
the patch as there is one small difference between the last and one-to-the-last
version. And I've committed it before the precommit hook started and hence the
patch no longer applies.
> Sqoop2: Enforce resource name not null when creating table
> ----------------------------------------------------------
>
> Key: SQOOP-2539
> URL: https://issues.apache.org/jira/browse/SQOOP-2539
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Dian Fu
> Assignee: Dian Fu
> Fix For: 1.99.7
>
> Attachments: SQOOP-2539.001.patch, SQOOP-2539.002.patch,
> SQOOP-2539.003.patch, SQOOP-2539.004.patch, SQOOP-2539.005.patch
>
>
> Currently resource name such as job name, connector name or link name can be
> null. We should enforce that these resource names cannot be null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
