Closed (won't fix)
Project:
Search Lucene API
Version:
6.x-2.2
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 Feb 2010 at 14:19 UTC
Updated:
29 Sep 2011 at 16:47 UTC
Jump to comment: Most recent file
Comments
Comment #1
cpliakas commentedHi r3to.
Sorry for your issues. This seems like a weird issue, and I cannot replicate it on any of my environments. Does the core search behave the same way?
Thanks,
Chris
Comment #2
walker2238 commentedI can confirm this issue. From my experience the minimum character count has something to do with this. I haven't done much trouble shooting as of yet but say I have minimum characters set to 4 and if I search for a word with less than 4 characters then all nodes show up in the search results.
Comment #3
cpliakas commentedwalker2238,
Thanks for the detailed use case. I will try to replicate, and I am flagging this issue to be fixed in the next release.
Thanks,
Chris
Comment #4
cpliakas commentedThis has been confirmed. Changing "Component" to a coding problem.
Comment #5
cpliakas commentedIssue resolved in commit #330222.
Comment #7
cpliakas commentedAs per the post at #832066: Lucene Search displays the same result for all searches / ignores search keyword, this issue is not yet resolved in all cases. Re-opening and tagging for the 6.x-2.3 release.
Comment #8
cpliakas commentedThis thread also may be applicable to this issue: #730064: Query won't execute if first key is a stopword
Comment #9
cpliakas commentedBumping to the 6.x-2.4 release, need more debugging information to resolve since I can't replicate.
Comment #10
cpliakas commentedBumping to next version to accommodate critical bugfix release.
Comment #11
davemybes commentedI have the same issue, on a multisite setup using Domain Access. It does not matter if I'm logged in or not, the results are always the same. The results are the same on all the sites in the multisite. PHP version is 5.1.6. If I clear the cache_luceneapi table, then results are shown correctly for the first search. Subsequent searches show those same results. Looks like it always pulls the first set of cached results.
*Edit*: subsequent searches do not change the structure of the cache_luceneapi table at all. Not sure about the data in the blobs.
Comment #12
davemybes commentedScreenshot of cache_lucenapi attached.
Comment #13
cpliakas commentedDue to end of life announcement.