NRT does not work because index updates hundreds times per second vs. "cache" warm-up time few minutes and we are in a loop
> allowing you to query > your huge index in ms. Solr also allows to query in ms. What is the difference? No one can sort 1,000,000 terms in descending "counts" order faster than current Solr implementation, and FieldCache & UnInvertedCache can't be used together with NRT cache discarded few times per second! - Fuad http://www.tokenizer.ca On 12-08-14 8:17 AM, "Nagendra Nagarajayya" <nnagaraja...@transaxtions.com> wrote: >You should try realtime NRT available with Apache Solr 4.0 with >RankingAlgorithm 1.4.4, allows faceting in realtime. > >RankingAlgorithm 1.4.4 also provides an age feature that allows you to >retrieve the most recent changed docs in realtime, allowing you to query >your huge index in ms. > >You can get more information and also download from here: > >http://solr-ra.tgels.org > >Regards > >- Nagendra Nagarajayya >http://solr-ra.tgels.org >http://rankingalgorithm.tgels.org > >ps. Note: Apache Solr 4.0 with RankingAlgorithm 1.4.4 is an external >implementation > > >On 8/13/2012 11:38 AM, Fuad Efendi wrote: >> SOLR-4.0 >> >> I am trying to implement this; funny idea to share: >> >> 1. http://wiki.apache.org/solr/HierarchicalFaceting >> unfortunately it does not support date ranges. However, workaround: use >> "String" type instead of "*_tdt" and define fields such as >> published_hour >> published_day >> published_week >> S( >> >> Of course you will need to stick with timezone; but you can add an >>index(es) >> for each timezone. And most important, "string" facets are much faster >>than >> "Date Trie" ranges. >> >> >> >> 2. Our index is overs 100 millions (from social networks) and rapidly >>grows >> (millions a day); cache warm up takes few minutes; Near-Real-Time does >>not >> work with faceting. >> >> HoweverS( another workaround: we can have Daily Core (optimized at >>midnight), >> plus Current Core (only today's data, optimized), plus Last Hour Core >>(near >> real time) >> >> "Last Hour Data" is small enough and we can use Facets with Near Real >>Time >> feature >> >> Service layer will accumulate search results from three layers, it will >>be >> near real time. >> >> >> >> Any thoughts? Thanks, >> >> >> >> >
