Allow immediate (re) indexing for specific items
Within search driven applications, actual values of columns within items are critical for users. Imagine a task, shown search driven in my open tasks. If user completes the task on the list, user will expect, that this tasks are not shown in the above mentioned my open tasks.
Therefore allow immediate (re) indexing for specific items (like tasks) - possibly configurable. This actually was possible with SP2010 server side code.
Dan Gøran Lunde commented
The ask here is really about supporting push instead of pull.
Jon Tereba commented
We have a search driven application that correlates to a large document library (500K+). We've noticed and confirmed from Microsoft that every once and a while a document may receive a call back error from the continuous or incremental search and therefore the most recent changes to the document are not in the search index. The only way to get the most recent changes would be to make an unnecessary change to the document or to re-index the entire library. It would be nice to be able to manually mark a specific document to re-index rather than having to re-index the entire library.
Gunnar LIed commented
Agreed. Currently the continuous crawl latency, even when put to the lowest level on 1-2 minutes, is non-user-friendly and confusing, especially when rolling up content in search based webparts. If not all (would be the best :-), at least some actions, i.e. publishing a major version, should trigger an immediate reindexing.