think there might be an additional issue
> > > here because it happens only when id field contains an underscore
> (didn't
> > > check for other special characters).
> > > Currently I have no other choice but to use
> enableLazyFieldLoading=false.
> > > I
;> with a nested child e.g.
> > >> {id:"abc_1", utterances:{id:"abc_1-1", text_en:"Solr is great"}}
> > >>
> > >> To reproduce:
> > >> Do a search with surround and unified highlighter:
> > >>
> &
age-
> From: David Smiley
> Sent: יום ה 18 פברואר 2021 01:03
> To: solr-user
> Subject: Re: Atomic Update (nested), Unified Highlighter and Lazy Field
> Loading => Invalid Index
>
> I think the issue is this existing bug, but needs to refer to
> toSolrInputDocument i
enableLazyFieldLoading=false. I
hope it wouldn't have a significant performance impact.
-Original Message-
From: David Smiley
Sent: יום ה 18 פברואר 2021 01:03
To: solr-user
Subject: Re: Atomic Update (nested), Unified Highlighter and Lazy Field Loading
=> Invalid Index
I think the is
_i:{add:1}}
>>
>> Important: it happens only when "id" contains underscore characters! If
>> you'll use "abc-1" it would work.
>>
>> Thanks in advance,
>> Ronen.
>>
>> -Original Message-
>> From: David Smiley
>&
rscore characters! If
> you'll use "abc-1" it would work.
>
> Thanks in advance,
> Ronen.
>
> -Original Message-
> From: David Smiley
> Sent: יום א 14 פברואר 2021 19:17
> To: solr-user
> Subject: Re: Atomic Update (nested), Unified Highlighter and Laz
y to update the parent e.g. {id:"abc_1", categories_i:{add:1}}
Important: it happens only when "id" contains underscore characters! If you'll
use "abc-1" it would work.
Thanks in advance,
Ronen.
-Original Message-----
From: David Smiley
Sent: יום א 14 פברואר 2
Hello Ronen,
Can you please file a JIRA issue? Some quick searches did not turn
anything up. It would be super helpful to me if you could list a series of
steps with Solr out-of-the-box in 8.8 including what data to index and
query. Solr already includes the "tech products" sample data; maybe
Hi All,
I discovered a strange behaviour with this combination.
Not only the atomic update fails, the child documents are not properly
indexed, and you can't use highlights on their text fields. Currently there
is no workaround other than reindex.
Checked on 8.3.0, 8.6.1 and 8.8.0.
1. Configure
