-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding flags to enable components #60
Conversation
wait this is a sneaky big feature! you mean this will allow replacement of the spark job, right? Maybe add to README: using as an alternative to zipkin-dependencies |
module/src/main/java/zipkin2/module/storage/kafka/ZipkinKafkaStorageProperties.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe for each flag, comment which api this supports eventhough this layer is below it, it will become more relevant I think.
I think so! :) we could add modules to downstream dependencies to cassandra/elasticsearch/etc later. |
@adriancole did some vars renaming, add docs and created a docker-compose example for only dependency processing. let me know wdyt |
@adriancole I'll be back on Monday, looking forward to your feedback :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only minor notes which can happen later. great work!
module/src/main/resources/zipkin-server-kafka-only-dependencies.yml
Outdated
Show resolved
Hide resolved
Thanks for the review @adriancole ! I will merge this and upgrade to latest zipkin on a minor release. |
bravo! |
In order to effectively disable certain components (aggregation, trace/dependency store) we require additional flags. This will help to users that only want to use certain part of Kafka Storage, as dependency aggregation, then we can disable other components.
Other use-case is when deploying aggregation and storage in separate components. And also to apply
searchEnabled
flag properly on the storage, to disable onlyGET /traces?params
query.Changes: