RE: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

http://www.linkedin.com/in/davidwsmiley > > > On Wed, Feb 17, 2021 at 6:36 AM Nussbaum, Ronen > > wrote: > >> Hello David, >> >> Thank you for your reply. >> It was very hard but finally I discovered how to reproduce it. I >> thought of issuing an i

RE: Atomic Update (nested), Unified Highlighter and Lazy Field Loading => Invalid Index

Hello David, Thank you for your reply. It was very hard but finally I discovered how to reproduce it. I thought of issuing an issue but wasn't sure about the components and priority. I used the "tech products" configset, with the following changes: 1. Added 2. Added Than I inserted one

RE: Ghost Documents or Shards out of Sync

Hi, Thank you your replies - much appreciated! I'm afraid it's neither one... Let me add some background. A user triggers an operation which under the hood needs to update a single field. Atomic update fails with a message that one of the mandatory fields is missing (which is strange by

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". The client retrieves documents,

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

Generate Missing Segments Files

Hi, Due to https://issues.apache.org/jira/browse/SOLR-11191 we tried to recover the index from backup. Apparently, all eight shards backups don't contain the segment file. Is there a way to generate it? Thanks, Ronen. This electronic message may contain proprietary and confidential

SPLITSHARD - data loss of child documents

Hi Everyone, We're using version 8.6.1 with nested documents. I used the SPLITSHARD API and after it finished successfully, I've noticed the following: 1. Most of child documents are missing - before the split: ~600M, after: 68M 2. Retrieving a document with its children, shows child

Non Deterministic Results from /admin/luke

Hi All, We are using the Luke API in order to get all dynamic field names from our collection: /solr/collection/admin/luke?wt=csv=0 This worked fine in 6.2.1 but it's non deterministic anymore (8.6.1) - looks like it queries a random single shard. I've tried using

Query Containing Multiple Parsers

Hello All, We have an application that translates user queries to Solr syntax (Lucene query parser) by using ANTLR. Lately, we wanted to add support for the user to search term(s) that appear in the beginning of the text. >From answers to similar questions, I understood that SpanFirst might be

Can't Find Phrases

Hello, I've installed Solr 7.6.0 with the following field definition: My stopwords_en.txt contains (among others) the words: it, will (synonyms