Take a loot at solrconfig.xml. You configure filtrerCache,
documentCache, queryResultCache. These (and
some others I believe, but certainly these) are _not_
per-segment caches, so are invalidated on soft commit.
Any autowarming you've specified also gets executed
if applicable.
On the other hand,
Erik-
/It does invalidate the "top level" caches, including the caches you
configure in solrconfig.xml. /
Could you elucidate?
--
View this message in context:
http://lucene.472066.n3.nabble.com/commit-vs-soft-commit-tp4083817p4083844.html
Sent from the Solr - User mailing list archive at Nabb
Soft commits also do not rebuild certain per-segment caches
etc. It does invalidate the "top level" caches, including
the caches you configure in solrconfig.xml.
So no, it's not free at all. Your soft commits should still
be as long an interval as makes sense in your app. But
they're still much fa
Yes a new searcher is opened with every soft commit. It's still considered
faster because it does not write to the disk which is a slow IO operation
and might take a lot more time.
On Sunday, August 11, 2013, tamanjit.bin...@yahoo.co.in wrote:
> Hi,
> Some confusion in my head.
> http://
> http:/
