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
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,
&g
20-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.
>
>Regards
>Bernd
>
>Am 08.04.20 um 09:34 schrieb slly:
>>
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 (-name_s:a) --> numFound is 0
>>
quot;, "QParser":"LuceneQParser",
At 2020-04-08 17:46:37, "Bernd Fehling" wrote:
>What is debugQuery telling you about:
>- "rawquerystring"
>- "querystring"
>- "parsedquery"
>- "parsedquery_toString"
>- &qu
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
Hello everyone,
I want to migrate data from one collection to another with MIGRATE API, but if
this parameter split.key is not specified, it cannot be executed.
Why can't we remove this limitation? Is there a better way to migrate data?
Thanks.
Hello everyone, I use the version of Solr-7.7.3.
The following error occurred during the index write phase, but after restarting
the Solr service, the file was deleted, and access to the index has also been
restored.
Has anyone ever encountered this mistake?
Caused by: org.apache.lucene.
Hello everyone.
I'm a little confused: replayUpdatesExecutor, only one thread is always
running?
OrderedExecutor limits the cfg.getReplayUpdatesThreads() number of tasks to be
submitted, and the newMDCAwareCachedThreadPool thread queue are up to
cfg.getReplayUpdatesThreads() queues, the thre
