Hi Yonik,
I just created a JIRA issue: https://issues.apache.org/jira/browse/SOLR-2642
Thomas
On Fri, Jul 8, 2011 at 4:00 PM, Yonik Seeley yo...@lucidimagination.comwrote:
On Fri, Jul 8, 2011 at 4:11 AM, Thomas Heigl tho...@umschalt.com wrote:
How should I proceed with this problem? Should
How should I proceed with this problem? Should I create a JIRA issue or
should I cross-post on the dev mailing list? Any suggestions?
Cheers,
Thomas
On Wed, Jul 6, 2011 at 9:49 AM, Thomas Heigl tho...@umschalt.com wrote:
My query in the unit test looks like this:
q=*:*fq=_query_:{!geofilt
On Fri, Jul 8, 2011 at 4:11 AM, Thomas Heigl tho...@umschalt.com wrote:
How should I proceed with this problem? Should I create a JIRA issue or
should I cross-post on the dev mailing list? Any suggestions?
Yes, this definitely sounds like a bug in the 3.3 grouping (looks like
it forgets to
My query in the unit test looks like this:
q=*:*fq=_query_:{!geofilt sfield=user.location_p pt=48.20927,16.3728
d=50.0} OR _query_:{!geofilt sfield=location_p pt=48.20927,16.3728
Did you add: fq={!geofilt} ??
On 7/3/11 11:14 AM, Thomas Heigl tho...@umschalt.com wrote:
Hello,
I just tried up(down?)grading our current Solr 4.0 trunk setup to Solr
3.3.0
as result grouping was the only reason for us to stay with the trunk.
Everything worked like a charm except for one of
I'm pretty sure my original query contained a distance filter as well. Do I
absolutely need to filter by distance in order to sort my results by it?
I'll write another unit test including a distance filter as soon as I get a
chance.
Cheers,
Thomas
On Tue, Jul 5, 2011 at 9:04 AM, Bill Bell
Hello,
I just tried up(down?)grading our current Solr 4.0 trunk setup to Solr 3.3.0
as result grouping was the only reason for us to stay with the trunk.
Everything worked like a charm except for one of our queries, where we group
results by the owning user and sort by distance.
A simplified
