Comments inline:
On Sun, Feb 15, 2015 at 2:09 AM, jaime spicciati
wrote:
> All,
> This is my current understanding of how SolrCloud load balancing works...
>
> Within SolrCloud, for a cluster with more than 1 shard and at least 1
> replica, the Zookeeper aware SolrJ client uses LBHTTPSolrServer
I think you meant to say that the shard has MORE than 1 replica. If a shard
has only 1 replica, then a query to that shard can only go to that one node.
Also, the leader is by definition a replica as well. So, where you say "the
leader or replica", that should be "a replica which may happen to be
Hello,
You can totally boost by calculations that happen on-the-fly on a
per-document basis when you search. These are called function queries in
Solr.
Your your specific example… a solution that doesn’t involve writing a custom
so-called ValueSource in Java would likely mean calculating the dist
All,
This is my current understanding of how SolrCloud load balancing works...
Within SolrCloud, for a cluster with more than 1 shard and at least 1
replica, the Zookeeper aware SolrJ client uses LBHTTPSolrServer which is
round robin across the replicas and leaders in the cluster. In turn the
shar
I hit a block when I ran into a use case where I had to boost on ranges of
distances calculated at query time. This is the case when the distance is
not present in the document initially but calulated based on the user
entered lat/long values.
1. Is it required that all the boost parameters be se
Hi,
I am using Solr 4.8.1 and when i am creating the new request handler i am
getting the following error:
*Request Handler config:*
edismax
on
*:*
0.01
type:garments
*Error:*
Any idea?
> On 12 Şub 2015, at 11:12, Volkan Altan wrote:
>
> Hello Everyone,
>
> All I want to do with Solr suggester is obtaining the fact that the asserted
> suggestions for the second letter whose entry actualizes after the initial
> letter is actually related to initial letter, itself
