The way we build the bits as part of the release process changed quite a bit during that release so there were some hiccups.
This seems like an oversight, though I tried to build them as close as possible to the releases before 2.7.3. We can fix this for the next releases. +Vinod > On Sep 30, 2016, at 7:46 PM, tsuna <tsuna...@gmail.com> wrote: > > Hi there, > Why are releases up to 2.7.2 shipped with a libhadoop.so built with Snappy > support but 2.7.3 not? I couldn’t find anything in the release notes or ML > archives that would indicate that this was an intentional change. > > hadoop-2.7.2/lib/native/libhadoop.so.1.0.0: > 0000000000014fb0 > <Java_org_apache_hadoop_util_NativeCodeLoader_buildSupportsSnappy>: > 14fb0: b8 01 00 00 00 mov $0x1,%eax > 14fb5: c3 retq > (this means return true;) > > hadoop-2.7.3/lib/native/libhadoop.so.1.0.0: > 0000000000014160 > <Java_org_apache_hadoop_util_NativeCodeLoader_buildSupportsSnappy>: > 14160: 31 c0 xor %eax,%eax > 14162: c3 retq > (this means return false;) > > Are Snappy users expected to rebuild libhadoop.so from scratch or is this an > unintentional change in the release process? > > -- > Benoit "tsuna" Sigoure
