Having same asset indexed twice would add overhead in terms of async indexing speed and space consumption by index. So if possible avoid such a setup
> We could assume that we always add a path restriction, but I'm not sure how > index movement can help. I mean, both indexes contains documents under > /nodeA/nodeB/nodeC so any query under this path is satisfied by both One way it would help is that entryCount for second index would be smaller compared to first and hence queries with path restriction for second index would have lesser cost Chetan Mehrotra
