> As such, if you have an itch to have a Thrift based wire protocol, that is
> a great idea and it should be relatively easy to build one.
Good. Feel free to put me down for that, if the group as a whole thinks that (supporting Thrift)
makes sense.
> It should also be relatively opaque to the user what wire protocol is in use.
Exactly. And this should be made explicit in the design considerations and requirements.
Cheers,
Michael
--
Michael Hausenblas
Ireland, Europe
http://mhausenblas.info/
On 4 Sep 2012, at 17:08, Ted Dunning wrote:
> I think that Thrift would make a fine remote API protocol. And I sincerely
> hope that we don't lock Drill into one data representation or one RPC wire
> format. API != wire protocol, after all.
>
> As such, if you have an itch to have a Thrift based wire protocol, that is
> a great idea and it should be relatively easy to build one.
>
> It should also be relatively opaque to the user what wire protocol is in
> use.
>
> On Tue, Sep 4, 2012 at 8:28 AM, lesliewang <wqyuwss@hotmail.com> wrote:
>
>>
>> Good point. They are quite similar.
>> I guess it is mainly because Dremel is developed by Google, and explain
>> how to use Protocol Buffer in paper. Thus, Protocol Buffers are adopted in
>> Drill by default. :-)
>>
>>> From: michael.hausenblas@gmail.com
>>> Subject: Thrift?
>>> Date: Tue, 4 Sep 2012 11:16:11 +0100
>>> To: drill-dev@incubator.apache.org
>>>
>>> All,
>>>
>>> I'm wondering: Protocol Buffers (and Avro) is mentioned a couple of
>> times both in the proposal and in the git README but no mention of Apache
>> Thrift [1] at all.
>>>
>>> Based on uptake and being a top-level Apache project, I think we might
>> want to consider re-using/basing Drill on Thrift, or, at least, mention it
>> as an option?
>>>
>>> Cheers,
>>> Michael
>>>
>>> [1] http://thrift.apache.org/
>>>
>>> --
>>> Michael Hausenblas
>>> Ireland, Europe
>>> http://mhausenblas.info/
>>>
>>
>>
|