cancel
Showing results for 
Search instead for 
Did you mean: 

Issues with search bar suggestions after turning on "case insensitive search and suggestions" and creating full-text indexes

neo
Node

After turning on "case insensitive search and suggestions" and creating full-text indexes, there are issues with the suggestions in the search bar. In many instances where there should be clear matches, suggestions do not appear.

Full text indexes were created like this:
CALL db.index.fulltext.createNodeIndex("nameIndex", ["Name"], ["name"]);

If I then search this index using Cypher for a specific name, it returns correctly:
e.g. CALL db.index.fulltext.queryNodes('nameIndex', 'first5lettersofname')

But typing these same 5 letters in the Bloom search bar does not result in this name being shown as a suggestion.

Bloom 1.6, Neo4j 4.1.3

Example to reproduce:

Make sure that there is fulltext index for "Contact", e.g.:
CALL db.index.fulltext.createNodeIndex("ContactIndex", ["Contact"], ["name"])

Create a node "Contact" with property "name": "aal lantaarnpaal".

Now type "aal" in the Bloom search bar (without pressing enter).
Result: "aal lantaarnpaal" is shown as a suggestion with "aal" underlined twice. So far so good.

But now type "lantaarn".
Result: our contact is NOT shown as suggestion, while obviously we do expect this.

Is there some type of stemming going on behind the scenes?

1 REPLY 1

I have the same problem in 2022.

Nodes 2022
Nodes
NODES 2022, Neo4j Online Education Summit

On November 16 and 17 for 24 hours across all timezones, you’ll learn about best practices for beginners and experts alike.