Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase, mail # dev - thrift vs thrift2


+
Jimmy Xiang 2012-12-06, 23:24
+
Stack 2012-12-07, 00:48
+
Jesse Yates 2012-12-07, 00:50
+
Andrew Purtell 2012-12-07, 03:21
+
Luke Lu 2012-12-07, 21:56
+
Stack 2012-12-07, 23:16
+
lars hofhansl 2012-12-08, 04:45
+
Andrew Purtell 2012-12-08, 05:06
+
lars hofhansl 2012-12-08, 05:27
+
Andrew Purtell 2012-12-08, 05:42
+
Ted Yu 2012-12-08, 05:12
+
Stack 2012-12-08, 07:31
+
Luke Lu 2012-12-08, 07:50
+
Jimmy Xiang 2012-12-08, 16:59
+
Andrew Purtell 2012-12-09, 02:15
+
Jake Farrell 2012-12-10, 20:36
+
Ted Yu 2012-12-10, 21:18
+
lars hofhansl 2012-12-08, 07:47
+
Ted Yu 2012-12-07, 22:01
+
Jimmy Xiang 2012-12-07, 22:20
+
Tim Sell 2012-12-07, 23:13
Copy link to this message
-
Re: thrift vs thrift2
Stack 2012-12-07, 23:30
On Fri, Dec 7, 2012 at 3:13 PM, Tim Sell <[EMAIL PROTECTED]> wrote:

> Hey,
>
>

Hey Mighty Tim.
I think a good design would be one in which the java/rest and thrift
> apis were simply implementing the same interface.
>

Yes.

I've not looked at the two idls.  Could we put them together and have
thrift package do both apis (you can all slap me if that a dumb idea).

> A better one might be that the thrift and rest packages are stand
> alone java projects that build separately and simply depend on HBase,
> but that would be a hassle for deployment.
>
>
Yes.  Could make them separate projects if someone wanted to own them.

> The thing is, if I was using hbase today, I wouldn't use the hbase
> thrift or thrift2 api, I'd implement my own thrift api (in java) that
> was domain specific so that the application didn't know it was talking
> to hbase.
>

That makes sense.  I'd imagine though that you wouldn't mind having an
existing IDL for inspiration.

St.Ack
+
Andrew Purtell 2012-12-08, 01:45