Isn't this already done?

(In reply to comment #1)

Isn't this already done?

Nevermind, missed the term "search engine" :)

rainman wrote:

Index is updated using articles from OAI repository and/or xml dumps. AFAIK, OAI doesn't know distinction between sighted or not. Not sure if dumpBackup has a switch to get sighted versions only?

gnu1742 wrote:

Well, that is the reason why i started with 'please evaluate the possibility...'... Anyway: What is OAI?

Edits call SearchUpdate(), so normally a revert would update the search index...does the lucene engine head those calls?

rainman wrote:

No, lucene backend periodically fetches new changes from the OAI repository (which contains all the changes made to the wiki). AFAIK, SearchUpdate is only used in built-in MW search.

gnu1742 wrote:

Has anything been done about this issue? It's the bugs 1st birthday in a few days ;-)

[Merging "MediaWiki extensions/Lucene Search" into "Wikimedia/lucene-search2", see bug 46542. You can filter bugmail for: search-component-merge-20130326 ]

This looks possible, though definitely low priority, with the new CirrusSearch: as it uses some queue system, I suppose the index update could be delayed until the revision is approved. (May need to be moved to FlaggedRevs component if the search system already allows such modifications.)

This will be significantly mitigated with CirrusSearch because it updates articles right after they are changed. I'm not sure how it interacts with FlaggedRevs at the moment but I'll be sure to have a look at some point in the future.

Change 104675 had a related patch set uploaded by Chad:
Support FlaggedRevs

https://gerrit.wikimedia.org/r/104675

Change 104675 abandoned by Chad:
Support FlaggedRevs

Reason:
With the latest implementation in Iff0bf5d5 this isn't needed anymore. We'll add a hook to FlaggedRevs to support it.

https://gerrit.wikimedia.org/r/104675