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

[query] Update v1 Query Service To Accept v2 Storage API #6480

Closed
mahadzaryab1 opened this issue Jan 4, 2025 · 0 comments · Fixed by #6485
Closed

[query] Update v1 Query Service To Accept v2 Storage API #6480

mahadzaryab1 opened this issue Jan 4, 2025 · 0 comments · Fixed by #6485

Comments

@mahadzaryab1
Copy link
Collaborator

mahadzaryab1 commented Jan 4, 2025

As per #6460 (comment),

  • keep v1 query service as is, operating on v1 storage
  • make the constructor of query service accept v2 storage only
  • the constructor should check if v2 storage is actually an adapter over v1, if so retrieve v1 reader and operate as usual
  • otherwise, apply another adapter that wraps native v2 storage into v1 reader API
@mahadzaryab1 mahadzaryab1 self-assigned this Jan 4, 2025
yurishkuro pushed a commit that referenced this issue Jan 4, 2025
…6482)

## Which problem is this PR solving?
- Towards #6480

## Description of the changes
- This PR changes the v1 query service to check for the v1 adapter at
construction rather than at method invocation.
- Currently, the constructor will panic if its provided a native v2
storage implementation. This will be remedied in a follow-up PR that
will implement a reverse adapter to go from v2->v1.

## How was this change tested?
- CI and added a unit test

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

---------

Signed-off-by: Mahad Zaryab <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant