Sorting by multi-valued field

Hey all! In our system users can create recurring events and search for events starting on or after a given date. Searching and filtering of events works perfectly, but users expect the result set to be ordered by the next start time. For each event, we index a multi-valued date field containing

Re: Sorting by multi-valued field

Hey Guys, Thanks a lot for your input! But my interpretation of "the next" start time is that it wsa dependent on > the value of "NOW" when the query was executed (ie: some of the indexed > values may be in the past) in which case that approach wouldn't work. If the query was always a NOW query

Minimum HA Setup with SolrCloud

Hey all, I'm in the process of migrating a single Solr 4.0 instace to a SolrCloud setup for availability reasons. After studying the wiki page for SolrCloud I'm not sure what the absolute minimum setup is that would allow for one machine to go down. Would it be enough to have one shard with one

Re: Minimum HA Setup with SolrCloud

Thanks a lot guys! On Thu, Dec 6, 2012 at 4:22 PM, Markus Jelsma wrote: > > -Original message- > > From:Yonik Seeley > > Sent: Thu 06-Dec-2012 16:01 > > To: solr-user@lucene.apache.org > > Subject: Re: Minimum HA Setup with SolrCloud > > > > On Thu, Dec 6, 2012 at 9:56 AM, Markus Jelsma

Exception when using result grouping and sorting by geodist() with Solr 3.3

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 exam

Re: Exception when using result grouping and sorting by geodist() with Solr 3.3

Bill Bell wrote: > Did you add: fq={!geofilt} ?? > > On 7/3/11 11:14 AM, "Thomas Heigl" 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 sta

Re: Exception when using result grouping and sorting by geodist() with Solr 3.3

ield=user.uniqueId_s&sfield=user.location_p&pt=48.20927,16.3728&sort=geodist() > asc This works without a problem in my trunk build of Solr 4.0 from March 2011. I use the standard schema.xml packaged with the Solr distribution. Thomas On Tue, Jul 5, 2011 at 10:20 AM, Thomas H

Re: Exception when using result grouping and sorting by geodist() with Solr 3.3

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 wrote: > My query in the unit test looks like this: > > q=*:*&fq=_query_:&quo

Re: Exception when using result grouping and sorting by geodist() with Solr 3.3

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 wrote: > On Fri, Jul 8, 2011 at 4:11 AM, Thomas Heigl wrote: > > How should I proceed with this problem? Should I create a JIRA issue or >

Tuning caching of geofilt queries

Hey all, Our production system is heavily optimized for caching and nearly all parts of queries are satisfied by filter caches. The only filter that varies a lot from user to user is the location and distance. Currently we use the default location field type and index lat/long coordinates as we ge