On 24 June 2014 16:22, Andrew Wang <andrew.w...@cloudera.com> wrote: > Steve can do a better job explaining > this to me, but we haven't bumped things like Jetty or Guava because they > are on the classpath and are not compatible. There is this line in the > compat guidelines: >
The current jetty version has unreliability issues, which can only be mitigated by updating or moving away from. MR did the latter, webHDFS has yet to do either. Guava is trouble as it aggressively deprecates things...if we move to a new version we know that some code that runs against the version we distribute today will fail. AFAIK the three uses we make of it are (a) @VisibleForTesting (b) Preconditions.* (c) enhanced collections If that's the case, we can strip out guava from Hadoop entirely. (a) and (b) are trivial to replicate in our own code; (c) perhaps cut and paste. Then we could just drop it and say "please use the version you like" -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
