Sure. You cannot learn if you don't try.

Hi @yurishkuro I hope you're doing well. I'm relatively new to Jaeger and I'm excited about the opportunity to contribute. I’d love to get involved and make some meaningful contributions. I am looking forward to learning from the community!

can you tell how to download all the dependencies for jaeger in order to contribute

There are no dependencies aside from Go tool chain (and we only support Linux-like environment). Please use Discussions for these types of questions, as they are distracting from the main topic of this issue.

their is no integration_test.go

The test is linked in the description.

Hi @yurishkuro,

Currently, the StorageIntegration test methods rely on the model.Trace data structure for traces. Since the storage_v2 API is built around OpenTelemetry's ptrace.Traces (pdata module), I have the following questions:

1. Do we need to rewrite the StorageIntegration test methods and supporting functions to use ptrace.Traces instead of model.Trace?
2. For the test fixtures (e.g., JSON files) that are currently formatted for the Jaeger model.Trace structure, do we need to convert or rewrite them to comply with the storage_v2 API's data format? Or is there a recommended way to handle this transition dynamically during tests?

@ekefan yes we need to update the business logic of the tests to use ptrace model. We need to find a way to do that incrementally, not in a single humongous PR. Maybe for some time we will need to live in a state where implementations provide both v1 and v2 storage objects while we gradually transition the tests.

We don't need to change json fixtures just yet, because we can easily transform them from model to ptrace.