I have made changes as listed in document ( sol.xml, core.properties, schema
changes) before i did upgrade
I am using solrcloud deployment
Doing node by node upgrade.
Almost everything work fine. Except if new upgraded node ( node which is
upgraded to 5.5) become leader than even if that node go
I'm a little confused. The "aggregator" node is just the Solr node
that happens to receive the call from the client. There is no fixed
aggregator node unless you're doing something custom.
So any replica can act as the aggregator, and in fact each and every
node acts as an aggregator at some point
Yes. i was looking for some kind of event listeners for client :)
On 26 March 2016 at 21:46, Andrea Gazzarini wrote:
> Hi Anil,
> If with "Application" you mean an external / remote Application then
> there's no such pre-built mechanism to do that.
>
> The event is not notifies "in" your applica
Hi Anil,
If with "Application" you mean an external / remote Application then
there's no such pre-built mechanism to do that.
The event is not notifies "in" your application or "to" your application.
Solr knows nothing about it.
Specifically, event listeners allows you to do something when a give
I am testing rolling upgrade fro 4.4 to 5.5
upgraded nodes start and i can see running status in in admin UI
But
node which is updated, get error
3/26/2016, 8:59:16 AM
<> ERROR
<> null
<> RecoveryStrategy
<> Error while trying to recover.
core=marin:java.util.concurrent.Exe
HI Alex,
i am still no clear how an event is notified in my application if it
listener is configured in SolrConfig.xml (centralized solr server). can you
please clarify?
Sorry for dumb question.
Thanks,
Anil
On 26 March 2016 at 19:48, Andrea Gazzarini wrote:
> Hi Anil,
> see here [1] where I
Thanks. Perfect. i was looking at same post :)
On 26 March 2016 at 19:48, Andrea Gazzarini wrote:
> Hi Anil,
> see here [1] where I did some data pre-loading at solr startup. The post
> has been written in 2014 so maybe something could have a different name
> (class, methods)
>
> Best,
> Andrea
Hi Anil,
see here [1] where I did some data pre-loading at solr startup. The post
has been written in 2014 so maybe something could have a different name
(class, methods)
Best,
Andrea
[1]
http://andreagazzarini.blogspot.it/2014/11/preloading-data-at-solr-startup.html
On 26 Mar 2016 15:14, "Anil"
Thanks Alex. Let me digg more in that area.
On 26 March 2016 at 19:40, Andrea Gazzarini wrote:
> Event listeners are custom classes so you could do "anything"however I
> guess the event firing is synchronous so the listener logic should be
> no-blocking and as fast as possible.
>
> But this
Event listeners are custom classes so you could do "anything"however I
guess the event firing is synchronous so the listener logic should be
no-blocking and as fast as possible.
But this is my guess, I hadn't look at the code. Instead, if the listener
invocation is asynch then forget my commen
Can solr notify other systems on commit of document ?
On 26 March 2016 at 13:59, Alexandre Rafalovitch wrote:
> Well, the updated documents are not visible until the commit. So,
> perhaps you just need the commit listeners then. Those could be any
> external scripts I believe.
>
> Regards,
>
Hi Emir,
that sounds like a great idea and filtering should be just fine!
In our case we need the individual price values (not the buckets), just
like facet.field=price but with respect to the user prices. Is this
possible as well?
About the performance: Are there any specific bottlenecks you wo
Well, the updated documents are not visible until the commit. So,
perhaps you just need the commit listeners then. Those could be any
external scripts I believe.
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 26 March 2016 at 1
I wrote a transformer for DIH to get the value from a field using Http call.
Since this runs on a SOLR node when indexing, I think I would do it with
SOLRJ.
How do I take this and convert it to SOLRJ and avoid the network call ?
Also, this is pretty cool, and avoids the Entity for the call - sinc
14 matches
Mail list logo
