On 10/11/07, BrendanD <[EMAIL PROTECTED]> wrote:
> Yes, we have some huge performance issues with non-cached queries. So doing a
> commit is very expensive for us. We have our autowarm count for our
> filterCache and queryResultCache both set to 4096. But I don't think that's
> near high enough. We
gt;> listings if their accounts run out of funds.
>
> means "make my edits visible now". Can you explain why
> this isn't exactly what you need? Are there performance problems?
>
> The flushing deletes parameter is a performance knob only: it doesn't
> actually make the deletes visible until
>
> -Mike
>
>
--
View this message in context:
http://www.nabble.com/Instant-deletes-without-committing-tf4610169.html#a13166522
Sent from the Solr - User mailing list archive at Nabble.com.
On 11-Oct-07, at 2:47 PM, BrendanD wrote:
Hi,
Is it possible to send a command to have Solr flush the deletesPending
documents without doing a commit? I know there's a setting in
solrconfig.xml
for setting a threshold value, but I'd like to somehow kick it off on
demand. We need this to be
ur product
listings if their accounts run out of funds.
Thanks,
Brendan
--
View this message in context:
http://www.nabble.com/Instant-deletes-without-committing-tf4610169.html#a13165413
Sent from the Solr - User mailing list archive at Nabble.com.
