[
https://issues.apache.org/jira/browse/SQOOP-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759419#comment-13759419
]
Venkat Ranganathan commented on SQOOP-1072:
-------------------------------------------
Thanks [~jarcec] for your thoughts. It looks like we have a small set of I/O
interfaces that we can look at. In fact, we may be able to just reduce that to
one (HCatalog) in a degenerate case. I do agree that the ability to abstract
the I/O interfaces for future evolution is good. It would be good to
understand the impact of one path vs the other by mapping out the work items
would be good to get an understanding of the tradeoffs in play.
> Sqoop2: Abstract Input/Output interfaces
> ----------------------------------------
>
> Key: SQOOP-1072
> URL: https://issues.apache.org/jira/browse/SQOOP-1072
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 1.99.2
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 2.0.0
>
>
> The input/output interfaces like {{Text}} or {{SequenceFile}} are currently
> hardcoded and are present through entire code base. It would be great to
> abstract the I/O module similarly as we are doing in connectors and push
> appropriate code to separate modules.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
