[
https://issues.apache.org/jira/browse/HIVE-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968598#comment-13968598
]
Eugene Koifman commented on HIVE-5072:
--------------------------------------
[~shuainie] Here are a few more thoughts:
0. I was thinking that the options file would originate at the client making
the REST call. It would be uploaded to WebHCat via the same REST call and then
WebHCat can copy to Dist Cache or handle as appropriate, but your use case also
makes sense and as currently implemented, it's on par with how pig/hive jobs
are handled.
5. Your implementation supports automatically shipping of Sqoop tar file to the
target node where the job will be executed. The tar file doesn't contain JDBC
drivers for all DB types so you can't expect it to be in the "lib" folder on
target node.
7. Since this API would mostly be used by Sqoop users, I think they'll find it
confusing that items with the same name in Sqoop have different meaning in
WebHCat/Sqoop. I would try to either change the names of parameters or make
the definition in the 2 systems match.
7.5 Please file Documentation Jira to make sure this API gets documented on the
wiki
9. Does your implementation work with Sqoop 1 and Sqoop 2? If not, it should
probably assert the right version is installed/tar file is available and
produce a meaningful error to client.
10. There is now (in Server.java) version/hadoop, version/hive, version/pig
methods. I think it would be useful to add the same for Sqoop.
> [WebHCat]Enable directly invoke Sqoop job through Templeton
> -----------------------------------------------------------
>
> Key: HIVE-5072
> URL: https://issues.apache.org/jira/browse/HIVE-5072
> Project: Hive
> Issue Type: Improvement
> Components: WebHCat
> Affects Versions: 0.12.0
> Reporter: Shuaishuai Nie
> Assignee: Shuaishuai Nie
> Attachments: HIVE-5072.1.patch, HIVE-5072.2.patch, HIVE-5072.3.patch,
> Templeton-Sqoop-Action.pdf
>
>
> Now it is hard to invoke a Sqoop job through templeton. The only way is to
> use the classpath jar generated by a sqoop job and use the jar delegator in
> Templeton. We should implement Sqoop Delegator to enable directly invoke
> Sqoop job through Templeton.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
