Promote index store to frontend feature #270
Merged
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 :class:
IndexFetcher
is a user-friendly fetcher built on top of our internal Argo index file store.But for one familiar with Argo index files and/or who cares about performances, it may be interesting to use directly the Argo index store. We thus try to promote this internal feature as a frontend class :class:
ArgoIndex
.As explained in the doc, we have to choose which store to use for index:
The goal here, is to have a new class ``ArgoIndex```:
that will be
indexstore_pa
if Pyarrow is available or fall back onindexstore_pd
otherwise.