Monthly rolling index with custom routing

Hi,
I am trying to figure out the how to create a monthly rolling index with custom routing (multi-tenancy scenario) , with these requirements :

  • WRITE flow : Each document will have a timestamp and the document should be indexed to the appropriate backing index based on that timestamp and not to the latest index. Also, write requests will have a custom routing key (eg: customerId) so they hit a specific shard.
  • READ flow : Requests must be routed to all backing indexes. Requests will have a custom routing key specified (eg: customerId) and results must be aggregated and returned.
  • Index creation : Rolling the index should be automated. Each index should have a custom routing key (eg: customerId )

Wondering, what are the options available ?

Welcome to our community! :smiley:

Given your first condition, you will need to handle this all yourself using time based indices and curator (or similar).

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.