You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, JabRef employs two different search backends: PostgreSQL and Apache Lucene. PostgreSQL is used for the search within the library (.bib file) and Apache Lucene is used for the fulltext search of PDF files.
It turned out that it is really hard to get "contains" search working properly in Lucene.
the query must be tokenized using the same tokenizer as during indexing to extract words from the query and look into the index for these words.
Currently, JabRef employs two different search backends: PostgreSQL and Apache Lucene. PostgreSQL is used for the search within the library (.bib file) and Apache Lucene is used for the fulltext search of PDF files.
It turned out that it is really hard to get "contains" search working properly in Lucene.
This will fix JabRef#235.
Working on handling following variants for the same word is as hard in Postgres as it is in Lucene:
Düsseldorf
Duesseldorf
D\"{u}sseldorf
Dusseldorf
The text was updated successfully, but these errors were encountered: