Had 2 indexes in 2 separate shards in one collection and had exact same
data published with composite router with a prefix. Disabled all caches.
Issued the same query which is a small query with q parameter and fq
parameter . Number of queries which got executed (with same threads and
run for
What did you test? Which queries? What were the exact results in terms of time ?
> Am 30.06.2020 um 22:47 schrieb Raji N :
>
> Hi ,
>
>
> Trying to place multiple smaller indexes in one collection (as we read
> solrcloud performance degrades as number of collections increase). We are
>
Hi ,
Trying to place multiple smaller indexes in one collection (as we read
solrcloud performance degrades as number of collections increase). We are
exploring two ways
1) Placing each index on a single shard of a collection
In this case placing documents for a single index is manual and
Thank you Walter, I'll look into “mm” (minimum match) parameter.
Best Regards,
Vadim Permakoff
-Original Message-
From: Walter Underwood
Sent: Tuesday, June 30, 2020 2:31 PM
To: solr-user@lucene.apache.org
Subject: Re: Query in quotes cannot find results
This is exactly why the “mm”
This is exactly why the “mm” (minimum match) parameter exists, to reduce the
number of hits with fewer matches. Think of it as a sliding scale between OR
and AND.
On the other hand, I don’t usually worry about hits with fewer matches. Those
are not on the first page, so I don’t care.
In
Hi Walter,
I'm with you, sometimes the stopwords are very important, I did a few years
back just for fun the Solr demo for Wikipedia search, you can see - nothing is
removed:
http://www.softcorporation.com/lab/solr/wiki/?sq=to+be+or+not+to+be
But with the enterprise search, sometimes you will
Hi Erick,
Thank you for the suggestion, I should of add it. Actually before asking this
question here, I tried to add and remove the FlattenGraphFilterFactory, plus
other variations, like expand / not expand, autoGeneratePhraseQueries / not
autoGeneratePhraseQueries - it just does not work with
Hi,
Maybe https://github.com/sematext/solr-diagnostics can be of use?
Otis
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
On Mon, Jun 29, 2020 at 3:46 PM Erick Erickson
wrote:
> Really look at your cache
Removing stopwords is a dumb requirement. “Doctor, it hurts when I shove
hedgehogs up my arse.”
Part of our job as search engineers is to solve the real problem, not implement
a pile of requirements from people who don’t understand how search works.
Here is an article I wrote 13 years ago
Well, the first thing is that you haven’t include FlattenGraphFilterFactory in
the index analysis chain, see:
https://lucene.apache.org/solr/guide/7_5/filter-descriptions.html#synonym-graph-filter.
IDK whether that actually pertains, but I’d reindex with that included before
pursuing.
Second,
Hi Erik,
That's what I did in the past, but this is an enterprise search and I have a
requirement to remove the stopwords.
To have both features I can add synonyms in the front-end application, I know
it will work, but I need a justification why I have to do it in the application
as it is an
Yes, The config is there and it works for me in live environment but not
the new staging environment.
On Tue, Jun 30, 2020 at 2:29 PM Erick Erickson
wrote:
> Did you put your auxiliary files in the
> confFiles tag? E.g. from the page you referenced:
>
> schema.xml,stopwords.txt,elevate.xml
>
>
Use nodes=, not node=
> 30. jun. 2020 kl. 02:02 skrev ChienHuaWang :
>
> Hi Jan,
>
> Thanks for the response.
> Could you please share more detail how you request the metric with multiple
> nodes same time?
> I do something as below, but only get one node info, the data I'm interested
> most
Did you put your auxiliary files in the
confFiles tag? E.g. from the page you referenced:
schema.xml,stopwords.txt,elevate.xml
Best,
Erick
> On Jun 30, 2020, at 5:38 AM, Atita Arora wrote:
>
> Hi,
>
> We are using Solr 6.6.2 in the Master-Slave mode ( hot star of the
> discussion thread
That’s not quite the question I was asking.
Let’s take "…that don’t contain the characters ‘paid’ “.
Start with the fact that no matter what the mechanics of
implementing pre-and-post wildcards, something like
*:* -tags:*paid*
would exclude a doc with a tag of "credit-ms-reply-unpaid" or
@Mikhail
Thanks for the link! I'll read through that.
On Tue, Jun 30, 2020 at 6:28 AM Chris Dempsey wrote:
> @Erick,
>
> You've got the idea. Basically the users can attach zero or more tags (*that
> they create*) to a document. So as an example say they've created the
> tags (this example is
@Erick,
You've got the idea. Basically the users can attach zero or more tags (*that
they create*) to a document. So as an example say they've created the tags
(this example is just a small subset of the total tags):
- paid
- invoice-paid
- ms-reply-unpaid-2019
-
Hi Jan,
Thanks for the response.
Could you please share more detail how you request the metric with multiple
nodes same time?
I do something as below, but only get one node info, the data I'm interested
most is, ex: CONTAINER.fs.totalSpace, CONTAINER.fs.usableSpace. etc..
Hi,
We are using Solr 6.6.2 in the Master-Slave mode ( hot star of the
discussion thread these days !!) and lately, I got into this weird issue
that at each replication trigger my index gets correctly replicated but my
config changes are not replicated to my slaves.
We are using referential
Hi, Dawn.
It might make sense. Feel free to raise a jira, and "patches are welcome!".
On Tue, Jun 30, 2020 at 10:33 AM Dawn wrote:
> Hi:
>
> When using the LTR, open timeAllowed parameter, LTR feature of query may
> call ExitableFilterAtomicReader. CheckAndThrow timeout detection.
>
> If a
Hi:
When using the LTR, open timeAllowed parameter, LTR feature of query may call
ExitableFilterAtomicReader. CheckAndThrow timeout detection.
If a timeout occurs at this point, the exception ExitingReaderException is
thrown, resulting in a no-result return.
Is it possible to accommodate this
21 matches
Mail list logo
