Re: In production solr cloud 4.6 is not working

Hi , Anyone Please suggest. On Sat, 11 Jan, 2020, 12:33 AM Rajdeep Sahoo, wrote: > Hi all, > In production we have done the set up of solr cloud with solr version > 4.6 , the set up contains 3 zookeeper and 4 shards each having three > replicas, a total of 12 solr nodes. > Active indexing wa

Re: Search phrase not parsed properly

I would _definitely_ follow Walter’s advice (take the stopword filter out) as my starting point. It’ll make your life a lot easier. I’ll add that I have seen clients with very large clusters that were willing to deal with the issues inherent in stopwords (and there are more than just this) for

Re: Search phrase not parsed properly

Remove ALL the stopwords. Remove the stopword filter. This will happen again and again with different words until you do that. Stopwords were necessary with 16-bit CPUs. I stopped using them in 1996. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On J

Re: Search phrase not parsed properly

I would follow Shawn's advice: remove the stopword filter from your field types' analysis chain... Up to you, as usual. Best, Edward Em sex, 10 de jan de 2020 23:12, chester escreveu: > Thanks, everyone. I found the stopword_en.txt file and saw that "will" was > included in there. I removed it

Re: Search phrase not parsed properly

Thanks, everyone. I found the stopword_en.txt file and saw that "will" was included in there. I removed it and have re-indexed the core. Hopefully, that will fix the issue. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Search phrase not parsed properly

The easiest way to verify this is to use the admin UI. Select a core (or replica), go to the analysis page. Select the field in question from there and type the words into the textbox. I’d also uncheck the “verbose” box, the detailed information resulting from that is unnecessary. Do note that

Re: Search phrase not parsed properly

Here is the stopwords' file for english: https://github.com/apache/lucene-solr/blob/ branch_8_3/solr/server/solr/configsets/_default/conf/lang/stopwords_en.txt

Re: remote debugging for docker solr

Could you share the content of your docker-compose.yml file? Did you export the 5005 port in the cited file YAML file? Best, Edward Em sex, 10 de jan de 2020 20:43, Arnold Bronley escreveu: > Hi, > > I have a running dockerized instance of Solr which runs fine with the > following setting for

Re: Search phrase not parsed properly

You have to check your managed-schema to see if the field type defines a stopwordfilter and which one it points to. There's a folder named 'lang' with many files, one for each language. If your field is configured to english the filter will point to lang/stopword_en.txt. The stopwords.txt file is

Re: Search phrase not parsed properly

I checked the stopwords.txt file and it is empty. That means "will" is not a stop word, correct? -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Search phrase not parsed properly

Hi, It looks like you are using the stopword filter and 'will' is a stop word, so it is removed by the the analysis chain of the field. Please, test the analysis chain in Solr Admin UI to see if this is the case. Best, Edward Em sex, 10 de jan de 2020 21:30, chester escreveu: > I'm using solr

Re: Search phrase not parsed properly

On 1/10/2020 5:30 PM, chester wrote: I'm using solr 6.3 and am having an issue with a certain search phrase. When I search for the phrase "Perkins AND Will", the parsed query does not include "Will". See debug info below. select?q=firmname:(Perkins%20AND%20Will) "debug":{ "rawquerystring"

Search phrase not parsed properly

I'm using solr 6.3 and am having an issue with a certain search phrase. When I search for the phrase "Perkins AND Will", the parsed query does not include "Will". See debug info below. select?q=firmname:(Perkins%20AND%20Will) "debug":{ "rawquerystring":"firmname:(Perkins AND Will)", "que

remote debugging for docker solr

Hi, I have a running dockerized instance of Solr which runs fine with the following setting for command option for solr service in docker-compose.yml file command: > bash -c "solr start -cloud -s /var/lib/solr -t /var/data/solr; set -x; export; wait-for-solr.sh;" Recently, I wanted

Re: Solr 8.x Startup problems when ZK is partially unavailable

I’ve also seen timeout with zkCli.sh of Solr8.4 when connected to 3 ZK and the first is not accessible. Solr 8.4 has ZK3.5.5 while 7.x has Zk3.4.x Jan Høydahl > 10. jan. 2020 kl. 17:44 skrev Markus Jelsma : > > Hello, > > I have multiple collections, one 7.5.0 and the rest is on 8.3.1. They a

In production solr cloud 4.6 is not working

Hi all, In production we have done the set up of solr cloud with solr version 4.6 , the set up contains 3 zookeeper and 4 shards each having three replicas, a total of 12 solr nodes. Active indexing was going on , after switching on we are experiencing a lot of issues , all the nodes stopped ser

Solr 8.x Startup problems when ZK is partially unavailable

Hello, I have multiple collections, one 7.5.0 and the rest is on 8.3.1. They all share the same ZK ensemble and have the same ZK connection string. The first ZK address in the connection string is one that is not reachable, it seems firewalled, the rest is accessible. The 7.5.0 nodes do not ap

Re: Edismax ignoring queries containing booleans

Cool, glad to help, Paras and Claire. :) Cheers, Edward Em sex, 10 de jan de 2020 06:31, Paras Lehana escreveu: > Hi Edward, the way you have explained mm and fq's relation with parser has > cleared all my potential queries. I didn't know fq supports other parsers. > :) > > On Fri, 10 Jan 2020

Re: Solr suggester : duplicate suggestions

@Paras Lehana.. Thanks for the reply Yes "and" is present in the stop words list. Dhanesh S.RSenior Technical Leade : dhan...@hifx.co.in | w : www.hifx.in712 t : (+91) 484 4011750 m : (+91) 994 666 6703 On Fri, Jan 10, 2020 at 3:07 PM Paras Lehana wrote: > Hi Dhanesh, > > Although I hand

RE: Edismax ignoring queries containing booleans

Hi Edward, Thank you so much for your reply. Your explanations have really helped me understand the impact of mm on our queries 😊 I'm going to try what you suggest but I agree, it seems like 2 or 3 is the best option for us. We still would like the behaviour of mm on certain queries, so removi

Re: Performance of Bulk Importing TSV File in Solr 8

Hi Joseph, Although your indexing rate is fast at around 2800 docs/sec, you can play with values of autoCommit, mergePolicy and ramBufferSize. You can post existing values of these to make us comment about those. As Mikhail suggested, batches can increase performance by committing in between. O

Re: Facet Range by Distance generating count of field - need sum of the field

Hi Robert, How does this work? {!frange l=0 u=5} sum(geodist()) On Fri, 3 Jan 2020 at 21:10, Robert Scavilla wrote: > Thank yo in advance for your help. > > I need to get the sum of a pivot range field. The following query uses the > stats function to sum the *sumField* values. I'm trying to

Re: Solr suggester : duplicate suggestions

Hi Dhanesh, Although I handle Auto-Suggest, I have worked a little with Suggester component. Suggester provides results as you type. Do you really need it? Also, I don't know if I'm correct, but where have you described '&' to be replaced with 'and'? Is 'and' present in your stopwords list? I th

Re: Edismax ignoring queries containing booleans

Hi Edward, the way you have explained mm and fq's relation with parser has cleared all my potential queries. I didn't know fq supports other parsers. :) On Fri, 10 Jan 2020 at 10:46, Edward Ribeiro wrote: > The fq is not affected by mm parameter because it uses Solr's default query > parser (Luc