# Feedback on new search

**URL:** https://discourse.jabref.org/t/feedback-on-new-search/4466
**Category:** General Feedback
**Created:** [August 28, 2024, 10:26am UTC](https://discourse.jabref.org/t/feedback-on-new-search/4466 "2024-08-28T10:26:46Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![koppor](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/koppor/32/5_2.png) [@koppor](https://discourse.jabref.org/u/koppor)
#### Post date: [August 28, 2024, 10:26am UTC](https://discourse.jabref.org/t/feedback-on-new-search/4466/1 "2024-08-28T10:26:46Z")

</div>

In the context of GSoC, we worked hard to get a new search finished. We need to update all documentation, create a blog post, etc.

TL;DR: We updated the search to Apache Lucene. The syntax is explained at [Searching externally using Online Services | JabRef](https://docs.jabref.org/collect/import-using-online-bibliographic-database#examples). Try it out - but ensure that you made a **backup of your library**.

* * *

The [pull request switching to Apache Lucene](https://github.com/JabRef/jabref/pull/11542) is close to a merge. We now aim for feedback. Both for show stoppers and improvements, we should target for 6.0 release of JabRef. We noticed that [JabRef’s v5.x Simple Search](https://docs.jabref.org/v/v5/finding-sorting-and-cleaning-entries/search#simple-search) sometimes did not work. Thus, we did not convert these kinds of searches.

The current implementation does not support a) case sensitive search and b) exact matches. “exact matches” mean that a search for “apple” DOES NOT match “pineapple”. It can be achieved by using regular expression search for `[^\w]apple[^\w]` IMHO.

* * *

**Call for action** : Download the [Lucene search](https://builds.jabref.org/pull/11542/merge) build and try if it works “OK” enough to be included in a developer build.