Thanks for this great work on Lucene search for Drupal!

I have set up a view of nodes with the luceneapi views filter, which is basically working. When I search for something that appears in the data, only the relevant items remain in the view.

However, when I search for something that does not exist, the view returns all items, just like when no filter at all is entered. What I would expect is that the view would be empty in this case. Is this a bug, or am I doing it wrong?

Comments

cpliakas’s picture

Hi.

Thanks for testing this module, and sorry for the late reply. I think that this is a very valid bug report, as searching for something that does not exist should return no results. For example, if you have a view that displays content with the values 1, 2, and 3, searching for "4" should return nothing.

Thanks for pointing this out!
~Chris

Bodo Maass’s picture

Ok, thanks for the confirmation that it is a bug.

I had a first look at the code, but I don't know enough about views filters yet to understand this quickly.

cpliakas’s picture

Status: Active » Fixed

Fixed in commit #322096. The module has been rebuilt, and as a result, this bug is fixed.

Status: Fixed » Closed (fixed)

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

Bodo Maass’s picture

Status: Closed (fixed) » Active

Ok, great. I just downloaded the latest lucene api module and also the current cvs head of this module. Unfortunately it doesn't seem to work yet. At least the views filter Node:Lucene Query is no longer available with this new version.
Is this already meant to be working, or should I wait for a real release?

Thank for the great work.

cpliakas’s picture

Hi!

Thanks for testing. It is not quite ready for use as there are a few known bugs, but I am hoping to release an alpha within the next couple of months. Maybe sooner if I can get in a groove.

Thanks for the feedback, and thanks for testing!
~Chris

Bodo Maass’s picture

Well the old version of 'Search Lucene Views' is working very well except for the one bug mentioned here and is very useful. Why don't you leave it as the official downloadable build if the next one might not be ready for a couple of months?

cpliakas’s picture

I didn't leave it because I like to commit regularly, and the dev build gets updated nightly with HEAD (which is the onlt line of development in this case). Therefore the dev build would be changing drastically and would frustrate users since the architecture is taking a different direction.

cpliakas’s picture

Status: Active » Closed (won't fix)

Due to end of life announcement.