Thank you. I'll try NRT and some post-filter :)
On Tue, Feb 7, 2012 at 3:09 PM, Erick Erickson <erickerick...@gmail.com> wrote: > You have several options: > 1> if you can go to trunk (bleeding edge, I admit), you can > get into the near real time (NRT) stuff. > 2> You could maintain essentially a post-filter step where > your app maintains a list of deleted messages and > removes them from the response. This will cause > some of your counts (e.g. facets, grouping) to be slightly > off > 3> Train your users to expect whatever latency you've > built into the system (i.e. indexing, commit and replication) > > Best > Erick > > On Mon, Feb 6, 2012 at 10:42 AM, Pawel Rog <pawelro...@gmail.com> wrote: >> Hello. I have some problem which i'd like to solve using solr. I have >> user profile which has some kind of messages in it. User can filter >> messages, sort them etc. The problem is with delete operation. If user >> click on message to delete it it's very hard to update index of solr >> in real time. When user deletes message, it will be still visible. >> Have you idea how to solve problem with removing data?
