atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-606) Change from Hive thrift interface to Hive MetastoreClient
Date Thu, 14 Apr 2016 19:02:25 GMT

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

Suma Shivaprasad commented on ATLAS-606:
----------------------------------------

Since the calls are going through RetryingMetastoreClient, failover is also handled. The calls
are also confirmed to be secure. The only concern with usig Hive client is that it is s not
a public interface but it is also the case with HookContext, ReadEntity, WriteEntity etc and
is also convenient to use because of API compatibiltty of entities ( eg: Table, DB etc) with
HookContext entities.

> Change from Hive thrift interface to Hive MetastoreClient
> ---------------------------------------------------------
>
>                 Key: ATLAS-606
>                 URL: https://issues.apache.org/jira/browse/ATLAS-606
>             Project: Atlas
>          Issue Type: Sub-task
>            Reporter: Suma Shivaprasad
>            Assignee: Suma Shivaprasad
>             Fix For: 0.7-incubating
>
>
> The reason to switch would be 
> a. Failovers from metastore client are not handled in Hive client
> b. Hive thrift calls are apparently unsecure



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message