[jira] [Commented] (FALCON-96) Hive client to talk to the metastore

["Srikanth Sundarrajan (JIRA)" <ji...@apache.org>]

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

Srikanth Sundarrajan commented on FALCON-96:
--------------------------------------------

>From the earlier discussion on this thread, it seems like we intend only support thrift url for catalog (using hcatclient over hive metastore), however I do see implementation for WebHCatCatalogService as well. So are we able to support both and leave it to users to pick something of their choice ? This is really nice. 

Looks good.

Should we also add unit tests for WebHCat based catalog service in the integration tests ?

                
> Hive client to talk to the metastore
> ------------------------------------
>
>                 Key: FALCON-96
>                 URL: https://issues.apache.org/jira/browse/FALCON-96
>             Project: Falcon
>          Issue Type: Sub-task
>    Affects Versions: 0.3
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>         Attachments: FALCON-96-addition.patch, FALCON-96.patch
>
>
> There are 2 choices: RPC using thrift and HTTP using webhcat. HTTP of course is preferable but there are a few issues with it:
> * Uses cli to talk to the server implying needing Hcat install and client. This is a PITA for integration-tests.
> * Also, there is no java wrapper around the RESTful APIs which returns Map and such. Need to roll our own. 
> * Runs as a separate daemon (which should eventually fold into metastore or HiveServer2). However this is short-term and a minor annoyance.
> Thoughts?

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