sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qian Xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1643) Sqoop2: Add Requires/Optional attribute support for input names
Date Thu, 30 Oct 2014 04:17:34 GMT

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

Qian Xu commented on SQOOP-1643:

In order not to bring too much complexity, I'd suggest use an annotation.

@Input(size = 255)
@Optional("A filtering clause of the query")
String filter;

In user interactive mode, user will see

{{> FILTER (A filtering clause of the query): }}

Note that 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

View raw message