Re: A problem with Spark 1.3 artifacts

Maybe you have some sbt-built 1.3 version in your ~/.ivy2/ directory that's masking the maven one? That's the only explanation I can come up with... On Tue, Apr 7, 2015 at 12:22 PM, Jacek Lewandowski < jacek.lewandow...@datastax.com> wrote: > So weird, as I said - I created a new empty project wh

Re: A problem with Spark 1.3 artifacts

So weird, as I said - I created a new empty project where Spark core was the only dependency... [image: datastax_logo.png] JACEK LEWANDOWSKI DSE Software Engineer | +48.609.810.774 | jacek.lewandow...@datastax.com [image: linkedin.png]

Re: A problem with Spark 1.3 artifacts

BTW, just out of curiosity, I checked both the 1.3.0 release assembly and the spark-core_2.10 artifact downloaded from http://mvnrepository.com/, and neither contain any references to anything under "org.eclipse" (all referenced jetty classes are the shaded ones under org.spark-project.jetty). On

Re: A problem with Spark 1.3 artifacts

My hunch is that this behavior was introduced by a patch to start shading Jetty in Spark 1.3: https://issues.apache.org/jira/browse/SPARK-3996. Note that Spark's *MetricsSystem* class is marked as *private[spark]* and thus isn't intended to be interacted with directly by users. It's not super lik

A problem with Spark 1.3 artifacts

A very simple example which works well with Spark 1.2, and fail to compile with Spark 1.3: build.sbt: name := "untitled" version := "1.0" scalaVersion := "2.10.4" libraryDependencies += "org.apache.spark" %% "spark-core" % "1.3.0" Test.scala: package org.apache.spark.metrics import org.apache.s