Fix issue with TTL policies in set_up_composite_indexes_and_ttl_policies #70
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.
This PR fixes the issue that if you were using
get_all_subclasses()to gather the models to pass into theasync_set_up_composite_indexes_and_ttl_policies()orset_up_composite_indexes_and_ttl_policies()like suggested in the README, like this:the indexes were created but the TTL policies were not. The
get_all_subclasses()method returns an iterator and the underlyingset_up_composite_indexesused up the generator so that the call to theset_up_ttl_policiesgot an empty generator. This fixes it by simply converting it to a list before passing it to each of the underlying functions and updates the test to spot the issue.