Re: When search term has two stopwords ('and' and 'a') together, it doesn't work

Hi So I don't think removing it completely is the way to go from the scenario > we have Removing stopwords is another story. I'm curious to find the reason assuming that you keep on using stopwords. In some cases, stopwords are really necessary. Quite a considerable increase If q.alt is

Re: subquery highlight

Oh.. gosh. Sure. Subquery yields doc results only, neither of facets, highlighting is attached to response. On Mon, Nov 11, 2019 at 10:07 AM Vasily Ogar wrote: > My subquery is products I tried product.hl=on=products.title > products.description and like this product.hl=on=title > description

Re: Solr as a windows service

Hey Thushara, Have you followed Installing Solr for Windows already? On Sat, 9 Nov 2019 at 10:42, wrote: > Hi, > > I am using solr 8.3 and I need it to use as a running background windows > service. After the 5x release it’s not

Re: Solr 7.7.0: Log file not getting generated

Hey Paresh, Please see permanent logging in Configuring Logging . Check what is your log directory. On Mon, 11 Nov 2019 at 12:27, Paresh wrote: > Hi, > > We just moved to Solr 7.7.0 and log file is

Re: subquery highlight

My subquery is products I tried product.hl=on=products.title products.description and like this product.hl=on=title description and like this hl=on=title description and hl.products=on=title description. I don't know what else On Mon, Nov 11, 2019 at 8:25 AM Mikhail Khludnev wrote: > Hello, >

Printing NULL character in log files.

Hello, Solr Community: I am using Solr7.4.0 which uses log4j (version 2.11 from Solr's Chanes.txt) as its component. Some of the log files that Solr generated contain <0x00> (null characters) in log files (like below) Because of this issue, it is difficult for me to trace what actually happened

Solr 7.7.0: Log file not getting generated

Hi, We just moved to Solr 7.7.0 and log file is not getting generated. Even log folder is not present there. I manually enabled all the logs through Solr-admin UI but it is not working. Is there any other way to enable the logs and how can we enable it at the start of Solr? Any help is

Re: Solr missing mandatory uniqueKey field: id or Unknown field

Hi Sthitaprajna, In Admin UI, select core and go to Schema. Select "title" and post the screenshot (try to host it). Do the same for "id". On Mon, 11 Nov 2019 at 09:14, Alexandre Rafalovitch wrote: > You still have a mismatch between what you think the schema is > (uniqueKey=title) and message

Re: subquery highlight

Hello, Have you tried to pefix hl.* params with particular subquery name? On Sun, Nov 10, 2019 at 11:46 PM Vasily Ogar wrote: > Hello, > I am using Solr 8.2 and can't find out how to use highlight in the > subquery. Is it possible at all? > Thank you > -- Sincerely yours Mikhail Khludnev

RE: [EXTERNAL] Re: XLSX Response Writer

Wow. This works. Thank you, Jan. -Lewin -Original Message- From: Jan Høydahl Sent: Saturday, November 9, 2019 2:21 PM To: solr-user@lucene.apache.org Subject: Re: [EXTERNAL] Re: XLSX Response Writer It is not the same thing. Instead of adding those lib lines to solr config you should

Re: Solr missing mandatory uniqueKey field: id or Unknown field

You still have a mismatch between what you think the schema is (uniqueKey=title) and message of uniqueKey being id. Focus on that. Try to get schema FROM Solr instead og looking at one you are providing. Or look in Admin UI what it shows for field title and for field id. Regards, Alex On

Re: Solr missing mandatory uniqueKey field: id or Unknown field

https://stackoverflow.com/questions/58763657/solr-missing-mandatory-uniquekey-field-id-or-unknown-field?noredirect=1#comment103816164_58763657 May be this will help ? I added screenshots. On Fri, 8 Nov 2019, 22:57 Alexandre Rafalovitch, wrote: > Something does not make sense, because your

subquery highlight

Hello, I am using Solr 8.2 and can't find out how to use highlight in the subquery. Is it possible at all? Thank you

Re: Solr 7.2.1 - unexpected docvalues type

So “lowercase” is, indeed, a solr.TextField, which is ineligible for docValues. Given that definition, the difference will be that a “string” type is totally un-analyzed, so the values that go into the index and the query itself will be case-sensitive. You’ll have to pre-process both to do the

Re: Mixing query between different parsers

Weird. Did you try echoParams=all just to see what other defaults are picked up. It feels like it picks up default parser and maybe default "df" value that points to not existing text field. Maybe enable debug too to see what it expands to. Regards, Alex On Sun, Nov 10, 2019, 9:26 PM

Mixing query between different parsers

Hi, We are trying to mix the query clause and use different parsers with some syntax we've seen in the community. The idea to re-use all capabilities of the default query parser, and also xmlparser capabilities of position filter (which we asked about it previously and got some guidance from