Hi Jayadevan,
There are a couple of ways to achieve the result you want! Two things you could
do from the top of my head are: You could sort the results based on some field,
or boost some fields so that they get a higher score.
> On 17 Oct 2020, at 05:51, Jayadevan Maymala wrote:
>
> Hi all,
Hi,
A few strategies you can use:
1. First you need to know why the result has matched. Solr provides
detailed debug info but it's not easy to interpret. Consider using
something like www.splainer.io to give you better visibility
(disclaimer: this is something we maintain, there are other
Hi Shawn,
Thank you for your response.
You are confirming my diagnosis.
This is in fact a 8 nodes cluster with one single collection with 4 shards
and 1 replica (8 cores).
4 Gb heap and 90 Gb Ram
When no issue occurs nearly 50% of the heap is used.
Num Docs in collection : 10.000.000
Num
Shawn,
According to the log4j description (
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714), the issue is related
to lock during appenders collection process.
In addition to CONSOLE and file appenders in the default log4j.properties,
my customer added 2 extra FileAppender dedicated to all
I think this is all explained quite well in the Ref Guide:
https://lucene.apache.org/solr/guide/8_6/docvalues.html
DocValues is a different way to index/store values. Faceting is a
primary use case where docValues are better than what 'indexed=true'
gives you.
Regards,
Alex.
On Mon, 19 Oct
uyilmaz:
Hmm, that _is_ confusing. And inaccurate.
In this context, it should read something like
The Text field should have indexed="true" docValues=“false" if used for
searching
but not faceting and the String field should have indexed="false"
docValues=“true"
if used for faceting but not
Sorry, correction, taking "the" time
On Mon, 19 Oct 2020 22:18:30 +0300
uyilmaz wrote:
> Thanks for taking time to write a detailed answer.
>
> We use Solr to both store our data and to perform aggregations, using
> faceting or streaming expressions. When required analysis is too complex to
Hmm. Fields used for faceting will also be used for filtering, which is a kind
of search. Are docValues OK for filtering? I expect they might be slow the
first time, then cached.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Oct 19, 2020, at 11:15
Thanks for taking time to write a detailed answer.
We use Solr to both store our data and to perform aggregations, using faceting
or streaming expressions. When required analysis is too complex to do in Solr,
we export large query results from Solr to a more capable analysis tool.
So I guess
As you've observed, it is indeed possible to facet on fields with
docValues=true, indexed=false; but in almost all cases you should
probably set indexed=true. 1. for distributed facet count refinement,
the "indexed" approach is used to look up counts by value; 2. assuming
you're wanting to do
Hey all,
>From my little experiments, I see that (if I didn't make a stupid mistake) we
>can facet on fields marked as both indexed and stored being false:
I'm suprised by this, I thought I would need to index it. Can you confirm this?
Regards
--
uyilmaz
Thanks! This also contributed to my confusion:
https://lucene.apache.org/solr/guide/8_4/faceting.html#field-value-faceting-parameters
"If you want Solr to perform both analysis (for searching) and faceting on the
full literal strings, use the copyField directive in your Schema to create two
Hey, I'm new to configuring Solr. I'm trying to configure Solr with Rule Based
Authorization.
https://lucene.apache.org/solr/guide/8_6/rule-based-authorization-plugin.html
I have permissions working if I allow everything with "all", but I want to
limit access so that a site can only access its
Can someone help on the above pls??
On Sat, Oct 17, 2020 at 6:22 AM yaswanth kumar
wrote:
> Using Solr 8.2; Zoo 3.4; Solr mode: Cloud with multiple collections; Basic
> Authentication: Enabled
>
> I am trying to run the
>
> export JAVA_OPTS="-Djavax.net.ssl.trustStore=etc/solr-keystore.jks
>
Hi,
Suppose I have say 50 ElevateIds and I have a way to identify those that
would get filtered out in the query by predefined fqs. So they would in
reality never be even in the results and hence never be elevated.
Is there any advantage if I avoid passing them in the elevateIds at the
time of
Hi all,
Hopefully someone can provide insight.
We are looking to see if there are any viable options for S3 or similar
for index/data storage.
Preferably (if possible) shared between nodes for dynamic scalability needs.
-Mike/NewsRx
16 matches
Mail list logo