[ https://issues.apache.org/jira/browse/SQOOP-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated SQOOP-1378:
--------------------------------
Attachment: SQOOP-1378.1.patch
Working version. Tested manually, LOCATION matching only.
No unittests and doesn't address Abe's concerns from 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
>
>
> 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)
|