Use boolean operator "-", the result is incorrect

Hello Folks, We are using Solr 7.3.1, I write the following two lines of data into collection: id, name_s, age_i 1, a, 10 2, b, 10 Use the following query syntax: -name_s:a OR age_i:10 I think we should return two pieces of data, but actually only one piece of data: id, name_s, age_i 2, b, 10

Re: Multiple versions of Solr nodes in the same cloud

On 4/6/2020 11:13 AM, Kudrettin Güleryüz wrote: Can I run let's say, Solr 8.5.0 together with Solr 7.3.1. nodes while replacing older nodes with 8.5.0 one by one? We have a cloud with rather large disk space utilization. What is the suggested way to handle this kind of situation? Building indexe

[Test failure] TestFoldingMultitermExtrasQuery Looks to be a ThreadLeak Branch 8.4.1

So I already found the problem over here https://lucene.472066.n3.nabble.com/mvn-test-failing-td4361042.html -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Spellcheck on specified fields?

Correction. "mark seattle" query doesn't show suggestions since "mark" alone has some hits. It is when the same logic is used for a single term query of "seatle" that 3 suggestions of "seattle" are returned. Do I have to identify the field by using startOffset value? On 4/7/20 3:46 PM, TK Solr

Spellcheck on specified fields?

I query on multiple field like: q=city:(mark seattle) name:(mark seattle) phone:(mark seattle)&spellcheck=true The raw query terms are distributed to all fields because I don't know what term is intended to for which field. If I misspell seattle, I get 3 suggestions: "spellcheck":{     "sugg

Query confusion - solr cloud 8.2.0

I'm running the following query: id:COLLECT2601697594_T496 AND (person:[80 TO 100]) That returns 1 hit. The following query also returns the same hit: id:COLLECT2601697594_T496 AND ((POP16_Rez1:blue_Sky AND POP16_Sc1:[80 TO 100]) OR (POP16_Rez2:blue_Sky AND POP16_Sc2:[80 TO 100]) OR (POP16_Re

Re: If the leader dies, will the data be lost?

bq. Does the replication by tlog always work like this? Yes. Otherwise there’s no way to even attempt to guarantee data integrity. The raw updates _must_ be received by all non-leaders that are eligible (i.e. TLOG or NRT but not PULL replicas). BTW, anecdotally I’ve seen indexing throughput tak

different interpretation of the same query between solr 7.3.1 and solr 8.4.1

Hello all, I noticed that solr8 parses the edismax queries differently from solr7. the querystring and parsedquery in solr 8.4.1 are "querystring":"(_query_:\"{!edismax qf='titles subtitles study_brief_title abstracts abstract_background abstract_objective abstract_methods abstract_results abst