Thanks John and Stephan for the hard work! *NOTE: If you don't use go bindings to interact with Aurora, feel free to ignore the rest of this message.*
Just a heads up to those those who use go clients and want to maintain version parity: Upgrading to bindings generated by Thrift 0.10.0 to maintain version parity will cause breakage due to a change in the way thrift sets are translated to go maps by the thrift generator (https://issues.apache.org/jir a/browse/THRIFT-3467). Although the thrift issue says this landed in 0.11.0, this change actually landed in Thrift 0.10.0 (https://github.com/apache/ thrift/commits/0.10.0?after=b2a4d4ae21c789b689dd162deb819665567f481c+139). -Renan On Tue, Dec 12, 2017 at 10:43 PM, Bill Farner <wfar...@apache.org> wrote: > After much battling with tools, tests, and jenkins; John upgraded us to > thrift 0.10.0 by landing r/64290 <https://reviews.apache.org/r/64290/>! > > The next time you pull, you will likely notice that you have some stale > untracked files. You can safely clean these up: > > $ rm -r build-support/thrift/thrift-0.* > > You may also notice that you no longer have to bootstrap the thrift > compiler by compiling it; meaning that building from scratch should be > noticeably faster! > > I scanned the changelog for thrift 0.9.2, 0.9.3, 0.10.0, and there is only > one feature i found potentially useful: > > THRIFT-640 <https://issues.apache.org/jira/browse/THRIFT-640> Support > deprecation > > There are a handful of modest performance improvements that we will benefit > from: > > THRIFT-2877 <https://issues.apache.org/jira/browse/THRIFT-2877> Optimize > generated hashCode > THRIFT-3306 <https://issues.apache.org/jira/browse/THRIFT-3306> Java: > TBinaryProtocol: Use 1 temp buffer instead of allocating 8 > THRIFT-2172 <https://issues.apache.org/jira/browse/THRIFT-2172> Java > compiler allocates optionals array for every struct with an optional field > THRIFT-3431 <https://issues.apache.org/jira/browse/THRIFT-3431> Avoid > "schemes" HashMap lookups during struct reads/writes > > > Many thanks to John and Stephan for their hard work getting us upgraded! >