[
https://issues.apache.org/jira/browse/SQOOP-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718293#comment-14718293
]
Dian Fu commented on SQOOP-2537:
--------------------------------
Thanks [~jarcec] for review. The reason to the exceptions is that resource name
such as job name, link name or connector name is null. Have created SQOOP-2539
to limit that resource name cannot be null.
> Sqoop2: Use object name instead of object id for the name filed in MResource
> ----------------------------------------------------------------------------
>
> Key: SQOOP-2537
> URL: https://issues.apache.org/jira/browse/SQOOP-2537
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Dian Fu
> Assignee: Dian Fu
> Fix For: 1.99.7
>
> Attachments: SQOOP-2537.001.patch
>
>
> Currently the meaning of the name field in MResource isn't consistent. Some
> places assume this field means the object name of the resource, such as in
> AuthorizationRequestHandler. Some places assume this field means the object
> id of the resource, such as in AuthorizationEngine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
