Re: Highlighting the search keywords

Nope, that is how it works. It is not in place. > On 31 Jul 2018, at 21:57, Renuka Srishti wrote: > > Hi All, > > I was using highlighting in solr, solr gives highlighting results within > the response but not included within the documents. > Am i missing something? Can i configure so that it

"dismax" parameter "bq" filters instead of boosting

I noticed a change in the behaviour of the regular "dismax" parser. At least in version 7.4: when you add "bq", it filters the results (like "fq" does), instead of boosting the matches. e.g. defType=dismax bq=format:periodical^30 gives only records with format "periodical". removing the

Re: "dismax" parameter "bq" filters instead of boosting

I agree, but I thought my thread was lost in the long list of issues. I prepared a simple case for solr 8.0: basic_dismax_set/config: schema.xml and solrconfig.xml basic_dismax_set/data: records_pp.json Total 6 records: http://localhost:8983/solr/test/select?echoParams=all

Re: "dismax" parameter "bq" filters instead of boosting

gt; Regards, > Alex > P.s. My suggestion was actually to give the queries against STOCK > examples. That would have made all these parameters explicit and more > obvious. And perhaps would have allowed you to discover the minimum > parameter set causing the issue without all those other

Re: local paramas only with defType=lucene?

Yup Changes in Solr 7.2: local parameters only parsed when defType is either "lucene" or "func" cf. https://lucene.apache.org/solr/guide/7_3/solr-upgrade-notes.html#solr-7-2 cf. https://issues.apache.org/jira/browse/SOLR-11501 On 17 Apr 2019, at 10:35, Michael Aleythe, Sternwald

Re: Urgent help on solr optimisation issue !!

In that case, hard optimisation like that is out the question. Resort to automatic merge policies, specifying a maximum amount of segments. Solr is created with multiple segments in mind. Hard optimisation seems like not worth the problem. The problem is this: the less segments you specify during

Re: Does Solr support retrieve a string text and get its filename accordingly?

In that case you'll have to duplicate that field: id: $name_of_file id_t: $name_of_file The first field should be marked as "string", and set to be the key field. Id-fields cannot be tokenized. The second field is a derivative (you can just copy the contents, or use copyField), and should be

Re: "dismax" parameter "bq" filters instead of boosting

any update on this? > On 5 Mar 2019, at 09:06, Nicolas Franck wrote: > > I noticed a change in the behaviour of the regular "dismax" parser. > At least in version 7.4: > > when you add "bq", it filters the results (like "fq" does), instead of &

Re: Problem while indexing DATE field in SOLR.

Dates need to be send in UTC format: -mm-ddTHH:MM:SSZ or if you want fractional seconds too: -mm-ddTHH:MM:SS.NNNZ See https://lucene.apache.org/solr/guide/6_6/working-with-dates.html#WorkingwithDates-DateFormatting There is no automatic conversion for dates On 26 Apr 2019, at 09:50,

Re: Solr 7.6.0: PingRequestHandler - Changing the default query (*:*)

If the ping request handler is taking too long, and the server is not recovering automatically, there is not much you can do automatically on that server. You have to intervene manually, and restart Solr on that node. First of all: the ping is just an internal check. If it takes too long to

Re: Searches across Cores

He's right. You can use the parameter "shards" for a very long time, even before the whole solr cloud existed. e.g. http://localhost:8983/solr/core0/select with parameters: shards = localhost:8983/solr/core0,example.com:8983/solr/core0 q = *:* defType

use highlighting on multivalued fields with positionIncrementGap 0

I'm trying to use highlighting on a multivalued text field (analysis not so important) .. { text: [ "hello", "world" ], id: 1 } but I want to match across the string boundaries: q=text:"hello world" This works by setting the attribute positionIncrementGap to 0, but then the hightlighting

Re: Lemmatizer for Solr

Try also looking at the HunspellFilter: https://lucene.apache.org/solr/guide/6_6/filter-descriptions.html dictionaries ( .dic and .aff ) can be found here: https://cgit.freedesktop.org/libreoffice/dictionaries or via the git repo:

Re: A question about solr filter cache

If 1GB would make solr go out of memory by using a filter query cache, then it would have already happened during the initial upload of the solr documents. Imagine the amount of memory you need for one billion documents.. A filter cache would be the least of your problems. 1GB is small in

replica's of same shard have different file contents

I noticed a - in my opinion - strange behavior in Solr Cloud. I have a collection that has 1 shard and two replica's. When I look at the directory structure, both have the same file names in "data/index" .. BUT the contents of those files are different. So when I query this collection, and

Re: Should I index the field that use in fq field?

Yes, every field you query has to be "indexed" every field you need to be returned in the response has to be "stored" the parameter "fl" can only return fields that are "stored". Other fields given are simply ignored. > On 13 Mar 2020, at 13:15, GTHell wrote: > > I'm doing a lot of filter

Re: How do *you* restrict access to Solr?

IPtables seems like the way to go, at least for me. Even if this basic-auth-plugin works, then you'll have to deal with denial-of-service attacks (although these can also happen indirectly, by hitting the website that uses Solr). > On 16 Mar 2020, at 15:44, Ryan W wrote: > > How do you,

Re: Questions about Solr Search

Short answer: no Neither Solr nor ElasticSearch have such capabilities out of the box. Solr does have a plugin infrastructure that enables you to provide better tokenization based on language rules, and some are better than others. I saw for example integration of openNLP here:

Re: Limit Solr Disk IO

The real questions are: * how much often do you commit (either explicitly or automatically)? * how much segments do you allow? If you only allow 1 segment, then that whole segment is recreated using the old documents and the updates. And yes, that requires reading the old segment. It is

Re: Getting error "Bad Message 414 reason: URI Too Long"

I believe you can also access this path in a HTTP POST request. That way you do no hit the URI size limit cf. https://stackoverflow.com/questions/2997014/can-you-use-post-to-run-a-query-in-solr-select I think some solr libraries already use this approach (e.g. WebService::Solr in perl) On 14

Re: Getting error "Bad Message 414 reason: URI Too Long"

Euh, sorry: I did not read your message well enough. You did actually use a post request, with the parameters in the body (your example suggests otherwise) > On 14 Jan 2021, at 10:37, Nicolas Franck wrote: > > I believe you can also access this path in a HTTP POST request. > Tha