Create Clickhouse config

[adityachopra29]

Which problem is this PR solving?

• Solves [jaeger-v2][storage] Add Configuration For ClickHouse #6154

Description of the changes

• Create plugin/storage/clickhouse/
• This is a draft pr, not ready to be merged.

How was this change tested?

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[adityachopra29]

This is a draft pr.
@yurishkuro I am having trouble writing the schema config, as we dont have a schema ready right now.
Also wanted to confirm whether I am on the right track.
Also, wanted to understand how we will be deciding the default configuration values.
I took inspiration from the badger and cassandra config and structure

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 7 lines in your changes missing coverage. Please review.

Project coverage is 95.97%. Comparing base (20bdd8d) to head (1536983).

Files with missing lines	Patch %	Lines
pkg/clickhouse/config/config.go	0.00%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6622      +/-   ##
==========================================
- Coverage   96.00%   95.97%   -0.04%     
==========================================
  Files         365      366       +1     
  Lines       20616    20623       +7     
==========================================
  Hits        19792    19792              
- Misses        626      633       +7     
  Partials      198      198              

Flag	Coverage Δ
badger_v1	9.92% <ø> (ø)
badger_v2	1.84% <ø> (ø)
cassandra-4.x-v1-manual	15.08% <ø> (ø)
cassandra-4.x-v2-auto	1.83% <ø> (ø)
cassandra-4.x-v2-manual	1.83% <ø> (ø)
cassandra-5.x-v1-manual	15.08% <ø> (ø)
cassandra-5.x-v2-auto	1.83% <ø> (ø)
cassandra-5.x-v2-manual	1.83% <ø> (ø)
elasticsearch-6.x-v1	19.30% <ø> (ø)
elasticsearch-7.x-v1	19.38% <ø> (ø)
elasticsearch-8.x-v1	19.56% <ø> (ø)
elasticsearch-8.x-v2	1.84% <ø> (-0.12%)	⬇️
grpc_v1	11.04% <ø> (ø)
grpc_v2	7.89% <ø> (ø)
kafka-3.x-v1	10.21% <ø> (ø)
kafka-3.x-v2	1.84% <ø> (ø)
memory_v2	1.84% <ø> (ø)
opensearch-1.x-v1	19.44% <ø> (ø)
opensearch-2.x-v1	19.44% <ø> (ø)
opensearch-2.x-v2	1.84% <ø> (ø)
tailsampling-processor	0.48% <ø> (ø)
unittests	94.78% <0.00%> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[adityachopra29]

Just realised a structure change is required. Will make it and update the pr shortly.

[yurishkuro]

What is the motivation for the specific config parameters you are introducing? It feels a bit like putting the horse in front of the carriage - we don't have an implementation of the storage yet, so how do we know which config options will even be required?

[zzzk1]

you can try: https://clickhouse.com/docs/en/integrations/go#connecting-1

[zzzk1]

Only the following are required for a mini connection: 1. host 2. port 3. database 4. username 5. password.

[adityachopra29]

Thanks!

[adityachopra29]

What is the motivation for the specific config parameters you are introducing? It feels a bit like putting the horse in front of the carriage - we don't have an implementation of the storage yet, so how do we know which config options will even be required?

@yurishkuro I see. I looked through the configurations for the other db storages, and saw what types of configurations jaeger was using to model config for clickhouse. But adding config as we develop is more logical.
I have moved the config to /pkg/clickhouse and also removed the extra config. Pls have a look