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/08/26 23:15:57 UTC
[jira] [Comment Edited] (SQOOP-1436) Sqoop2: Support custom form
name via the Form Annotation
[ https://issues.apache.org/jira/browse/SQOOP-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111352#comment-14111352 ]
Veena Basavaraj edited comment on SQOOP-1436 at 8/26/14 9:14 PM:
-----------------------------------------------------------------
RB link : https://reviews.apache.org/r/25074/
I just used the java valid identifier convention at this point since it is the norm most places use
was (Author: vybs):
RB link : https://reviews.apache.org/r/25074/
> Sqoop2: Support custom form name via the Form Annotation
> ---------------------------------------------------------
>
> Key: SQOOP-1436
> URL: https://issues.apache.org/jira/browse/SQOOP-1436
> Project: Sqoop
> Issue Type: Bug
> Reporter: Abraham Elmahrek
> Assignee: Veena Basavaraj
> Labels: newbie
> Fix For: 1.99.4
>
> Attachments: SQOOP-1436.patch
>
>
> Form names and input names are currently derived from the configuration property name that they exist in (example 1). It would be nice if custom names could be provided so that the property names could remain simple.
> Example 1:
> The derived form name for the "table" property in the configuration object below is "table".
> {code}
> @ConfigurationClass
> public class FromJobConfiguration {
> @Form public TableForm table;
> ...
> }
> {code}
> Example 2:
> The form name for the "table" member in the the configuration object below is "from-table".
> {code}
> @ConfigurationClass
> public class FromJobConfiguration {
> @Form(name="from-table")
> public TableForm table;
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)