[SQOOP-1643] Sqoop2: Add Requires/Optional attribute support for input names

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 2.0.0
• Assignee: Unassigned
• Reporter: Veena Basavaraj
• Created: 29/Oct/14 21:34
• Updated: 26/Mar/15 07:27

Description

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

/**
   * 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;

Issue Links

• is a clone of: SQOOP-1636 Sqoop2: Add unique constraint to the SQI_INPUT name per type per config