sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1191) Explore alternatives to using the HCatalog Shim layer
Date Wed, 04 Sep 2013 21:15:52 GMT

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

Jarek Jarcec Cecho commented on SQOOP-1191:
-------------------------------------------

Thank you all for sharing your thoughts and discussing the alternatives! While working on
SQOOP-1190, I've realized that using Shims is not the best approach, but the workarounds seems
to be quite complex as Sqoop itself do not have any shim layer at the moment. So I've decided
to go with a reflection. The code itself will be called only in local mode and only on Hadoop
1, so I believe that the reflection overhead is quite negligible.
                
> Explore alternatives to using the HCatalog Shim layer
> -----------------------------------------------------
>
>                 Key: SQOOP-1191
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1191
>             Project: Sqoop
>          Issue Type: Task
>          Components: hive-integration
>            Reporter: Arvind Prabhakar
>
> In SQOOP-1190 [~ekoifman] points out:
> bq. The shim layer is not part of public API of hcat. Why does Scoop use it? Is there
some other solution to this?
> This issue is being filed to track that discussion and take any necessary corrective
actions.

--
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

Mime
View raw message