If documented, some text alerting the user to the difficulties possible if schemas don't match, and relevancy not working as well due to different term frequencies among collections (except maybe it will be ok with use of a stats cache?) It's kind of a tricky thing to use, mostly applicable in carefully designed custom solutions. Doesn't mean it should be undocumented however.
On Tue, Dec 14, 2021 at 4:07 PM Eric Pugh <ep...@opensourceconnections.com> wrote: > I suspect it’s more like this never was documented ;-). > > On Dec 14, 2021, at 2:59 PM, Mikhail Khludnev <m...@apache.org> wrote: > > Hello, Colleagues. > > I remember this param from early beginning > https://github.com/apache/solr/blame/main/solr/core/src/java/org/apache/solr/handler/component/CloudReplicaSource.java#L76. > And every time I wondered why it's out of reference guide. > Is it a kind of backdoor? Is it described somewhere already? Where can I > put it? > > Thanks > -- > Sincerely yours > Mikhail Khludnev > > > _______________________ > *Eric Pugh **| *Founder & CEO | OpenSource Connections, LLC | 434.466.1467 > | http://www.opensourceconnections.com | My Free/Busy > <http://tinyurl.com/eric-cal> > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed > <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> > This e-mail and all contents, including attachments, is considered to be > Company Confidential unless explicitly stated otherwise, regardless > of whether attachments are marked as such. > > -- http://www.needhamsoftware.com (work) http://www.the111shift.com (play)
