Skip to content
This repository has been archived by the owner on Oct 13, 2021. It is now read-only.

How to create a separate index for each git commit and allow browsing code as of old commits #684

Closed
mbautin opened this issue Feb 27, 2019 · 3 comments
Labels
ARCHIVED CLOSED at time of archiving

Comments

@mbautin
Copy link

mbautin commented Feb 27, 2019

If the entire index is being rebuilt for every commit and then atomically switched, is it possible, instead of throwing old indexes away, save N latest indexes to allow people to browse code as of a particular commit within that range?

@erikrose
Copy link
Contributor

There's technically no reason you couldn't do it, though you'd chew up a lot of space very quickly. ES indices are BIG due to all the different ways Lucene likes to index things.

@mbautin
Copy link
Author

mbautin commented Mar 7, 2019

So currently if we wanted to do this, what would be the recommended way? Creating a separate tree for each commit, and maintaining a config file listing all the trees which could be used with dxr serve?

@erikrose
Copy link
Contributor

erikrose commented Mar 7, 2019

I suppose, though that sounds like a pain in the neck. I'd make some code changes if you were really interested.

@cknowles-admin cknowles-admin added the ARCHIVED CLOSED at time of archiving label Oct 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ARCHIVED CLOSED at time of archiving
Projects
None yet
Development

No branches or pull requests

3 participants