Hello,
I've started to evaluate Solr and so far haven't seen anything mentions for
support of compound indexes.
I'm looking to either radius or share based geospatial proximity queries
(find all document that are 20km from given lat,lng)
I would also at times be doing geo queries bonded with anot
Hello Mikhail
Thank you for the fast reply, please find my answers inline.
On Tue, Jan 3, 2012 at 11:00 PM, Mikhail Khludnev <
mkhlud...@griddynamics.com> wrote:
> Hello,
>
> Please find my thoughts below.
>
> On Wed, Jan 4, 2012 at 12:39 AM, Maxim Veksler wrote:
> &
On Tue, Jan 17, 2012 at 3:13 AM, Erick Erickson wrote:
> I don't see why not. I'm assuming a *nix system here so when Solr
> updated an index, any deleted files would hang around.
>
> But I have to ask why bother with the Embedded server in the
> first place? You already have a Solr instance up an
Hello,
I'm querying with bbox which should be faster then geodist, my queries are
looking like this:
http://localhost:8983/solr/select?indent=true&fq={!bbox}&sfield=loc&pt=39.738548,-73.130322&d=100&sort=geodist()%20asc&q=trafficRouteId:235
the trouble is, that with bbox solr does not return the
I tried.
Being new to Solr query language I'm not sure how to form the search terms
to combine all of this with the score.
> what do you get on this case? pls provide, logs, exception, and debug
> response.
>
> Thanks
>
>
> On Tue, Jan 17, 2012 at 10:06 PM, Maxim Veksler
hail Khludnev <
mkhlud...@griddynamics.com> wrote:
> Can you try to specify two fqs, geodist as a function query, sort by score?
>
>
> fq={!bbox}&.&sort=score%20asc&fq=trafficRouteId:235&q={!func}geodist()&fl=*,score
>
> On Wed, Jan 18, 2012 at 4:46
I'm planning on having 1 Master and multiple slaves (cloud based, slaves
are going up / down randomly).
The slaves should be constantly available, meaning searching performance
should optimally not be affected by the updates at all.
It's unclear to me how the Cluster based replication works, does
ll cause you to merge and ship the whole index rather than just
> the relevant portions when you replicate.
> >
> > The change on our slaves in terms of IO and CPU as well as RAM was
> marked.
> >
> > Andrew
> >
> > Sent on the run.
> >
> > On 23/
