(echoing Shawn because I was about to hit send anyway):
The process of "uninverting" a field involves running through the
dictionary of indexed terms for a given field, and building an on-heap data
structure that provides "doc => term" lookup (analogous to docValues), as
opposed to "term => doc" l
On 5/19/22 01:13, Vincenzo D'Amore wrote:
As far as I understand, we should always set the property
uninvertible=false to avoid that Solr builds "up large in memory data
structure to serve in place of DocValues" and this is good for "stability",
not explaining exactly what it means.
Could anyone
ping :)
On Thu, May 19, 2022 at 9:13 AM Vincenzo D'Amore wrote:
> Hi All,
>
> recently I've noticed the property "uninvertible". Reading the
> documentation:
>
> > If true, indicates that an indexed="true" docValues="false" field can be
> "un-inverted" at query time to build up large in memory d
Did you try mergeContiguous yet and see if it produced what you wanted?
> On May 20, 2022, at 8:19 AM, Endika Posadas wrote:
>
> Hi all,
>
> I am using Solr's Unified highlighter to highlight parts of a text block.
> However, I have noticed that the highlighter, instead of highlighting the
>
Hi all,
I am using Solr's Unified highlighter to highlight parts of a text block.
However, I have noticed that the highlighter, instead of highlighting the
whole phrase, highlights the words separately.
For example, if we search for "hello world" it will highlight hello
world. Both words are high
Hi Team,
Even after installing java/jre on the machine, solr GC Tuning setting is not
working. We tried to enable it but then our solr service is not getting start.
Can you please provide some resolution on the same and please let us know what
information is needed to investigate this issue fur
On 5/20/22 01:46, Ruchi Gupta wrote:
Even after installing java/jre on the machine, solr GC Tuning setting is not
working. We tried to enable it but then our solr service is not getting start.
Can you please provide some resolution on the same and please let us know what
information is needed
Since Solr 8.x, eDismax parser throw an error when putting a non-existent field
in qf. Previously, qf could be used like “qf= field fallback1 fallback2”. Is it
possible to have fallback fields in qf in case some field does not exist in 8.x
Solr? I have already tried using {!func} and def functio
