[
https://issues.apache.org/jira/browse/SQOOP-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218930#comment-14218930
]
Qian Xu edited comment on SQOOP-1768 at 11/21/14 1:47 AM:
----------------------------------------------------------
I've some thoughts:
1. {{\-\-all}} shows items in details. Without {{\-\-all}} shows items in a
table. They are different.
2. I'd keep long switches, since they are already implemented and documented.
3. Which apis are still accessible but should be marked as deprecated? I'd
suggest use {{HTTP 301}} to indicate REST API deprecation and remove in future
(e.g. the next release after).
was (Author: stanleyxu2005):
I've some thoughts:
1. Better use {{HTTP 301}} to indicate REST API deprecation rather than
removing them directly.
2. Besides short switches, better keep long switches as well. I'd only correct
inconsistent usage of long/short switches in documentation.
3. {{\-\-all}} shows items in details. Without {{\-\-all}} shows items in a
table. They are different.
> Sqoop2: Simplify the command support for using the entity ids in the show
> command
> ---------------------------------------------------------------------------------
>
> Key: SQOOP-1768
> URL: https://issues.apache.org/jira/browse/SQOOP-1768
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Veena Basavaraj
> Assignee: Qian Xu
> Priority: Minor
> Labels: newbie++
> Fix For: 1.99.5
>
>
> Since all is deprecated in the rest apis, the command line should get rid of
> the same as well.
> - show links should replace show link with no id today.
> - remove the support for -all
> - remove the confusion around 2 ways to give a entity Id, Do we need --jid
> and -j ?
> Lets keep it simple
> -c for connector
> -l for link
> -j for job
> -s for status
> -f and -t are basically the linkIds. so we should make it explicit that they
> are so
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
