On Monday, September 6, 2010, Jonathan Ellis <jbel...@gmail.com> wrote: > Thrift does not support method overloading (methods with the same name > but different parameters). > > On Mon, Sep 6, 2010 at 9:09 AM, Edward Capriolo <edlinuxg...@gmail.com> wrote: >> On Mon, Sep 6, 2010 at 3:33 AM, Ran Tavory <ran...@gmail.com> wrote: >>> we don't have one version that supports both versions. >>> you can hack it if you download the source code (create two java package >>> trees for 0.6.0 and 0.7.0) but it's not on the shelf, sorry... >>> >>> On Mon, Sep 6, 2010 at 12:39 AM, Edward Capriolo <edlinuxg...@gmail.com> >>> wrote: >>>> >>>> I am looking to move from 6.0 to 7.0 soon. Will one version of hector >>>> support both 6.0 and 7.0? This would be great as performing a >>>> cassandra upgrade and an app server upgrade at the same time is always >>>> tricky? >>>> >>>> Thank you, >>>> Edward >>> >>> >>> >>> -- >>> /Ran >>> >> >> I am going to cross post this to get the vibe on what people are >> thinking. Does it make sense that the thrift api for 7.X should also >> have deprecated methods that match the signature of 6.X? In this way, >> code that was linked to the old signatures would not have to be >> recoded. >> >> As i said above timing, an upgrade and deploying new code across two >> clusters with minimal downtime is tricky. >> >> Edward >> > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of Riptano, the source for professional Cassandra support > http://riptano.com >
I was not aware of that. Also is the default for 6.o non framed and 7.o framed? I was thinking possibly replace cassanda.client detect the server version and use reflection. This way hector sees the same interface to thrift
