Open teertinker opened 1 year ago
Hi! Thanks for reporting this. Unfortunately I am unable to reproduce the behavior you are seeing. Would you be so kind to share logs regarding this error message? (should be visible in 'Details anzeigen' in the error notification).
Some more things that you can try:
Let me know if the issue still persists after that.
Hi! I added the log file.
Just found a simliar issue from @ThiloteE #8287 where I posted this link https://northcoder.com/post/lucene-fields-and-term-vectors/
Hm, I think the log you posted and the image do not fit well together, as they are different errors.
"bi
. What we would need here would be additional query validation for lucene. Easy fix would be to just add closing quotation marks whenever an uneven number of quotation marks is found in the search string? Nice solution would be query validation and giving the user feedback if the closing quotation mark is missing and refusing search until syntax errors are fixed (which is on my list for things to implement for the full lucene search backend).Thank you for the exploration. The error only occured with fulltext search activated and was accompanied by a lag while typing. So in my case it was probably caused by the second error. Another reason to deactivate fulltext search on default (https://github.com/JabRef/jabref/issues/9491).
JabRef version
5.8 (latest release)
Operating system
GNU / Linux
Details on version and operating system
Ubuntu 21.04
Checked with the latest development build
Steps to reproduce the behaviour
Enter a search term including: "soziale Arbeit" --> the problem does not occur in every situation. It could be caused by the space between the two words.
Appendix
...
Log File
``` Index path for /home/felix/Dokumente/UniDaten/backup/Jena.bib is /home/felix/.local/share/JabRef/lucene94 Could not parse query: '"bi'! Cannot parse '"bi': Lexical error at line 1, column 4. Encountered: