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/09/25 03:38:34 UTC

[jira] [Commented] (SQOOP-1378) Sqoop2: From/To: Refactor schema

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

Gwen Shapira commented on SQOOP-1378:
-------------------------------------

Uploaded a patch with some changes based on Veena's feedback in RB.

> Sqoop2: From/To: Refactor schema
> --------------------------------
>
>                 Key: SQOOP-1378
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1378
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Abraham Elmahrek
>            Assignee: Gwen Shapira
>         Attachments: SQOOP-1378.0.patch, SQOOP-1378.1.patch, SQOOP-1378.2.patch, SQOOP-1378.3.patch, SQOOP-1378.4.patch
>
>
> Relational database systems, hierarchical databases, etc. tend to have a well defined schema. Key-value DBs, BigTable clones, etc. tend to have weakly defined schemas. In fact, a key-value datastore may not have any kind of schema (other than the fact is is key-value).
> Schemas seem like they are local to the connector and should not be needed by the framework. Or, there should be a common Schema format that every connector knows how to decipher.



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