Are there any known performance issues to consider in the event that we use
a very large number of aliases in an ES cluster? The use case that
motivates this question is a follows.
Here is an extremely- simplified representation of some data we want to
"type": "file" | "container",
The is a UUID. Our thoughts are to have an
over-sharded index to start with for storing all of these objects in, using
the "parent" as a route. If a given parent container ends up with enough
objects in it such that searches for the objects inside that container
start to become non-performant, we can re-index that container's
information into its own index and update the alias for that container
This means that any time we create a container, we create alias to use when
searching that container's list of children, and the number of containers
in the system will get large.
Thanks in advance for any feedback you may have.