JabRef version
5.5 (latest release)
Operating system
Windows
Details on version and operating system
Windows 10 21H2
Checked with the latest development build
Steps to reproduce the behaviour
When using the fulltext search with a simple single-keyword query, e.g. test, I only get partial results and a subset of expected entries containing the text test is not displayed in the search results. When I open the JabRef's Lucene index in Luke and execute the same query (content:test), it returns all related entries including those that are missing in JabRef's search results.
The library in which I experience this has 400 entries. When I create a new library and add only one of the missing entries, the fulltext search returns it as expected. When I delete large portions (e.g. 350 entries) from my 400-entry library, that missing search result also starts to appear - this does not seem related to deleting a specific (potentially problematic) entry, as it starts to appear after different random selections of entries are removed. There's also no specific threshold library size that triggers this behavior - I was able to make the result appear after cutting the library randomly down to ~40 - 70 entries.
Appendix
No response
JabRef version
5.5 (latest release)
Operating system
Windows
Details on version and operating system
Windows 10 21H2
Checked with the latest development build
Steps to reproduce the behaviour
When using the fulltext search with a simple single-keyword query, e.g.
test, I only get partial results and a subset of expected entries containing the texttestis not displayed in the search results. When I open the JabRef's Lucene index in Luke and execute the same query (content:test), it returns all related entries including those that are missing in JabRef's search results.The library in which I experience this has 400 entries. When I create a new library and add only one of the missing entries, the fulltext search returns it as expected. When I delete large portions (e.g. 350 entries) from my 400-entry library, that missing search result also starts to appear - this does not seem related to deleting a specific (potentially problematic) entry, as it starts to appear after different random selections of entries are removed. There's also no specific threshold library size that triggers this behavior - I was able to make the result appear after cutting the library randomly down to ~40 - 70 entries.
Appendix
No response