Adding option to ignore lineage when indexing, #398 #473
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.
Reason for this pull request
During new product development it is often necessary to create temporary databases to index new product data for reviewing purposes. This can often take long time due to lineage data being added to the fresh db, even though it is not relevant in this context (the DB is transient and will be deleted anyway, and the tests do not care about lineage data).
Proposed changes
--ignore-lineage
and--confirm-ignore-lineage
optionsThe first one only works during interactive runs and asks user to confirm the intent, second one can be used in scripts.
docs/about/whats_new.rst
for all changes