openhatch

Issue585

Title Roundup's search is unreliable
Milestone later Priority critical
Waiting On Status resolved
Superseder Nosy List aldeka, paulproteus, pythonian4000
Assigned To Keywords

Created on 2011-09-05.22:11:50 by aldeka, last changed 2012-09-02.22:03:46 by paulproteus.

Messages
msg3387 (view) Author: paulproteus Date: 2012-09-02.22:03:46
I believe search is now working properly, thanks to not using the (broken, I 
suppose) Xapian support.
msg3343 (view) Author: paulproteus Date: 2012-07-30.08:32:56
I just upgraded to 1.4.20 and reindexed. No improvement.

Then I realized that I could just:

 sudo apt-get remove python-xapian

and Roundup will "downgrade" to using the database for searches.

Maybe now things will be fine. The search for "mission" within the bug tracker 
actually finds more hits now.

I can enable xapian any time anyone asks, if anyone wants to see a demo.

I'd love to get to the root cause, mostly for the benefit of upstream. I think 
we'll be fine with xapian disabled.
msg3342 (view) Author: pythonian4000 Date: 2012-07-30.05:03:58
I don't know if this is the same bug, but there was a bug which broke Roundup
search with Xapian 1.2 - http://issues.roundup-tracker.org/issue2550676 - which
was fixed upstream in Roundup v1.4.17. The latest upstream version is 1.4.20,
and we are on v1.4.15. Might it be worthwhile upgrading?
msg2965 (view) Author: paulproteus Date: 2012-02-08.23:15:30
https://www.google.com/search?q=site%3Aopenhatch.org+inurl%3Abugs+mission

Only *so* useful, but there you go for now...
msg2963 (view) Author: aldeka Date: 2012-02-08.23:12:02
Did we ever bring this up with upstream?

Also: aaaaaaaaaaaugh.
msg2616 (view) Author: paulproteus Date: 2011-11-09.23:33:48
We should bring this up with upstream. Anyway not fixed yet for 0.11.10
msg2587 (view) Author: paulproteus Date: 2011-10-04.19:23:39
I did try this:

* Remove the Xapian index
* Reindex
* Re-do the search

This did not actually fix the problem.

Therefore this is, as far as I can tell, an issue with upstream Roundup.

If we want to try digging deeper, we should read the Roundup code and see how
they're using Xapian. Maybe there's e.g. some configuration option they set that
is inappropriate.

The other next step is to file a bug with upstream's bug tracker, perhaps with a
copy of our database or instructions on how to reproduce the problem.

It'd be nice if there were a command-line test tool that we could use to test if
searches find things we expect them to. There's the roundup-admin tool, but per
http://roundup.sourceforge.net/doc-1.0/user_guide.html it doesn't seem to have a
search option.
msg2555 (view) Author: paulproteus Date: 2011-10-01.06:06:12
So here's what I know about this:

* Roundup uses Xapian to store an index

* There is a command to regenerate the index

* Surprisingly, when you regenerate the index, these searches still fail to find
things.

Things to try next:

* Remove the Xapian index

* Reindex

* Re-do the search.
msg2484 (view) Author: aldeka Date: 2011-09-05.22:18:03
Just confirmed that issue550 and issue546 were also missed in that 'mission'
search. Argh!
msg2482 (view) Author: aldeka Date: 2011-09-05.22:11:50
Search for 'mission' on the top right. You get taken to
https://openhatch.org/bugs/issue?%40columns=id%2Cactivity%2Ctitle%2Ccreator%2Cassignedto%2Cstatus%2Cmilestone&%40sort=activity&%40group=priority&%40search_text=mission&submit=Search

This doesn't *actually* have all of the bugs with 'mission' in their title or
body text. For instance, (I noticed) issue535 does not appear. There are
probably many others. Unfortunately, because of this problem, I have no way to
tell how many!

I first noticed this problem in trying to find all of the 'buildhelper' related
bugs. Several bugs--bugs with 'buildhelper' in the title!--would never appear in
searches. I could only access them easily because I was the one who opened them. >.<

Without reliable, working Roundup search, there's no way to handle and reliably
process the huge volume of bugs in this issue tracker. And it's been bugging me
for a long time. Marking as 'critical' for that reason.
History
Date User Action Args
2012-09-02 22:03:46paulproteussetstatus: in-progress -> resolved
messages: + msg3387
2012-07-30 08:32:57paulproteussetstatus: need-review -> in-progress
messages: + msg3343
2012-07-30 05:04:02pythonian4000setstatus: chatting -> need-review
nosy: + pythonian4000
messages: + msg3342
2012-02-08 23:15:31paulproteussetmessages: + msg2965
2012-02-08 23:12:03aldekasetmessages: + msg2963
2011-11-09 23:33:54paulproteussetmessages: + msg2616
milestone: 0.11.10 -> later
2011-10-04 19:23:40paulproteussetmessages: + msg2587
2011-10-01 06:06:13paulproteussetmessages: + msg2555
milestone: 0.11.09 -> 0.11.10
2011-09-05 22:18:03aldekasetstatus: unread -> chatting
messages: + msg2484
2011-09-05 22:11:50aldekacreate