add option to remove finished run from db after export #55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The indexer crashed since the hdd was too small to keep the data of two runs in the database: the current run, and the latest finished run.
until now we kept the table of the finished run to be able manually export to csv - which is not really needed, so we could just throw the table away after creating the exports.
this pr adds an optional envvar: if
HUBGREP_KEEP_LAST_RUN_IN_DBis 0, we delete the table after export, otherwise (the default) it works as before, and we "rotate" the tables when a run finished.