Atomic Update Failures with Nested Schema and Lazy Field Loading
Hi, I’ve encountered another issue that might be related to nested schema. Not always, but many times atomic updates fails for some shards with the message “TransactionLog doesn't know how to serialize class org.apache.lucene.document.LazyDocument$LazyField”. I checked both options: 1. Set false. 2. Set true but removed child documents. In both cases atomic update worked without any errors. This might suggest that there is an issue with this combination. Thanks in advance, Ronen.
Ghost Documents or Shards out of Sync
Hi All, I'm using Solr Cloud (version 8.3.0) with shards and replicas (replication factor of 2). Recently, I've encountered several times that running the same query repeatedly yields different results. Restarting the nodes fixes the problem (until next time). I assume that some shards are not synchronized and I have several questions: 1. What can cause this - many atomic updates? issues with commits? 2. Can I trigger the "fixing" mechanism that Solr runs at restart by an API call or some other method? Thanks in advance, Ronen.
Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index
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 nested schema. 2. enableLazyFieldLoading is true (default). 3. Run a search with hl.method=unified and hl.fl= 4. Trying to do an atomic update on some of the *parents* of the returned documents from #3. You get an error: "TransactionLog doesn't know how to serialize class org.apache.lucene.document.LazyDocument$LazyField". Now trying to run #3 again yields an error message that the text field is indexed without positions. If enableLazyFieldLoading is false or if using the default highlighter this doesn't happen. Ronen.
