sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1646) Support a default attribute on the Input for better usability
Date Mon, 03 Nov 2014 00:02:34 GMT

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

Jarek Jarcec Cecho commented on SQOOP-1646:
-------------------------------------------

I think that having a "default" value is a good idea that will have its place - I'm merely
stating that I'm afraid that it's usability will be quite limited. By looking into our current
Generic JDBC Connector or [all Sqoop 1 parameters|https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/SqoopOptions.java],
there is only a handful of arguments for which it make sense to have default constant value
on connector level - mostly boolean arguments and home directories for various dependencies
(Accumulo,Hive,HBase). I believe that this actually make sense as most reasonable "defaults"
depends on values of other inputs or configurations. For example input "partitionColumn" do
have default - it's name of the column that serves as a primary key of given table, but we
can't easily hardcode such constant in the code.

Thinking out lough here and definitely outside of scope of this JIRA, it might be interesting
to include ability for connectors to suggest values. I have in my mind a GUI where I'll select
a link and then in the form for creating a job Sqoop Server (with connector's cooperation)
will suggest me what tables are there in the database that I might want to transfer. This
would be easily reusable for the primary key example that I've described above - as I would
already know the link and the table name at that point, Sqoop server could recommend me what
column would be the best to use as "partitionColumn".

> Support a default attribute on the Input for better usability
> -------------------------------------------------------------
>
>                 Key: SQOOP-1646
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1646
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>             Fix For: 1.99.4
>
>
> For some of the input values in configs it is nice to have the default values in the
code when the connector creates the inputs, so they dont have to be filled in from the user
when not necessary to do so
> {code}
> public @interface Input {
>   String defaultsTo() default "";
> ...
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message