You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2014/10/23 03:19:34 UTC

[jira] [Commented] (SQOOP-1554) Add NullConfigurationClass/ EmptyConfigurationClass to support use cases that do not have a particular type of config

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

Gwen Shapira commented on SQOOP-1554:
-------------------------------------

Are you sure this is a blocker for 1.99.4? I'm not sure where it falls in the road map. 
What are the implications of having this later?

(obviously if this is ready before we cut the branch, then no problem. I'm just curious why its a blocker)

> Add NullConfigurationClass/ EmptyConfigurationClass to support use cases that do not have a particular type of config
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-1554
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1554
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>            Priority: Blocker
>             Fix For: 1.99.4
>
>         Attachments: SQOOP-1554.patch, SQOOP-1554.patch, SQOOP-1554.patch
>
>
> Hdfs connector can use the Null Class to support typed parameters



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