Hi Jan,
The same sequence of add/commit commands results in a successful atomic
update in Solr 8.11.2. And I don't see anything in the ref guide (for Solr
8 or 9) that makes me think this shouldn't be possible. So from a user
perspective, I'd argue that this is a bug introduced in Solr 9.0.0. Shou
You are using three features together
A) Nested docs
B) Price field (which is really storing price and currency in two sub fields)
C) Atomic updates
I would not be surprised if these three are not really compatible.
Since there is a requiement to ALWAYS index the entire block of parent and
childr
On 10/27/22 15:51, Thomas Corthals wrote:
I can reproduce it on a pristine techproducts example index by unpacking
the Solr 9.0.0 download and changing the schema in the sample configset
*before* I even start that Solr instance for the very first time. That
should rule out a conflict between the
Op do 27 okt. 2022 om 22:04 schreef Shawn Heisey :
> On 10/19/22 16:41, Thomas Corthals wrote:
> > I'm running into an exception with Solr 9.0.0 for a request that works
> fine
> > with Solr 8.11.2 and I have no idea why.
>
> > However, if I don't do a commit between the two adds, I don't get the
On 10/19/22 16:41, Thomas Corthals wrote:
I'm running into an exception with Solr 9.0.0 for a request that works fine
with Solr 8.11.2 and I have no idea why.
However, if I don't do a commit between the two adds, I don't get the error.
Did something change between Solr 8 and 9 that I have to
Bumping this to the list again in case anyone has any insights before I
open an issue in JIRA for this.
Op do 20 okt. 2022 om 00:41 schreef Thomas Corthals :
> Hi,
>
>
> I'm running into an exception with Solr 9.0.0 for a request that works
> fine with Solr 8.11.2 and I have no idea why.
>
>
> I'
