[
https://issues.apache.org/jira/browse/SQOOP-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148428#comment-14148428
]
ASF subversion and git services commented on SQOOP-1378:
--------------------------------------------------------
Commit 327d4372fedaaa0961c9ba3cb9e3af2c1d9d4bb5 in sqoop's branch
refs/heads/SQOOP-1367 from [~gwenshap]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=327d437 ]
SQOOP-1378: Sqoop2: From/To: Refactor schema
This patch also changes the tools documentation.
> 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, SQOOP-1378.5.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)
