I've got a problem with a query running against Lucene 7.3 where the
boolean AND is not being applied.
The fields involved are:
1. _missing_, which contains a token for each field missing in the document
2. phoneNationalNumberQueryNgrams, which contains a phone number. The index
analyzer is keywo
egment (e.g. because files got
> mixed up), there's a clear error this way that files are mixed up.
> otherwise, without this check, you get pure insanity trying to debug
> problems when files get mixed up.
>
> On Wed, Apr 13, 2022 at 10:39 PM Tim Whittington wrote:
> >
> &
a great point to look at first and that would eliminate any
> jdbc related issues that may lead to such problems.
> Best regards
> ____
> From: Tim Whittington
> Sent: Wednesday, April 13, 2022 9:17:44 PM
> To: java-user@lucene.apache.org
> Subje
Thanks for this - I'll have a look at the database server code that is
managing the Lucene indexes and see if I can track it down.
Tim
On Thu, 14 Apr 2022 at 12:41, Robert Muir wrote:
> On Wed, Apr 13, 2022 at 8:24 PM Tim Whittington
> wrote:
> >
> > I'm working wi
tj Lucene.
>
> Can you maybe recreate lucene index on 7.3.0?
>
> Also how do you use database in your scenario?
> Are you using jdbc like operations like in Oracle database? lucene
> operations are independent of database operations.
>
> Best regards
> ________
I'm working with/on a database system that uses Lucene for full text
indexes (currently using 7.3.0).
We're encountering occasional problems that occur after unclean shutdowns
of the database , resulting in
"org.apache.lucene.index.CorruptIndexException: file mismatch" errors when
the IndexWriter i
