Hi, On 2021/03/30 14:59:40, Shawn Heisey <a...@elyograg.org> wrote:
On 3/30/2021 4:07 AM, Daniel Exner wrote:When updating some different field, like say "stock" for a document using partial Update, *all* enum Fields with stored=false vanish from the document.There is no error or Warning about this somewhere in Error log.If you have fields that are not stored, and do not have docValues with the flag to use docValues as stored, you will lose those fields when you do an atomic update. No error is logged when this happens because the behavior isn't an error. It's inherent to the way that the Atomic Update feature works.The documentation states this requirement pretty clearly, though it doesn't mention the need for useDocValuesAsStored.
This is known and the fields in question all have the attribute docValues=true.
I might have not stated clearly: the exact same mechanism works flawlessly with Solr 8.2.
From reading the documentation useDocValuesAsStored is a query parameter to change the behaviour of ommitting the fl parameter or setting it to * for not stored fields and got nothing todo whether those fields are actually in the document or not.
https://solr.apache.org/guide/8_8/updating-parts-of-documents.html#field-storageCan you share your full schema? You will need to either paste the whole thing into the email text or put it on an info-sharing site and give us
a link to it. If you try attaching a file to an email, the mailing list will most likely remove the attachment before any of us receive the email.
Sure. I uploaded the schema to: https://pastebin.com/v6NwWnkx The enumsConfig.xml is here: https://pastebin.com/RZw1xPN6 Testcase we used so far: * fill Index * read mxlang field for some id * try in place update for "oxvarstock" Field for that id * try rereading mxlang field --> nothingHope someone can make up some sense of that. If not I'm going to open up a bug report.
Greetings Daniel Exner
OpenPGP_signature
Description: OpenPGP digital signature
