lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saroj C <saro...@tcs.com>
Subject Re: Dynamically loading Elevation Info
Date Tue, 23 Apr 2013 05:50:35 GMT
Thanks Ravi and Eric. Will try these options.


Thanks and Regards,
Saroj Kumar Choudhury

____________________________________________
Experience certainty.   IT Services
                        Business Solutions
                        Outsourcing
____________________________________________



From:
Ravi Solr <ravisolr@gmail.com>
To:
"solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Date:
22-04-2013 23:27
Subject:
Re: Dynamically loading Elevation Info



If you place the elevate.xml in the data directory of your index it will 
be
loaded every time a commit happens.

Thanks

Ravi Kiran Bhaskar


On Mon, Apr 22, 2013 at 7:38 AM, Erick Erickson 
<erickerickson@gmail.com>wrote:

> I believe (but don't know for sure) that the QEV file is re-read on
> core reload, which the same app that modifies the elevator.xml file
> could trigger with an http request, see:
>
> http://wiki.apache.org/solr/CoreAdmin#RELOAD
>
> At least that's what I would try first.
>
> Best
> Erick
>
> On Mon, Apr 22, 2013 at 2:48 AM, Saroj C <saroj.c@tcs.com> wrote:
> > Hi,
> >  Business User wants to configure the elevation text and the IDs and 
they
> > want to have an UI to do the same. As soon as they configure, it 
should
> be
> > reflected  in SOLR,(without restarting).
> >
> > My understanding is, Now, the QueryElevationComponent reads the
> > Elevator.xml(Configurable) and loads the information into 
ElevationCache
> > during startup and uses the information while responding to queries. 
Is
> > there any way, the content in the ElevationCache can be modifiable  by
> > some other external process / is there any easy way of achieving this
> > requirement ?
> >
> > Thanks and Regards,
> > Saroj Kumar Choudhury
> > =====-----=====-----=====
> > Notice: The information contained in this e-mail
> > message and/or attachments to it may contain
> > confidential or privileged information. If you are
> > not the intended recipient, any dissemination, use,
> > review, distribution, printing or copying of the
> > information contained in this e-mail message
> > and/or attachments to it are strictly prohibited. If
> > you have received this communication in error,
> > please notify us by reply e-mail or telephone and
> > immediately and permanently delete the message
> > and any attachments. Thank you
> >
> >
>



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message