You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Chamnap Chhorn <ch...@gmail.com> on 2010/07/12 11:39:57 UTC
Ranking position in solr
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?
--
Chhorn Chamnap
http://chamnapchhorn.blogspot.com/
Re: Ranking position in solr
Posted by Markus Jelsma <ma...@buyways.nl>.
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 <io...@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
Re: Ranking position in solr
Posted by Chamnap Chhorn <ch...@gmail.com>.
I sent this command: curl http://localhost:8081/solr/update -F stream.body='
<commit />', but it doesn't reload.
It doesn't reload automatically after every commit or optimize unless I add
new document then i commit.
Any idea?
On Tue, Jul 13, 2010 at 4:54 PM, Ahmet Arslan <io...@yahoo.com> wrote:
> > I'm using solr 1.4 and only one core.
> > The elevate xml file is quite big, and
> > i wonder can solr handle that? How to reload the core?
>
> Markus Jelsma's suggestion is more robust. You don't need to restart or
> reload anything. Put elevate.xml under data directory. It will reloaded
> automatically after every commit or optimize.
>
>
>
>
--
Chhorn Chamnap
http://chamnapchhorn.blogspot.com/
Re: Ranking position in solr
Posted by Ahmet Arslan <io...@yahoo.com>.
> I'm using solr 1.4 and only one core.
> The elevate xml file is quite big, and
> i wonder can solr handle that? How to reload the core?
Markus Jelsma's suggestion is more robust. You don't need to restart or reload anything. Put elevate.xml under data directory. It will reloaded automatically after every commit or optimize.
Re: Ranking position in solr
Posted by Chamnap Chhorn <ch...@gmail.com>.
I'm using solr 1.4 and only one core. The elevate xml file is quite big, and
i wonder can solr handle that? How to reload the core?
On Tue, Jul 13, 2010 at 4:12 PM, Ahmet Arslan <io...@yahoo.com> 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?
>
> You can reload core, without restarting tomcat, if you are using multi-core
> setup. Which version of solr are you using?
>
>
>
>
--
Chhorn Chamnap
http://chamnapchhorn.blogspot.com/
Re: Ranking position in solr
Posted by Ahmet Arslan <io...@yahoo.com>.
> 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?
You can reload core, without restarting tomcat, if you are using multi-core setup. Which version of solr are you using?
Re: Ranking position in solr
Posted by Chamnap Chhorn <ch...@gmail.com>.
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 <io...@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.
>
>
>
>
--
Chhorn Chamnap
http://chamnapchhorn.blogspot.com/
Re: Ranking position in solr
Posted by Ahmet Arslan <io...@yahoo.com>.
> 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.