Vinod Kumar Nardiya
Vinod Kumar Nardiya

Reputation: 1

Inconsistent Solr Search Behavior for Customers with Job and Customers Without Job - Partial vs. Whole Word Search Issue

We are facing a puzzling issue with Solr search integration in Laravel, and we could really use some expert guidance to resolve this matter.

Our project involves indexing data on Solr using Laravel. Within our indexed data, we have two distinct types of customers - Customers with Job and Customers Without Job.

However, we have noticed a perplexing difference in the search behavior of Solr for these two customer types:

For Customers with Job:

As we start typing a word in the search input, Solr immediately returns relevant data (partial word search).

For Customers Without Job:

Solr only returns data after we have entered the entire word (full word search).

This inconsistent behavior is creating confusion for our users and negatively impacting the user experience. Ideally, we want Solr to exhibit the same partial word search behavior for both customer types.

Upon inspecting our indexing configuration in Laravel, we haven't identified any noticeable discrepancies between the data of Customers with Job and Customers Without Job.

Has anyone encountered a similar issue with Solr integration in Laravel, or is there a specific configuration or setting that might be causing this difference in search behavior between the two customer types?

We would greatly appreciate any insights, suggestions, or potential solutions to ensure uniform search behavior for both types of customers using Solr in Laravel.

Thank you so much for your assistance!

For Customers Without Job:

Solr should return data as soon as we start typing a word.

Note:

We are using Dismax query parser and searching on multiple fields.

Upvotes: 0

Views: 52

Answers (0)

Related Questions