I do think as we near 1.0 we should choose one thrift implementation. Carrying two with one in an incomplete state is confusing and an invitation to code rot.
Given the state of the alternatives, one reasonable course of action would be to keep the thift1 interface in tree and move the thrift2 one to Github. If eventually thrift2 is in a finished state and popular, perhaps it could be pulled back in. > On Sep 19, 2014, at 3:40 AM, Lars George <lars.geo...@gmail.com> wrote: > > We had others report their use earlier (previous thread about removing it). > So it is definitely in use. But... I agree it needs to be completed. I know > I have been tardy on this and need to speed up. :( Darn work always comes > in between. > > On Thu, Sep 18, 2014 at 11:48 PM, Andrew Purtell <apurt...@apache.org> > wrote: > >> Survey: Is anyone using the Thrift 2 interface? >> >> Not here. >> >>> On Thu, Sep 18, 2014 at 2:24 PM, Stack <st...@duboce.net> wrote: >>> On Thu, Sep 18, 2014 at 3:56 AM, Kiran Kumar.M.R < >> kiran.kumar...@huawei.com> >>> wrote: >>> >>>> Hi, >>>> Our customers were using Hbase-0.94 through thrift1 (C++ clients). >>>> Now HBase is getting upgraded to 0.98.x >>>> >>>> I see that thrift2 development is going on ( >>>> https://issues.apache.org/jira/browse/HBASE-8818) >>> >>> It has stalled with quite a while now. >>> >>> >>> >>>> Customers are interested in continuing to use thrift1 as they are not >>>> interested in new capability given in thrift2 and also minimize their >>>> application changes as much as possible. >>>> >>>> What should be our direction in using thrift interface? >>>> >>>> - Shall we continue to use thrift1? (Will this continue to be >>>> supported, I see some mail threads on making it deprecated) >>> IMO this would be safest. >>> >>> >>> >>>> - Or suggest our customers to switch to thrift2? >>> >>> >>> Unless anyone is interested in seeing through the thrift2 project to the >>> finish, I think we should just purge it from the codebase and stay >> thrift1. >>> >>> St.Ack >> >> >> >> -- >> Best regards, >> >> - Andy >> >> Problems worthy of attack prove their worth by hitting back. - Piet >> Hein (via Tom White) >>
