Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate fultlext search from Lucene to PostgreSQL #12261

Open
koppor opened this issue Dec 2, 2024 · 0 comments
Open

Migrate fultlext search from Lucene to PostgreSQL #12261

koppor opened this issue Dec 2, 2024 · 0 comments
Labels
Milestone

Comments

@koppor
Copy link
Member

koppor commented Dec 2, 2024

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.

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants