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

Handle gitbase index data compatibility on upgrades #337

Open
carlosms opened this issue Mar 15, 2019 · 0 comments · Fixed by src-d/jgit-spark-connector#338
Open

Handle gitbase index data compatibility on upgrades #337

carlosms opened this issue Mar 15, 2019 · 0 comments · Fixed by src-d/jgit-spark-connector#338
Labels
enhancement New feature or request triage/needs-product-input

Comments

@carlosms
Copy link
Contributor

Related to #336.

Right now engine does not handle what happens when we upgrade gitbase, and there is existing index data in ~/.srcd.
This issue is to discuss how we want to handle the case when gitbase breaks compatibility with previous index data. For example, this is documented as a breaking change of gitbase 0.19
@carlosms carlosms added the enhancement New feature or request label Mar 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request triage/needs-product-input
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #337 issue zurk/engine
1 participant
@carlosms