Re: $deleteDocByQuery is not working for me

Hi, I am able to get it done using following way - Thanks, Paresh -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: $deleteDocByQuery and $deleteDocByID

Hi, I am able to get it done using following way - Thanks, Paresh -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: $deleteDocByQuery and $deleteDocByID

Hi, I am able to get it done using following way - Thanks, Paresh -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

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

What I can't understand is: I search for the exact term - "Immunoregulatory interactions between a Lymphoid and a non-Lymphoid cell" and If i search "I search for the exact term - Immunoregulatory interactions between a Lymphoid and non-Lymphoid cell" then it works > On 11 Nov 2019, at 12:24,

Re: sort by score in join with geodist()

Hello, It seems like I breached the limit on unconscious replies in mailing list I'd rather start with this: q={!join from=site_id to=site_id fromIndex=stores score=max}+{!geofilt} {!func}geodist()&sfield=coordinates&pt=54.6973867999,25.22481530046&d=10 On Mon, Nov 11, 2019 at 11:11 PM

Re: Does Solr replicate data securely

Hi, How about in the master/slave set up. If I enable ssl in master/slave setup would the segment and config files be copied using TLS. On Sat, Nov 9, 2019 at 3:31 PM Jan Høydahl wrote: > You choose. If you use solr cloud and have enabled ssl in your cluster, > then all requests including replic

Re: different results in numFound vs using the cursor

On Mon, Nov 11, 2019 at 8:32 PM Chris Hostetter wrote: > > Based on the info provided, it's hard to be certain, but reading between > the lines here are hte assumptions i'm making... > > 1) your core name is "dbtr" > 2) the uniqueId field for the "dbtr" core is "debtor_id" > > ..are those assumpt

Re: sort by score in join with geodist()

First of all, thank you for your help. Now it doesn't show any errors, but somehow score is based on the title and description but not on the geodist. "params":{ "hl":"on", "pt":"54.6973867999,25.22481530046", "fl":"score,*,store:[subquery fromIndex=stores]", "store.rows":"1", "fq":"{!join

Re: sort by score in join with geodist()

tlrd; I noticed func under fq that make no sense. Only q or sort yield scores. On Tue, Nov 12, 2019 at 6:43 PM Vasily Ogar wrote: > First of all, thank you for your help. > Now it doesn't show any errors, but somehow score is based on the title and > description but not on the geodist. > "params

using fq means no results

If I do this query in the browser: http://10.40.10.14:8983/solr/debt/select?q=(clt_ref_no:+owl-2924-8)^=1.0+clt_ref_no:owl-2924-8 I get 84662 results. If I do this query: http://10.40.10.14:8983/solr/debt/select?q=(clt_ref_no:+owl-2924-8)^=1.0+clt_ref_no:owl-2924-8&fq=clt_ref_no I get 0 result

Re: sort by score in join with geodist()

Thank you for advice, now it working as expected. Maybe you know how to integrate with dismax? On Tue, Nov 12, 2019 at 6:10 PM Mikhail Khludnev wrote: > tlrd; > I noticed func under fq that make no sense. Only q or sort yield scores. > > On Tue, Nov 12, 2019 at 6:43 PM Vasily Ogar wrote: > > >

Re: using fq means no results

fq is a filter query, and thus narrows the result set provided by the q down to what also matches all specified fq's. You gave it a query, "cat_ref_no", which literally looks for that string in your default field. Looking at your q parameter, cat_ref_no looks like a field name, and your fq sh

Re: using fq means no results

On Tue, Nov 12, 2019 at 11:57 AM Erik Hatcher wrote: > fq is a filter query, and thus narrows the result set provided by the q > down to what also matches all specified fq's. > > So this can be used instead of scoring? Or alongside scoring? > You gave it a query, "cat_ref_no", which literally l

Re: using fq means no results

> On Nov 12, 2019, at 12:01 PM, rhys J wrote: > > On Tue, Nov 12, 2019 at 11:57 AM Erik Hatcher > wrote: > >> fq is a filter query, and thus narrows the result set provided by the q >> down to what also matches all specified fq's. >> >> > So this can be used instead of scoring? Or alongsid

Re: using fq means no results

I explain it this way: * fq: filtering * q: filtering and scoring * bq: scoring wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Nov 12, 2019, at 9:08 AM, Erik Hatcher wrote: > > > >> On Nov 12, 2019, at 12:01 PM, rhys J wrote: >> >> On Tue, Nov

Re: different results in numFound vs using the cursor

: > a) What is the fieldType of the uniqueKey field in use? : > : : It is a textField whoa... that's not normal .. what *exactly* does the fieldType declaration (with all analyzers) look like, and what does the declaration look like? you should really never use TextField for a uniqueKey ...

Re: different results in numFound vs using the cursor

On Tue, Nov 12, 2019 at 12:18 PM Chris Hostetter wrote: > > : > a) What is the fieldType of the uniqueKey field in use? > : > > : > : It is a textField > > whoa... that's not normal .. what *exactly* does the fieldType declaration > (with all analyzers) look like, and what does the declaration >

Re: different results in numFound vs using the cursor

: > whoa... that's not normal .. what *exactly* does the fieldType declaration : > (with all analyzers) look like, and what does the declaration : > look like? : > : > : : : NOTE: "text_general" != "text_gen_sort" Assuming your "text_general" declaration looks like it does in the _default

Re: using fq means no results

To add bq in there makes it query parser specific. But I’m being pedantic since most folks are using edismax where that applies (along with a bunch of other params that would also deserve mention, like boost and bf). q and fq, agreed for the explanation. bq mentioned only if specifics and sib

Re: different results in numFound vs using the cursor

> : I am going to adjust my schema, re-index, and try again. See if that > : doesn't fix this problem. I didn't know that having the uniqueKey be a > : textField was a bad idea. > > > https://lucene.apache.org/solr/guide/8_3/other-schema-elements.html#OtherSchemaElements-UniqueKey > > "The fieldTyp

Solr 8.2 indexing issues

We recently migrated from 6.6.2 to 8.2. We are seeing issues with indexing where the leader and the replica document counts do not match. We get different results every time we do a *:* search. The only issue we see in the logs is Jira issue : Solr-13293 Has anybody seen similar issues? Thanks

Re: Full-text search for Solr manual

Thanks Alex, For your response. Unfortunately the Solr source does not ship with the source of the manual. (Directory /docs only contains a link to the online manual.) Google search with domain limitation does not give any results, as mentioned in my initial post. Any other limitation