You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2014/12/17 23:56:13 UTC
[jira] [Updated] (SQOOP-1919) Supporting Conditions on
ConfigAnnotation in the Configuration class
[ https://issues.apache.org/jira/browse/SQOOP-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Veena Basavaraj updated SQOOP-1919:
-----------------------------------
Description:
As we make configs more dynamic with SQOOP-1168, a Configuration class might support more than one config class and all may or may not be mandatory, able to extend the conditions concept to configs and not just inputs is a good enhancement to build clean UIs as well for sqoop 2 job workflow
see SQOOP-1061 for what conditions might mean on the annotations
was:
As we make configs more dynamic with SQOOP-1168, a Configuration class might support more than one config class and all may or may not be mandatory, able to extend the conditions concept to configs and not just inputs is a good enhancement to build clean UIs as well for sqoop 2 job workflow
see SQOOP-1601 for what conditions might mean on the annotations
> Supporting Conditions on ConfigAnnotation in the Configuration class
> ----------------------------------------------------------------------
>
> Key: SQOOP-1919
> URL: https://issues.apache.org/jira/browse/SQOOP-1919
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
>
> As we make configs more dynamic with SQOOP-1168, a Configuration class might support more than one config class and all may or may not be mandatory, able to extend the conditions concept to configs and not just inputs is a good enhancement to build clean UIs as well for sqoop 2 job workflow
> see SQOOP-1061 for what conditions might mean on the annotations
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)