gt; frequencies in the data. We are now looking for a good commit/merge
> strategy. Any advice?
>
> Thanks and best,
> Peter
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Looking-for-a-good-commit-merge-strategy-tp3582294p3582294.html
, I will take a look!
@ Nagendra: Solr-RA seems very interesting! I take it that you can use it
with an existing index?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Looking-for-a-good-commit-merge-strategy-tp3582294p3582626.html
Sent from the Solr - User mailing list archive
@ project: Thanks for the hints, I will take a look!
@ Nagendra: Solr-RA seems very interesting! I take it that you can use it
with an existing index?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Looking-for-a-good-commit-merge-strategy-tp3582294p3582626.html
Sent from
-ra.tgels.org
http://rankingalgorithm.tgels.org
--
View this message in context:
http://lucene.472066.n3.nabble.com/Looking-for-a-good-commit-merge-strategy-tp3582294p3582380.html
Sent from the Solr - User mailing list archive at Nabble.com.
y happen, but they do not have a high priority. Search
> results do not need to be exactly reatime (they can be 1 minute or so
> behind), but facet counts should be correct as we use them to visualize
> frequencies in the data. We are now looking for a good commit/merge
> strategy
. Search
results do not need to be exactly reatime (they can be 1 minute or so
behind), but facet counts should be correct as we use them to visualize
frequencies in the data. We are now looking for a good commit/merge
strategy. Any advice?
Thanks and best,
Peter
--
View this message in context:
http
