Open haanhvu opened 9 months ago
@yurishkuro pls check if I miss anything
Hey @haanhvu, and @yurishkuro, I'm interested in contributing to this issue. However, I'm new to the codebase and do not have a deep understanding of the complexities of the tasks mentioned in this issue. While Haanhvu working on span export, do you think that I can start working on the Implement dependency store
item? Looking forward to collaborating with you on these tasks. I'm open to working on other items on the checklist as well. Thank!
However, I'm new to the codebase and do not have a deep understanding of the complexities of the tasks mentioned in this issue.
These tasks are medium in complexity. You're of course welcome to work on these. But they would require more time and effort than good first issues, especially if you're new to Jaeger and ClickHouse.
I'm all in, I'd appreciate it if you could share some pointers about the dependencies between each of these tasks. As a beginner, I'd like to tackle independent tasks first.
Yeah I think dependency store can be implemented independently from span store. Right @yurishkuro ?
It can be but only as an extension of already established framework for Ch integration
It can be but only as an extension of already established framework for Ch integration
@yurishkuro So #4941 needs to be merged first right?
Will look into it
@yurishkuro Can I take up on this issue progress? Or Would I prefer
I think the Kafka exporter left to be work as part of our V2 roadmap.
Regarding the "Implement dependency store" task, is a big data job like https://github.com/jaegertracing/spark-dependencies needed as well ?
@chenlujjj I would say dependency store is much lower priority, but yes, ideally the spark job would be extended to support a different storage.
Requirement
Support ClickHouse storage in Jaeger V2
Problem
Not supported yet.
Proposal
Open questions
No response