You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2018. It is now read-only.
The spring factories thing allows spring boot to pick up and load the class you made. This is called auto-configuration... like java service loader, but better. Read more here.
ZipkinSparkStreamingConfiguration looks for any beans of type Adjuster and collects them. These are applied in the spark job. By default, only the all-jar goes across the cluster. However, any jar which contains an adjuster is also sent (implicitly via SparkConf.sparkJars). This can also be manually controlled via zipkin.sparkstreaming.spark-jars.
The text was updated successfully, but these errors were encountered:
so the key here is that we shouldn't need a custom build to use an ad-hoc adjuster. In other words, users shouldn't need to re-shade zipkin-dependencies-job, or invalidate docker layers.
Adding an adjuster should be as simple as the following..
zipkin.sparkstreaming.Adjuster
org.springframework.context.annotation.Configuration
META-INF/spring.factories
that containsPut your compiled class and
META-INF/spring.factories
into a jar. Place that jar in the classpath of the spark job.In maven, the following structure would accomplish this.
Why this should work..
The spring factories thing allows spring boot to pick up and load the class you made. This is called auto-configuration... like java service loader, but better. Read more here.
ZipkinSparkStreamingConfiguration
looks for any beans of typeAdjuster
and collects them. These are applied in the spark job. By default, only the all-jar goes across the cluster. However, any jar which contains an adjuster is also sent (implicitly viaSparkConf.sparkJars
). This can also be manually controlled viazipkin.sparkstreaming.spark-jars
.The text was updated successfully, but these errors were encountered: