thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Siamak Haschemi <hasch...@informatik.hu-berlin.de>
Subject Re: Thrift and Hadoop; especially: Java support in Thrift
Date Fri, 24 Oct 2008 21:15:11 GMT
Hello Jeff,

is it possible that you give some hints about *where* and *what* is poor
supported?


Kind regards,

Siamak Haschemi

Bryan Duxbury schrieb:
> I've been doing lots of Java work on Thrift for a while now. Are there
> particular things that need to be fixed, or are you just noting that the
> Java library is poor in general?
> 
> -Bryan
> 
> On Oct 24, 2008, at 1:02 AM, Jeff Hammerbacher wrote:
> 
>> Hey Thrift Users and Developers,
>>
>> The Apache Hadoop community is going through the process of hardening
>> Hadoop in preparation of a 1.0 release. The process is being
>> documented here: http://wiki.apache.org/hadoop/Release1.0Requirements.
>>
>> If you check out the "Multi-language serialization" part of the linked
>> document, you'll see that there is a debate going on about which
>> cross-language RPC framework to use for Hadoop going forward. The
>> major contenders are Thrift, Protocol Buffers, Etch, and Hessian. One
>> of the major reasons I pushed to get Thrift into Apache when at
>> Facebook was the opportunity to replace Hadoop's RPC mechanisms with
>> Thrift. I guess now is the moment of truth.
>>
>> If you'd like to see Hadoop adopt Thrift as it's internal and external
>> RPC framework, please voice your opinion on the Hadoop development
>> list. If you want to go the extra mile, the biggest blocker to Thrift
>> adoption within the Hadoop community is its poor support for Java. If
>> you have some time available and you're a Java wizard, any code you
>> can contribute to Thrift in the next few weeks will make a difference
>> in the push to get Thrift adopted by the Hadoop community.
>>
>> Anyways, as a Thrift and Hadoop fanboy, I'm just trying to do some
>> cheerleading to make the marriage happen.
>>
>> Regards,
>> Jeff
> 

Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message