You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2014/11/12 23:29:34 UTC
[jira] [Commented] (SQOOP-1716) Add Options as a field in the Enum
object ( so it can be used for validation)
[ https://issues.apache.org/jira/browse/SQOOP-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208814#comment-14208814 ]
Jarek Jarcec Cecho commented on SQOOP-1716:
-------------------------------------------
I'm strong +1 on this idea. I think that this is oversight on my side when working on SQOOP-515. {{Enum("A", "B")}} is completely different type then let say {{Enum("B", "C")}} and we should be able to distinguish those two cases in our schema objects.
> 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
> Fix For: 1.99.5
>
>
> 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)