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.

Sign up for GitHub

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

Jump to bottom

Document upgrade and compatibility policy #117

Open
yurishkuro opened this issue Jul 27, 2018 · 2 comments
Open

Document upgrade and compatibility policy #117

yurishkuro opened this issue Jul 27, 2018 · 2 comments

Comments

@yurishkuro
Copy link
Member

yurishkuro commented Jul 27, 2018 •
edited
Loading

  • the order of upgrades of backend components is always: query, collector, agents
  • compatibility guarantee between backend components: V-1 and V only
  • compatibility between clients and backends: by default backend should be compatible with all clients, but there may be future exceptions
@yurishkuro yurishkuro mentioned this issue Jul 30, 2018
Closed
@jkowall
Copy link
Collaborator

jkowall commented Nov 27, 2024

I think we should provide similar advice to the first bullet, as there is less impact with this method (query first). Since we are using Otel there is no real "agent" but instead collector role (including Kafka which likely needs to have both upgraded together).

I do not see us making schema changes at this point, but should we want to normalize the schema to Otel versus OT we might make this change.

I would see this being part of a FAQ.

I should also remove jaeger-agent from the v2 FAQ :)

@yurishkuro
Copy link
Member Author

We have some compatibility rules in https://github.com/jaegertracing/jaeger/blob/main/README.md#version-compatibility-guarantees

This was referenced Nov 30, 2024
Open
Merged
yurishkuro pushed a commit to jaegertracing/jaeger that referenced this issue Dec 23, 2024
@jkowall
Compatibility updates for v2 in README (#6316)
5b1c76b 
## Which problem is this PR solving?
Addresses part of
jaegertracing/documentation#117

## Description of the changes
Update text to match Jaeger v2

## How was this change tested?
Not tested

## Checklist
- [X] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [X] I have signed all commits

---------

Signed-off-by: Jonah Kowall <jkowall@kowall.net>
Manik2708 pushed a commit to Manik2708/jaeger that referenced this issue Jan 5, 2025
@jkowall @Manik2708
Compatibility updates for v2 in README (jaegertracing#6316)
902136b 
## Which problem is this PR solving?
Addresses part of
jaegertracing/documentation#117

## Description of the changes
Update text to match Jaeger v2

## How was this change tested?
Not tested

## Checklist
- [X] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [X] I have signed all commits

---------

Signed-off-by: Jonah Kowall <jkowall@kowall.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jkowall @yurishkuro