Index size issue. Migration from Solr-6.5.1 To Solr-8.6.3

Hi, I am in a process of migrating from Solr-6.5.1 To Solr-8.6.3. The current index size after optimisation is 2.4 TB. We use a 7TB disk for indexing as the optimization needs extra space. Now with the newer Solr the un-optimised index itself got created of size 5+TB which after optimisation reduc

Re: _version_ taking too much memory

You should change the _version_ field to be of type docValues and re-index data. This way you don't have to pay the memory cost of un-inversion. On Wed, Nov 18, 2020 at 9:51 AM sanjay dutt wrote: > Solr Collection setup > Shards :- 2Replication :- 4Documents :- 569 Million (I know it's too > muc

_version_ taking too much memory

Solr Collection setup Shards :- 2Replication :- 4Documents :- 569 Million (I know it's too much)Heap Space :- 12GB So basically, above collection is having OutOfMemory issues. And upon inspection, I got to know that  org.apache.lucene.uninverting.FieldCacheImpl$LongsFromArray for field "_version

Re: Faceting: !terms vs mincount precedence

Thanks for the context David - I didn't realize this was built as an internal mechanism and then documented later on. A few other thoughts below: > {!terms}, it suggests a reference to the TermsQParser, but when you write > {!terms=a,b,c} it suggests local-params I agree that the two are easy to

Re: Faceting: !terms vs mincount precedence

This is confusing because when you write {!terms}, it suggests a reference to the TermsQParser, but when you write {!terms=a,b,c} it suggests local-params, with key "terms" and value "a,b,c" -- entirely different things. I think that "terms" local-param to faceting was a purely internal thing that

Re: Multiple Facets on Same Field

Ah, ok! The Jira issue mentioned in the mail thread you cited above has some further discussion/detail. (I don't think adding a "{!terms}" query filter would necessarily work ... it'd need to be a group of facets of type "query", sorted client-side ... unless I'm missing something?) https://issues.

Re: Multiple Facets on Same Field

Thanks Michael, I agree - JSON Facets is a better candidate for the functionality I'm looking for. In my case specifically though, I think I'm pegged to traditional facets because I also want to use the "terms" local params support that doesn't have a native equivalent in JSON Faceting (yet: SOLR

Re: Multiple Facets on Same Field

Answering a slightly different question perhaps, but you can definitely do this with the "JSON Facet" API, where there's much cleaner separation between different facets (and output is assigned to arbitrary keys). Michael On Tue, Nov 17, 2020 at 9:36 AM Jason Gerlowski wrote: > > Hi all, > > Is i

Multiple Facets on Same Field

Hi all, Is it possible to have multiple facets on the same field with different parameters (mincount, limit, prefix, etc.) on each? The ref-guide describes these per-facet parameters as being settable on a "per-field basis" with syntax of "f..facet." [1]. But I wasn't sure whether to take that a

Faceting: !terms vs mincount precedence

Hey all, I was using the {!terms} local parameter on some traditional field facets to make sure particular values were returned. e.g. facet=true&facet.field={!terms='fantasy,scifi,mystery'}genre_s&f.genre_s.facet.mincount=2 On single-shard collections in 8.6.3 this worked as I expected - "fanta

SOLR fuzzy search not behaving as expected when analysers are used

Hello everyone, I am using the fuzzy search capability of SOLR 8.7 and I dug into a specific case in which the search misbehaves. I am using this analyzer (JSON here) on the field that I am using for search "analyzer" : { "filters":[ { "cl