No, this is on purpose. Have a look at the build POM. A few Guava classes were used in the public API for Java and have had to stay unshaded. In 2.x / master this is already changed such that no unshaded Guava classes should be included.
On Tue, Jan 12, 2016, 07:28 Jake Yoon <sungji...@gmail.com> wrote: > I found an unshaded google guava classes used internally in > spark-network-common while working with ElasticSearch. > > Following link discusses about duplicate dependencies conflict cause by > guava classes and how I solved the build conflict issue. > > > https://discuss.elastic.co/t/exception-when-using-elasticsearch-spark-and-elasticsearch-core-together/38471/4 > > Is this worth raising an issue? > > -- > Dynamicscope >
