Requirement

As Jaeger-V2 is currently being developed, it would be nicer if the remote storage API had the same API with query service so it could be reused between components.

Problem

As discussed in #5322 (comment), by changing the remote storage API to be the same as the query storage API, we can reuse this API for Jaeger-V2 e2e testing purposes.

Proposal

No response

Open questions

• Remote storage APIs have read & write span, read & write archive span, get capabilities, and read dependencies while query storage APIs only have read span data. So, the scope of this feature is to change the read span, archive span, and dependencies. Is this correct?

• I have looked into query service API and there are v2 and v3, in which v3 uses OTLP model while v2 uses Jaeger model. V3 handles most v2's API except ArchiveTrace and GetDependencies. Do we need to use partially v3 APIs and v2 for the rest or fully v2 APIs?