I'm not sure if this is a bug or a support request. I upgraded from luceneapi 6.x-2.0-beta1 to beta3 and noticed that search by title no longer worked, i.e. when I search for a keyword that appears in a node title, the node will appear in the search result with beta1 but not with beta3. I wiped and rebuild the index several times, deleted the folder that lucene creates in sites/default/files and checked this behaviour a few times, but I always get the same result.

Going back to beta1 and reindexing immediately makes node title matches appear in the search results again. Is it possible that beta3 has removed or broken title matches, or am I doing it wrong?

In other words, can someone else confirm that beta3 does index node titles for them?

Comments

Bodo Maass’s picture

One more observation:
I just deleted the luceneapi beta3 folder and restored the beta1 archive without rebuilding the index, and the result is still the same: beta1 includes title matches, but beta3 doesn't (at least for me).

cpliakas’s picture

Assigned: Unassigned » cpliakas
Priority: Normal » Critical
Issue tags: +6.x-2.0-beta4

Thanks for posting.

I will research this. I was actually going to file a bug report because I noticed that there are some inconsistencies with search results in complex queries due to a logic error in the way the content bias subqueries are added. It may or may not be related, but you are correct in your assertion that node titles should be returned. In fact, the default settings places more importance on node titles. I am attending a code sprint this weekend, so hopefully beta4 will be released by the beginning of next weak with the fix.

Great find,
Chris

cpliakas’s picture

cpliakas’s picture

Issue tags: -6.x-2.0-beta4

I just tested this with the fix applied to the issue in #3. I searched for a term that was contained in the title and not the body, and the document containing the term in the title was returned. As a side note, make sure the title field bias setting is not set to "Don't search", otherwise titles will not be searched by default. I am leaving this issue open so it can be tested after the 6.x-2.0-beta4 release.

cpliakas’s picture

Status: Active » Fixed

This has been thoroughly tested, and I don't see this as being a problem in beta4.

Bodo Maass’s picture

Yes, seems to be working now. Thank you very much.

cpliakas’s picture

Thanks for the confirmation and initial report!

~Chris

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.