[
https://issues.apache.org/jira/browse/SQOOP-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189624#comment-14189624
]
Qian Xu edited comment on SQOOP-1643 at 10/30/14 4:20 AM:
----------------------------------------------------------
In order not to bring too much complexity, I'd suggest use an annotation.
{code}
@Input(size = 255)
@Optional
public String filteringClause;
{code}
In user interactive mode, user will see
{code}
Filtering Clause (optional):
{code}
Note that if you want to support custom text in annotation,, localization
should be considered.
was (Author: stanleyxu2005):
In order not to bring too much complexity, I'd suggest use an annotation.
{code}
@Input(size = 255)
@Optional
public String filteringClause;
{code}
In user interactive mode, user will see
{code}
Filtering Clause (optional):
{code}
Note that if you want to support custom text in annotation,, localization
should be considered.
> Sqoop2: Add Requires/Optional attribute support for input names
> ----------------------------------------------------------------
>
> Key: SQOOP-1643
> URL: https://issues.apache.org/jira/browse/SQOOP-1643
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.4
>
>
> The goal is to have much better user experience when user has to fill out the
> values for config inputs in the UI/ shell client.
> Today there is no way to tell if a input is required or optional. Also the
> help labels should be more clear in explaining what each of them mean and
> when their value is not required. We can even group the required ones first
> and then the optional ones latter
> Similar to
> {code}
> /**
> * Sqoop will ensure that sensitive information will not be easily
> * accessible.
> *
> * @return True if field is sensitive
> */
> boolean sensitive() default false;
> boolean required() default true;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
