RE: requesting help to solve an issue

Hi, That’s not happening the replicas are created even on property value-typeahead Thanks. -Original Message- From: Sandeep Dharembra Sent: Wednesday, April 08, 2020 8:23 PM To: solr-user@lucene.apache.org Subject: Re: requesting help to solve an issue Hi, You have used ! - not operato

Re:Re: Use boolean operator "-", the result is incorrect

Thank you very much for your reply. I have understood the meaning of it. https://lucidworks.com/post/why-not-and-or-and-not/ At 2020-04-09 01:45:14, "Chris Hostetter" wrote: >: Solr/Lucene do not employ boolean logic. See Hossman’s excellent post: >: >: https://lucidworks.com/post/w

Re: ReversedWildcardFilter - should it be applied only at the index time?

I experimented with the index-time only use of ReversedWildcardFilter and the both time use. My result shows using ReverseWildcardFilter both times runs twice as fast but my dataset is not very large (in the order of 10k docs), so I'm not sure if I can make a conclusion. On 4/8/20 2:49 PM, T

Re: match string fields with embedded hyphens

Look at what’s returned when you specify &debug=query. Particularly the parsed query. That’ll show you the results of parsing. My bet: you’ll see something unexpected... Best, Erick > On Apr 8, 2020, at 17:59, Teresa McMains wrote: > > I am still really struggling with this. > > Current fie

RE: match string fields with embedded hyphens

I am still really struggling with this. Current field type as defined in schema.xml: Two fields are defined using this field type: A transaction key may look like: 107986541-85487JY_X4528745 An account number may look like: 1258458-0659841 After making this chang

ReversedWildcardFilter - should it be applied only at the index time?

In the usage example shown in ReversedWildcardFilter in Solr Ref Guide, and only usage find in managed-schema to define text_general_rev, the filter is used only for indexing.   positionIncrementGap="1

Unable to RESTORE collections via Collections API

Hello, I have been unsuccessfully trying to find a way to restore a collection using the Collections API for the last several days. *I would greatly appreciate any help as I am now stuck.* I am using Solr 8.2 in cloud mode. To simplify things, I have only a single Solr node on my local machine (th

Re: Use boolean operator "-", the result is incorrect

: Solr/Lucene do not employ boolean logic. See Hossman’s excellent post: : : https://lucidworks.com/post/why-not-and-or-and-not/ : : Until you internalize this rather subtle difference, you’ll be surprised. A lot ;). : : You can make query parsing look a lot like boolean logic by carefully usin

Re: requesting help to solve an issue

Hi, You have used ! - not operator, so, the replicas would be created on all nodes not having that property value (typeahead) Thanks On Wed, Apr 8, 2020, 4:21 PM saicharan.k...@spglobal.com < saicharan.k...@spglobal.com> wrote: > Hi there, > > We are trying to apply the following collection sp

allTermsRequired not working for me with suggester

Hi folks, I have allTermsRequired=true defined in the suggester component. Despite of this if I run the following query: http://localhost:8983/solr/pocwithedgengram/suggesthandler?allTermsRequired=true&q=*%3A*&suggest.q=Arany%20J%C3%A1nos I get back the following result (it is only a snipet from

Re: Query confusion - solr cloud 8.2.0

The easiest way to answer questions like this is an under-appreciated parameter “explainOther” when submitted with “debug=true”. It’ll return an explanation of how the doc identified by the “explainOther” parameter was scored. See: https://lucene.apache.org/solr/guide/8_1/common-query-parameters

Re: Use boolean operator "-", the result is incorrect

Solr/Lucene do not employ boolean logic. See Hossman’s excellent post: https://lucidworks.com/post/why-not-and-or-and-not/ Until you internalize this rather subtle difference, you’ll be surprised. A lot ;). You can make query parsing look a lot like boolean logic by carefully using parentheses

requesting help to solve an issue

Hi there, We are trying to apply the following collection specific policy in solr { "set-policy": { "generalpolicy": [ { "replica": "<2", "shard": "#EACH", "sysprop.key":"!typeahead", "strict": "true"

Re: Use boolean operator "-", the result is incorrect

About first query, you have a negative query telling the searcher to give only results _NOT_ containing "name_s:a". From that result list you want only results of "age_i:10". Boolean table for OR is: 0 OR 0 = 0 1 OR 0 = 1 0 OR 1 = 1 1 OR 1 = 1 You get one result. About second query your "parsedque

requesting support to solve an issue

Hi there, We are trying to apply the following collection specific policy in solr { "set-policy": { "generalpolicy": [ { "replica": "<2", "shard": "#EACH", "sysprop.key":"!typeahead", "strict": "true"

Re:Re: Use boolean operator "-", the result is incorrect

My default query operator is OR.There are two pieces of data in the index: { "id":"1", "name_s":"a", "age_i":10, "_version_":1663396766955864064}, { "id":"2", "name_s":"b", "age_i":10, "_version_":1663396767058624512}] } 1. -name_s:a OR age_i:10 # I think two pieces of data should b

Re: Use boolean operator "-", the result is incorrect

What is debugQuery telling you about: - "rawquerystring" - "querystring" - "parsedquery" - "parsedquery_toString" - "QParser" Also what is your default query operator, AND or OR? This is what matters for your second example with id:("1" "2") It could be id:("1" AND "2") or id:("1" OR "2") . R

Re:Re: Use boolean operator "-", the result is incorrect

Thanks Bernd for your reply. Can you tell me what your query syntax looks like? At 2020-04-08 16:33:20, "Bernd Fehling" wrote: >Looks correct to me. > >You have to obey the level of the operators and the parenthesis. >Turn debugQuery on to see the results of parsing of your query. > >Re

Re:Re: Use boolean operator "-", the result is incorrect

Thanks Bernd for your reply. I run the query on the Solr Web UI in Solr 7.3.1/7.7.2, the screenshot of my execution results is as follows, I don't understand whether there is a grammatical error ? 1. -name_s:a OR age_i:10 2. id:("1" "2") AND (-name_s:a) At 2020-04-08 16:33:20, "Bernd Fe

Unable to finish sending updates

Hello. Recently we upgraded to SOLR 8.4.1 from 6.4. After the upgrade we started getting errors during our indexing process. We have 3 node solr cloud cluster with main-2 (main-index via alias) collection replicated on each node. We have standalone app running in cycle, it will query our DB to

Re: Use boolean operator "-", the result is incorrect

Looks correct to me. You have to obey the level of the operators and the parenthesis. Turn debugQuery on to see the results of parsing of your query. Regards Bernd Am 08.04.20 um 09:34 schrieb slly: > > > If the following query is executed, the result is different: > > > id:("1" "2") AND (-n

Re:Use boolean operator "-", the result is incorrect

If the following query is executed, the result is different: id:("1" "2") AND (-name_s:a) --> numFound is 0 id:("1" "2") AND -(name_s:a)--> numFound is 1 At 2020-04-08 14:56:26, "slly" wrote: >Hello Folks, >We are using Solr 7.3.1, I write the following two lines of da