r its distance score results. Kind of a
mess, I know.
~ David
From: Luis Cappa Banda [luisca...@gmail.com]
Sent: Tuesday, March 12, 2013 12:48 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr 4.1: problems with Spatial Search.
Hey, David.
How are you
Hey, David.
How are you? I did what you suggested and now works fine. However I hope
that those performance issues will be resolved soon and I hope I could help
some way: coding, testing, whatever. About cache warm up, I have setted up
some warm-up queries in solrconfig.xml that fills the cache. O
Rakudten wrote
> Hello again!
>
> Uhm, so if I have understood then if I´m writing/reading from the index at
> the same time (in other words, indexing operations are executing at the
> same that that other ones are querying) the performance goes down, isn´t
> it?
Committing is the problem (soft o
documents your search matched (aka
> "numFound"). If you're doing simultaneous committing then this approach is
> completely un-workable.
>
> ~ David
>
> From: "Rakudten [via Lucene]" <mailto:ml-node+s472066n4045273...@n3.nabble.com>>
> Date: Wedn
3...@n3.nabble.com>>
Date: Wednesday, March 6, 2013 11:48 AM
To: "Smiley, David W." mailto:dsmi...@mitre.org>>
Subject: Re: Solr 4.1: problems with Spatial Search.
I´ve doing some performance tests and I´ve noticed that with the new query
syntax that David told me to use the QT
neConstFunction.java:168)
>> > at
>> >
>> org.apache.solr.search.function.distance.HaversineConstFunction.access$200(HaversineConstFunction.java:47)
>> > at
>> >
>> org.apache.solr.search.function.distance.HaversineConstFunction$1.parse(Haversine
)
> > at
> >
> org.apache.solr.search.FunctionQParser.parseValueSource(FunctionQParser.java:352)
> > at org.apache.solr.search.FunctionQParser.parse(FunctionQParser.java:68)
> > at org.apache.solr.search.QParser.getQuery(QParser.java:142)
> > at org.apache.solr.search
s Cappa
>
>
> 2013/3/5 Chris Hostetter <
> hossman_lucene@
> >
>
>>
>> 1) which version of solr are you using?
>> 2) what is the field & fieldtype for "geolocation"
>> 2) can you try changing your query to "q={!func}geodist(
unction works at all?
>
>
>
> : Date: Tue, 5 Mar 2013 19:30:33 +0100
> : From: Luis Cappa Banda
> : Reply-To: solr-user@lucene.apache.org
> : To: solr-user@lucene.apache.org
> : Subject: Re: Solr 4.1: problems with Spatial Search.
> :
> : Without the sort it works perfect
a
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Re: Solr 4.1: problems with Spatial Search.
:
: Without the sort it works perfectly, and there are no more error messages,
: just the one I copy&pasted, :-(
: El 05/03/2013 19:05, "David Smiley (@MITRE.org)"
:
Without the sort it works perfectly, and there are no more error messages,
just the one I copy&pasted, :-(
El 05/03/2013 19:05, "David Smiley (@MITRE.org)"
escribió:
> Hmm; weird. It looks right. Does it work without the sort? -- i.e. does
> the
> filter work? Are there more interesting lookin
Hmm; weird. It looks right. Does it work without the sort? -- i.e. does the
filter work? Are there more interesting looking error messages output by
Solr?
Rakudten wrote
> Hello!
>
> I´m trying to sort by geodist() distance, but it seems that I can´t:
>
> *The query:*
>
> http://192.168.1.1
12 matches
Mail list logo