[
https://issues.apache.org/jira/browse/SQOOP-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216624#comment-14216624
]
Sqoop QA bot commented on SQOOP-1716:
-------------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12681815/SQOOP-1716.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/633/console
This message is automatically generated.
> Add Options as a field in the Enum object ( so it can be used for validation)
> -----------------------------------------------------------------------------
>
> Key: SQOOP-1716
> URL: https://issues.apache.org/jira/browse/SQOOP-1716
> Project: Sqoop
> Issue Type: Sub-task
> Components: sqoop2-framework
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: SQOOP-1716-v1.patch, SQOOP-1716.patch, SQOOP-1716.patch
>
>
> For instance, today we store the type as a Enum, but we really do not know
> what is the Enum value set. Having this will allow more control for validation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
