Thanks Emir. I’m unfortunately already using a routing key that needs to be at
the top level, since I’m collapsing on that field.
Adding a sub-key won’t help much if my theory is correct, as even a single
shard (distrib=false) showed serious performance degradation, and query latency
is the ma
Hi Jeff,
I will not comment on your theory (will let that to guys more familiar
with Lucene code) but will point to one alternative solution: routing.
You can use routing to split documents with different permission to
different shards and use composite hash routing to split "A" (and maybe
"B
