We use Solr quite a bit at edelight -- and love it. However, we encountered one
minor peeve: although each individual
Solr server has its own dashboard, there's no easy way of getting a complete
overview of an entire Solr cluster and the
status of its nodes.
Over the last weeks our own Aengus Wa
.
Much appreciated!
Kind regards,
Alexander Valet
--
edelight GmbH, Wilhelmstr. 4a, 70182 Stuttgart
Fon: +49 (0)711-912590-14 | Fax: +49 (0)711-912590-99
Geschäftsführer: Peter Ambrozy, Steffen Belitz, Tassilo Bestler
Amtsgericht Stuttgart, HRB 722861
Hi everybody,
we are using Solr 1.4.1 as our search backend and are replicating (Java based)
from one master to four slaves.
When our index data grew in size (optimized around 4,5 GB) lately we started
having huge trouble to spread a new index to
the slaves. They run on 100% CPU and are not able
Hi, thanks for your help, I figued it out myself I guess.
All parts of an fq are always intersected, so it has no effect to put
a boolean operator inside a fq like in
fq=+tags:(Gucci) OR -tags:(watch sunglasses)
(would be a mildly strange query anyway)
The order in which the intersections are m
Hi, thanks for your help, I figued it out myself I guess.
All parts of an fq are always intersected, so it has no effect to put
a boolean operator inside a fq like in
fq=+tags:(Gucci) OR -tags:(watch sunglasses)
(would be a mildly strange query anyway)
The order in which the intersections are m
Hi,
i was wondering how the following query might be processed:
?q=*:*&fq=+tags:(Gucci)&fq=-tags:(watch sunglasses)
and if there is a difference to a query with only one fq parameter like
?q=*:*&fq=+tags:(Gucci) -tags:(watch sunglasses)
I am aware of the chaching implications but i am not sure
