Shawn,
I knew that the shard had to be specified by the indexing process or
document, but I didn't realize that the uniqueness of the document across
the collection also had to be handled outside of solr as well.
We've used the compositeId router successfully to route documents, but it
seemed
On 3/14/2018 9:26 AM, Chris Ulicny wrote:
We've been looking at using implicit for one of our collections, and there
seems to be some weird behavior that we're not sure whether it was expected
or not.
Is it recommended to use a uniqueKey for implicit routing? Is the following
behavior intended?
Hi all,
We've been looking at using implicit for one of our collections, and there
seems to be some weird behavior that we're not sure whether it was expected
or not.
Is it recommended to use a uniqueKey for implicit routing? Is the following
behavior intended?
We have encountered the following
