[
https://issues.apache.org/jira/browse/SQOOP-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111364#comment-14111364
]
Sqoop QA bot commented on SQOOP-1436:
-------------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12664484/SQOOP-1436.patch
against branch sqoop2.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch add/modify test case
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All tests passed
Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/320/console
This message is automatically generated.
> 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)