Hello,
Say, I have a schema field which is multivalued. Is there a way to maintain
distinct values for that field though I continue to add duplicate values
through atomic update via solrj?
Is there some property setting to have only unique values in a multi valued
fields?
Thanks,
Srinivas
Separately, and in parallel to Erick's question: indeed I'm not aware
of any way to do this currently, but I *can* imagine cases where this
would be useful. I have a sense this could be cleanly implemented as a
stat facet function
Hi,
after reading some Solr source code, I might have found the cause:
There was indeed a change in Solr 8.6 that leads to the NullPointerException
for the CoreAdmin STATUS request in CoreAdminOperation#getCoreStatus. The
instancePath is not retrieved from the ResourceLoader anymore, but from
Hello,
We are using below suggest component in our solr implementation.
analyzinginfixsuggester
analyzinginfixlookupfactory
DocValues=true are usually only used for “primitive” types, string, numerics,
booleans and the like, specifically _not_ text-based.
I say “usually” because there’s a special “SortableTextField” where it does
make some sense to have a text-based field have docValues, but that’s intended
for
Double the heap.
All that CPU is the GC trying to free up space.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Oct 28, 2020, at 6:29 AM, Jaan Arjasepp wrote:
>
> Hi all,
>
> Its me again. Anyway, I did a little research and we tried different
Chegg is running a 4.10.2 master/slave cluster for textbook search and several
other collections.
1. None of the features past 4.x are needed.
2. We depend on the extended edismax (SOLR-629).
3. Ain’t broke.
We are moving our Solr Cloud clusters to 8.x, even though there are no
features we need
Hi all,
Its me again. Anyway, I did a little research and we tried different things and
well, some questions I want to ask and some things that I found.
Well after monitoring my system with VirtualVM, I found that GC jumping is from
0.5GB to 2.5GB and it has 4GB of memory for now, so it should
This really sounds like an XY problem. The whole point of facets is
to count the number of documents that have a value in some
number of buckets. So trying to stop your facet query as soon
as it matches a hit for the first time seems like an odd thing to do.
So what’s the “X”? In other words,
On Tue, Oct 27, 2020 at 04:25:54PM -0500, Mike Drob wrote:
> Based on the questions that we've seen over the past month on this list,
> there are still users with Solr on 6, 7, and 8. I suspect there are still
> Solr 5 users out there too, although they don't appear to be asking for
> help -
Hi,
I use json facets of type 'query'. As these queries are pretty slow and I'm
only interested in whether there is a match or not, I'd like to restrict
the query execution similar to the standard facetting (like with the
facet.exists parameter). My simplified query looks something like this (in
11 matches
Mail list logo
