ACCUMULO-756 has been put on the back-burner for now (at least from me). I'd love to revisit it, but unfortunately, I've had other priorities.
As for 0.9.2, I've had a lot of concerns over our continued use of Thrift. It has had serious regressions, and behavior changes in "bug fixes" that have not been expected. I'd be in favor of switching to 0.9.2 for Accumulo 1.8.0, if we can be reasonably assured it's not going to wreak havoc on us like 0.9.0->0.9.1 did. That means time and testing. I think we can go ahead and make a ticket for it (if it's not done already), and if somebody has time to do it for 1.8.0, great. If it turns out to be more trouble than it's worth, or if it causes unnecessary problems, we can postpone or roll back. For 1.7.x, we'll likely stay with 0.9.1, unless our experience working with 0.9.2 on 1.8.0 leads us to believe that it'd be a safe transition. It'd have to be *very* low risk, I imagine... but we'd probably need to discuss further once we have more information. -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Wed, Aug 19, 2015 at 1:56 PM, Josh Elser <[email protected]> wrote: > We talked about updating 1.8.0 to 0.9.2. 1.7 would very likely not be > updated to 0.9.2 due to worry of stability from Thrift (this has been a real > problem in the past). > > Thrift itself needs consistent libraries on both sides of the wire. An 0.9.1 > client doesn't work with an 0.9.2 server. Thrift's compatibility gives us > the ability to run Accumulo 1.6 clients against Accumulo 1.7 servers > (hypothetically). > > Hopefully, you could bump the version, recompile the Thrift code in 1.7 and > it would work if you want to experiment. YMMV > > > Max Thomas wrote: >> >> The latest major thrift release is 0.9.2; Accumulo 1.7 (and the current >> master branch on Github) depends on 0.9.1. 0.9.2 fixes a number of >> issues that are desirable to have, such as functions in Python for hash >> codes. >> >> An initial test with a Java project depending on thrift 0.9.2 and >> accumulo results in an exception when the Accumulo server starts, >> presumably due to conflicting classes. >> >> I have a few questions: >> >> 1) Are there creative Maven things to get Accumulo and thrift 0.9.2 to >> place nicely together without building Accumulo from scratch? >> >> 2) Is there a plan in place to upgrade the thrift dependency for 1.8.0 >> or the 1.7.x line? (Perhaps short term; see below) >> >> 3) I see this issue on JIRA: >> >> https://issues.apache.org/jira/browse/ACCUMULO-756?jql=project%20%3D%20ACCUMULO%20AND%20text%20~%20thrift >> >> >> Is work still active on this issue?
