No, it can build for each new searcher [1]. [1]: http://wiki.apache.org/solr/QueryElevationComponent#config-file
On Tuesday 13 July 2010 11:02:10 Chamnap Chhorn wrote: > The problem is that every time I update the elevate.xml, I need to restart > solr tomcat service. This feature needs to be updated frequently. How would > i handle that? > > Any idea or other solutions? > > On Mon, Jul 12, 2010 at 5:45 PM, Ahmet Arslan <iori...@yahoo.com> wrote: > > > I wonder there is a proper way to > > > fulfill this requirement. A book has > > > several keyphrases. Each keyphrase consists from one word > > > to 3 words. The > > > author could either buy keyphrase position or don't buy > > > position. Note: each > > > author could buy more than 1 keyphrase. The keyphrase > > > search must be exact > > > and case sensitive. > > > > > > For example: Book A, keyphrases: agile, web, development > > > Book B, keyphrases: > > > css, html, web > > > > > > Let's say Author of Book A buys search result position 1 > > > with keyphrase > > > "web", so his book should be in the first position. His > > > book should be > > > listed before the Book B. > > > > > > Anyone has any suggestions on how to implement this in > > > solr? > > > > http://wiki.apache.org/solr/QueryElevationComponent - which is used to > > "elevate" results based on editorial decisions - may help. > Markus Jelsma - Technisch Architect - Buyways BV http://www.linkedin.com/in/markus17 050-8536620 / 06-50258350
