[
https://issues.apache.org/jira/browse/SQOOP-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158266#comment-14158266
]
Jarek Jarcec Cecho commented on SQOOP-1367:
-------------------------------------------
It seems that {{sqoop2}} and {{SQOOP-1367}} branches are very close, so the
merging should be relatively straightforward. +1 on the next Wednesday (10/8).
From the process perspective I would suggest doing an usual git merge rather
than uploading one big patch containing entire development in feature branch
and committing it into {{sqoop2}} branch as one commit (as some other projects
are doing). My main motivation to suggest this is that we will preserve entire
history, which means that:
* People will get proper contribution for their changes
* {{git blame}} will be able to point specific JIRA and not just a master JIRA
> Sqoop2: From/To
> ---------------
>
> Key: SQOOP-1367
> URL: https://issues.apache.org/jira/browse/SQOOP-1367
> Project: Sqoop
> Issue Type: New Feature
> Affects Versions: 1.99.3
> Reporter: Abraham Elmahrek
> Assignee: Abraham Elmahrek
>
> Hadoop shouldn't have a special meaning in Sqoop. HDFS, HBase, etc. should
> have their own connectors. Sqoop should transfer data FROM one connector TO
> another. To be more explicit, instead of IMPORT/EXPORT, provide API for
> FROM/TO.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
