I like this one (never released) https://issues.apache.org/jira/browse/LUCENE-3575
the basics are that fields in lucene have numbers, but if code mixes these up (e.g. in an optimization), then data can "move" to different field. Maybe there were other real corruption bugs along the same lines with bulk merge. On Wed, Nov 25, 2015 at 9:08 AM, Eslam Elnikety <eslam.elnik...@gmail.com> wrote: > Hi everyone, > > This is a question about your experience with bugs that silently make the > application produce wrong results. > > I am developing a tool that prevents search engines from leaking sensitive > information when they start misbehaving due to bugs/misconfigurations. I am > trying to get better understanding of these bugs. If you recall bugs (e.g., > wrong/corrupt index, incorrect query parsing, ..) that result in wrong > results or another strange silent behavior, it will be great if you share > them with me. This will be extremely helpful. > > Here is an example of the kind of bugs I am looking for: > https://issues.apache.org/jira/browse/LUCENE-2756 > > Thanks! > > -- Eslam --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
