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

Add Badger v1 to v3 migration steps #507

Merged
merged 1 commit into from
Jun 24, 2021

Conversation

Ashmita152
Copy link
Contributor

Signed-off-by: Ashmita Bohara [email protected]

Which problem is this PR solving?

Update documentation with steps to migrate from badger v1 to v3

/cc @jpkrohling

@jpkrohling jpkrohling merged commit 9ef3d8b into jaegertracing:master Jun 24, 2021
@@ -171,6 +171,117 @@ docker run \
jaegertracing/all-in-one:{{< currentVersion >}}
```

#### Upgrade Badger v1 to v3
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We usually do not keep such detailed migration instructions in the core documentation - they are going to become irrelevant soon, but the docs are "forever". I would instead create an .md file in the badger dir in the main repo and link to that file from the changelog.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, I think it might be useful to have it here for this version, and remove for the next one, keeping the doc in the readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants