Hi all,
Just wish to confirm on the cross DC connection situation from the
CloudSolrClient.
Scenario:
We have multiple DC with the same collection data. Can we add the zookeeper
connect string of the DC's to the cloud SolrClient.
Will it work like this:
The client will utilise this connection stri
Okay confirmed-
I am getting a more predictable results set after adding an additional field:
q=slug:what_is_lo*&fl=slug&rows=1000&wt=csv&sort=slug_alpha%20asc
So it appears I can skip edge ngram entirely using this method as
slug:foo* appears to
You’re getting the correct sorted order… The underscore character is confusing
you.
It’s ascii code for underscore is %2d which sorts before any letter, uppercase
or lowercase.
See the alphaOnlySort type for a way to remove this, although the output there
can also
be confusing.
Best,
Erick
>
Okay. I am getting pretty much a random order of documents containing
the prefix.
Does my "string_ci" defined below count as
"keywordtokenizer+lowecasefilter"? (assumption)
Does my "fayt" copy field below look right? (assumption)
I have a bunch of web pages indexed with "slug" fields with the p
What _is_ happening? Please provide examples of the inputs
and outputs that don’t work for you. ‘cause
the sort order should be “nothing comes before something"
so sorting ascending on a keywordtokenizer+lowecasefilter
should give you exactly what you’re asking for with no
need for a length field.
Hi everyone,
I'm currently testing with Solr Standalone 8.1.1.
I have the following need: through the API Solr standalone create an
empty core and then use the schema API to add what I need. Similar to
create a sql database and then create tables (except that I need only
one table in my case) and
For both Solr 7 and Solr 8, we have found that attempts to do range queries on
DatePointField when there are a large number of points performs poorly (queries
were taking over 30 seconds on a 50G core). We also tried switching to
IntPointField to see if it made a difference and it didn't. Just f
My original goal was to avoid indexing the string length because I
wanted edge ngram to "score" based on how "exact" the match was:
q=abc
"abc" has a high score
"abcd" has a lower score
"abcde" has an even lower score
You say sorting by by the original field will do that but in practice
it is not
Why do you want to deal with score at all? Sorting
overrides score-based sorting. Well, unless you
specify score as a secondary sort. But since you’re
sorting by length anyway, trying to score
based on proximity to the end does nothing.
The weirdness you’re going to get here, though, is
that the
Where I landed:
---
I can then do a search for
q=fayt:my_article_slu&sort=qt_len asc
to get the shortest/most exact find-as-you-type match. I couldn't get
around all results having the same score (can I boost pr
Hi,
I knew I could get that information by using the "debug" query parameter,
but I want to use it in "production".
If I want to use it in "production", I have to write a plugin?
2020年3月25日(水) 9:03 Yasufumi Mizoguchi :
> Hi,
>
> I think "debug" query parameter or "explain" document transformer
Try splainer.io - it parses the Debug output to show in detail how the
scores are calculated (disclaimer, I work for OSC who created it - but
it's free & open source of course ).
Charlie
On 23/03/2020 01:26, Taisuke Miyazaki wrote:
The blog looks like it's going to be useful from now on, so I
12 matches
Mail list logo
