Re: auotscaling tlog+pull and replicationFactor

I am not sure whether you have added triggers for nodelost and nodeadd events Action is taken based on triggers which have the execute plan. You can move create replicas and also delete node in these triggers. One more thing, since you are using solr 7.7 if you add move replica action to the

Re: Admin UI core loading fails

On 4/2/20 5:39 AM, Erick Erickson wrote: What do your Solr logs show? My bet is that your mods to the configs somehow caused the reload to fail too early in the process to be shown in the UI. These are the lines in solr.log that I see lead to the stack trace (core name has been modified to

auotscaling tlog+pull and replicationFactor

Hi there, I'm currently using solr v7.7.2 *(I applied the patch SOLR-13674 to my build to preserve replica types for triggers)* and trying to set up a cluster with the combination of TLOG+PULL replicas and utilising the solr autoscaling feature

unified highlighter methods works unexpected

Hi All, I use Solr 8.4.1 and implement suggester functionality. As part of the suggestions I would like to show product info so I had to implement this functionality with normal query parsers instead of suggester component. I applied an edgengramm filter without stemming to fasten the analysis of

Solr connectivity with Apachhe Kudu and Apache Presto

Hi, Does Solr have connectivity with Apache Kudu, Apache Presto and AWS s3 services. Kindly let me know about this. Regards, Meraj -- * ***Disclaimer** *This email communication (including any attachments) contains information which is confidential and may be legally privileged. It is for

Solr proximity search highlighting issue

Hello Dev Team, I found some problem in highlighting module. Not all the search terms are getting highlighted. Sample query: q={!complexphrase+inOrder=true}"pos1 (pos2 OR pos3)"~30=true Indexed text: "pos1 pos2 pos3 pos4" please find attached response xml screen shot from solr. You can see

Re: Admin UI core loading fails

What do your Solr logs show? My bet is that your mods to the configs somehow caused the reload to fail too early in the process to be shown in the UI. Best, Erick > On Apr 2, 2020, at 02:50, TK Solr wrote: > > I'm on Solr 8.3.1 running in non-solrcloud mode. > > When I tried to reload an

Solr on Kubernetes with solr-operator

So I finally had some time to play with the new Solr Operator (https://github.com/bloomberg/solr-operator) for a client I got a shiny ZK ensemble and a Solr cluster up and running in a few hours, but not without some learning curve. If you want to try and happen to be on a Mac, then I wrote up

Re: FW: Solr proximity search highlighting issue

I may be wrong here, but the problem may be that the match was on your terms pos1 and pos2 (you don't need the pos3 term to match, due to the OR operator) and thus that's what's been highlighted. There's a hl.q parameter that lets you supply a different query for highlighting to the one

Admin UI core loading fails

I'm on Solr 8.3.1 running in non-solrcloud mode. When I tried to reload an existing core from Admin UI's "Core Admin" by clicking Reload, after modifying the core's conf/managed-schema, no error was reported. But the newly added field type is not shown in the core's Analyzer section. I