Implement Storage API v2 that operates on OTLP batches

[yurishkuro]

Summary

In OTEL-based Jaeger-v2 we don't want to force OTLP trace data to go through unnecessary transformation into Jaeger's current data model. We want to define a V2 version of the storage API so that the OTLP data can be passed through the receiver-exporter pipeline without additional conversions, for better efficiency.

Problem

More discussion in the doc https://docs.google.com/document/d/1s4_6VgAS7qAVp6iEm5KYvpiGw3h2Ja5T5HpKo29iv00/edit#heading=h.hlhu8pegwdcj

Progress

• Define Storage V2 API [jaeger-v2] Define an internal interface of storage v2 spanstore #5399
• Write path
  • Change jaegerstorage extension to expose Storage V2 API [v2] Add v1 factory converter to v2 storage factory #5497
  • Change storageexporter to use V2 API exclusively [v2] Add v1 factory converter to v2 storage factory #5497
    • This is achieved by using an adapter that provides v2 API over v1 storage implementation, for writes only
• Read path (more complicated)
  • discussed in the Migration section of the doc
• Remove jaegerstorage.GetStorageFactory once not used
• Implement v2 API in the backends Upgrade Storage Backends to V2 Storage API #6458 - tracked separately

[tarhphilomina]

Can I take this issue ?

[yurishkuro]

you can try - this is a design issue

[mahadzaryab1]

@yurishkuro For the read path implementation, do we just want to expand the v2 adapter to implement spanstore.Reader (in storage_v2) that just wraps the v1 implementation?