Last modified: 2014-11-18 18:07:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 6090 - Add time of last search index update to Special:Search
Add time of last search index update to Special:Search
Product: Wikimedia
Classification: Unclassified
lucene-search-2 (Other open bugs)
All All
: Normal enhancement with 5 votes (vote)
: ---
Assigned To: Robert Stojnic
: 7611 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2006-05-26 05:48 UTC by Borgx
Modified: 2014-11-18 18:07 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Borgx 2006-05-26 05:48:54 UTC
Please add the cache last update timestamp on special:search just like other
special pages (see bug 4327)
Comment 1 Rick Block 2006-11-04 13:37:54 UTC
Users are frequently curious why their articles don't show up in search.  See, for example,
Wikipedia_talk:Searching#Search_for_article_name_not_yielding_article .  Lacking some way to tell when the index was last 
rebuilt, the best that can be said (no matter how long it's been since the article was created) is "the index probably hasn't 
been rebuilt since then".  It would be much better to be able to say "it's not found because the last time the index was 
rebuilt was <date>".
Comment 2 Rob Church 2006-11-04 13:46:19 UTC
This requires us to store this information somewhere in the database, or
otherwise accessible to MediaWiki; search updates are an external process.

Do the Lucene daemons know when their last update was, and if so, could we pull
the information from them upon unsuccessful searches?
Comment 3 Rick Block 2006-11-04 15:42:23 UTC
Perhaps a kludge, but aren't the indices in a file someplace whose last changed
time corresponds to when the index was last rebuilt?  Or, is the process to kick
off the rebuild a shell that could just put the current time somewhere?
Comment 4 Brion Vibber 2007-07-05 18:19:36 UTC
*** Bug 7611 has been marked as a duplicate of this bug. ***
Comment 5 Siebrand Mazeland 2008-08-17 20:02:06 UTC
Mass close WONTFIX open Lucene Search issues because extension Lucene Search was removed, and replaced by MWSearch. Please set to REOPENED if behaviour still exists with a another component, and update the domain.
Comment 6 Siebrand Mazeland 2008-08-17 20:18:20 UTC
Mass REOPEN after discussion with Robert. Domain: Wikimedia/lucene-search-2. Assigned to maintainer.
Comment 7 Foroa 2012-04-04 06:46:27 UTC
Problem still persists and becomes more urgent as several times per month, search don't return any result for more than half an hour, probably because of ongoing search database update.
Comment 8 Foroa 2013-01-01 10:46:02 UTC
Problem still persists, see
Comment 10 Chad H. 2013-10-28 18:57:36 UTC
Marking this WONTFIX as lsearchd has already reached its end of life.

This isn't an issue at all in Cirrus/Elasticsearch as the index is updated in near real time (a few seconds at most).

Note You need to log in before you can comment on or make changes to this bug.