[ 
https://issues.apache.org/jira/browse/SOLR-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916126#comment-13916126
 ] 

Hoss Man commented on SOLR-5795:
--------------------------------

The one hitch with this idea -- which is already a problem if you do the same 
logic from an external client -- is that ass things stand today, if you do a 
lot of periodic {{deleteByQuery}} commands with auto-commit, every one will 
cause a new searcher to be opened, even if nothing was actually deleted -- but 
it looks like we can fix that independently in SOLR-5783.

I'm going to tackle the design i laid out here once I get SOLR-5783 in shape 
with enough tests that i'm comfortable committing.

> Option to periodically delete docs based on an expiration field -- or ttl 
> specified when indexed.
> -------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5795
>                 URL: https://issues.apache.org/jira/browse/SOLR-5795
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>
> A question I get periodically from people is how to automatically remove 
> documents from a collection at a certain time (or after a certain amount of 
> time).  
> Excluding from search results using a filter query on a date field is 
> trivial, but you still have to periodically send a deleteByQuery to clean up 
> those older "expired" documents.  And in the case where you want all 
> documents to auto-expire some fixed amount of time when they were indexed, 
> you still have to setup a simple UpdateProcessorto set that expiration date.  
> So i've been thinking it would be nice if there was a simple way to configure 
> solr to do it all for you.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to