Thanks, this is what I was looking for. Although, when I am experimenting with them now, I see no performance improvement. I suspect that it is still doing atomic updates and not in-place updates. How do I confirm whether in-place updates are happening vs atomic updates? I can't tell it simply by looking at the update values for the document because the behavior will be the same in both cases.
On Wed, Mar 30, 2022 at 12:37 PM Walter Underwood <wun...@wunderwood.org> wrote: > Integer view counts probably do meet those requirements, but you might > need to update all 25 million documents every day, which is not going to be > fast. > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > > > On Mar 30, 2022, at 9:34 AM, Shawn Heisey <apa...@elyograg.org> wrote: > > > > On 3/30/22 10:27, gnandre wrote: > >> IIRC, under the hood, atomic indexing indexes the whole document again > even > >> if you might be updating just one field of that document. This costs > hugely > >> in terms of indexing performance because the other fields might be > >> requiring some significant heavy tokenization. Is there any way around > this? > > > > > > If you need to be able to query on any of the fields you're modifying in > the atomic update, then there is no way to do it without reindexing the > whole document. > > > > There is a feature that can do an in-place update, but the field has to > be not indexed, not stored, single valued, and have docValues enabled. A > field using the TextField class cannot have docValues. It is probably > unlikely that the fields you want to update meet these requirements. > > > > > https://solr.apache.org/guide/8_11/updating-parts-of-documents.html#in-place-updates > > > > Thanks, > > Shawn > > > >
