[ 
https://issues.apache.org/jira/browse/SQOOP-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083135#comment-15083135
 ] 

ASF subversion and git services commented on SQOOP-2763:
--------------------------------------------------------

Commit c40c23c9e6cb398816ee16ccbd4ee77c0b3df57e in sqoop's branch 
refs/heads/sqoop2 from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=c40c23c ]

SQOOP-2763: Sqoop2: Sqoop shell is accepting non existing arguments

(Dian Fu via Jarek Jarcec Cecho)


> Sqoop2: Sqoop shell is accepting non existing arguments
> -------------------------------------------------------
>
>                 Key: SQOOP-2763
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2763
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.7
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Dian Fu
>             Fix For: 1.99.7
>
>         Attachments: SQOOP-2763.001.patch, SQOOP-2763.002.patch, 
> SQOOP-2763.003.patch, SQOOP-2763.003.patch
>
>
> We happily accept non-existing arguments in the shell which is highly 
> deceptive:
> {code}
> sqoop:000> set server --name x
> Server is set successfully
> sqoop:000>
> {code}
> or
> {code}
> sqoop:000> show connector --please
> ...
> sqoop:000>
> {code}
> We should throw an exception or something if one is using 
> incorrect/non-existing arguments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to