Can we connect our backend to multiple indexes per STAC catalog?

cedadev / search-futures

Future Search Architecture

BSD 2-Clause "Simplified" License

0 stars 0 forks source link

Can we connect our backend to multiple indexes per STAC catalog? #143

Open agstephens opened 2 years ago

agstephens commented 2 years ago

@rhysrevans3 @Mahir-Sparkess: Let's talk about this tomorrow.

Do we need to add a level of routing? Do we need to add versioning in the API? Will those affect the transactional endpoint?

Mahir-Sparkess commented 2 years ago

https://github.com/cedadev/stac-fastapi-elasticsearch/blob/68b93de1c749a5e9972afc37b99b1980b332735b/conf/defaults.py#L17-L19

In the settings.py, stac-fastapi-elasticsearch points to one index each, is it possible to point to multiple indices and how would this work for transactions?

rhysrevans3 commented 2 years ago

Could we use aliases? https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-aliases.html

rhysrevans3 commented 2 years ago

How does this effect the transaction api