Skip to content
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

[Feature]: Support ClickHouse storage in Jaeger V2 #5058

Open
1 of 7 tasks
haanhvu opened this issue Dec 29, 2023 · 11 comments
Open
1 of 7 tasks

[Feature]: Support ClickHouse storage in Jaeger V2 #5058

haanhvu opened this issue Dec 29, 2023 · 11 comments

Comments

@haanhvu
Copy link
Contributor

haanhvu commented Dec 29, 2023

Requirement

Support ClickHouse storage in Jaeger V2

Problem

Not supported yet.

Proposal

Open questions

No response

@haanhvu
Copy link
Contributor Author

haanhvu commented Dec 29, 2023

@yurishkuro pls check if I miss anything

@VaibhavMalik4187
Copy link
Contributor

VaibhavMalik4187 commented Jan 23, 2024

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!

@haanhvu
Copy link
Contributor Author

haanhvu commented Jan 23, 2024

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.

@VaibhavMalik4187
Copy link
Contributor

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.

@haanhvu
Copy link
Contributor Author

haanhvu commented Jan 23, 2024

Yeah I think dependency store can be implemented independently from span store. Right @yurishkuro ?

@yurishkuro
Copy link
Member

It can be but only as an extension of already established framework for Ch integration

@haanhvu
Copy link
Contributor Author

haanhvu commented Jan 23, 2024

It can be but only as an extension of already established framework for Ch integration

@yurishkuro So #4941 needs to be merged first right?

@varshith257
Copy link
Contributor

Will look into it

@varshith257
Copy link
Contributor

varshith257 commented May 15, 2024

@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.

@chenlujjj
Copy link

Regarding the "Implement dependency store" task, is a big data job like https://github.com/jaegertracing/spark-dependencies needed as well ?

@yurishkuro
Copy link
Member

@chenlujjj I would say dependency store is much lower priority, but yes, ideally the spark job would be extended to support a different storage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

5 participants