[WIP] Defer index creation in view stages until usage? #5326
+21
−10
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.
Create indexes in view stages in their
to_mongo()
method rather thanvalidate()
.The motivation here is to defer potentially expensive actions like index creation until the view is actually used, rather than performing them immediately when the view is created.
As currently implemented,
create_index()
could be called in surprising circumstances, eg an operation that requires loading a saved view but not actually iterating over it.Marking this PR as a draft so we can ponder this change a bit more, as there are other view stages (
to_frames()
,to_patches()
, etc) that do perform expensive operations immediately when the view is created 🤔Example usage