Configuring load balancer for Kerberised Solr cluster

We are trying to enable authentication mechanism in our Solr cluster using Kerberos authentication plugin. We use Active Directory as our KDC, each Solr node has its own SPN in the form of HTTP/@ and things are working as expected. Things are getting complicated while trying to configure our load

Getting authenticated user inside DocTransformer plugin

We are using Solr's kerberos authentication plugin and we are trying to implement field-level filtering based on the authenticated user and DocTransformer class: public class FieldAclTransformerFactory extends TransformerFactory { @Override public DocTransformer create(String

Reading authenticated user value inside custom DocTransformer

We are using Solr's kerberos authentication plugin and we are trying to implement field-level filtering based on the authenticated user and DocTransformer class: public class FieldAclTransformerFactory extends TransformerFactory { @Override public DocTransformer create(String

Highlighting values of non stored fields

Our use case is as follow: We are indexing free text documents. Each document contains metadata fields (such as author, creation date...) which are kinda small, and one "big" field that holds the document's text itself. For ranking purpose each field is indexed in more then one "variation" and

Re: Leading wildcard searches very slow

Hi, is there any sophisticated way [using the schema] to block brutal regex queries? Thanks -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

UPDATE collection's Rule-based Replica Placement

Hi community, Using Solr 8.3, is there any way to change the replica placment of "running" collection say "from this point forward" or should I recreate the collection and migrate all my data from the existing collection to the new one? Tried to use the COLLECTIONPROP action which doesn't do the

Re: [SOLVED] UPDATE collection's Rule-based Replica Placement

Thanks Ilan and Aroop for replying. So not exactly move but rather *update* the existing set of rules so future replica placement will enforced by them. I managed to do so using the MODIFYCOLLECTION action: