Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Received-SPF: pass (nike.apache.org: domain of carl@cloudera.com designates
 209.85.220.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CB9A3A2C.36981%toffer@apache.org>
References: 
 <CAJqeMKTyJsYFx9oNodMab-KrhgndQTg7zdDBT7d-Xzc_axib2g@mail.gmail.com>
	<CB9A3A2C.36981%toffer@apache.org>
Date: Thu, 19 Jul 2012 14:55:13 -0700
Message-ID: 
 <CAJqeMKTzt_81c1wRmM=jZLG=-2SxFUPVrPH2KnPRt1YgiB7CBQ@mail.gmail.com>
Subject: Re: Is HiveMetastoreClient a public interface?
From: Carl Steinbach <carl@cloudera.com>
To: dev@hive.apache.org, hcatalog-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf307f34ba862b5604c535d581

--20cf307f34ba862b5604c535d581
Content-Type: text/plain; charset=ISO-8859-1

Sorry for the delay in responding.


> The java API is an ask from one of our users for Hcatalog. Given that
> HiveMetaStoreClient is a thin wrapper around public apis, then change
> shouldn't be drastic? It seems the cleaner way to go about it is to create
> an hcat client wrapper around HiveMetaStoreClient and have HCatClient as
> public?
>

The problem with this proposal is that until HiveMetaStoreClient is a
public API, HCatalog has just as little right to integrate with it directly
as any other third-party. I think the best solution is to invest the time
required to make HiveMetaStoreClient a public API, or to wrap
HiveMetaStoreClient with HiveMetaStoreClient2 and make that a public API
(we'll probably need to take the latter approach since HiveMetastoreClient
currently exposes raw Thrift types).

I filed HIVE-3280 to track this task.

Thanks.

Carl

--20cf307f34ba862b5604c535d581--