Mike, I've applied the patch as of a June-dated trunk. There were some trivial conflicts, but mostly-easy to apply. It has been in production for a couple months with no major hiccups so far :).
Justin "Smiley, David W." <dsmi...@mitre.org> writes: > Hi Mike. > > I have hopes that LSP will be ready in time for Solr 4. It's usable now with > the understanding that it's still fairly early and so there are bound to be > bugs. I've been focusing a lot on testing lately. You could try applying > SOLR-2155 but I think there was some Lucene/Solr code re-organization > regarding the ValueSource API. It shouldn't be hard to update. I don't think > JTeam's plugin handles multi-value but I could be wrong (Chris Male will be > sure to jump in and correct me if so). QBase/Metacarta has a Solr plugin > I've used indirectly through a packaged deal with their products > http://www.metacarta.com/products-overview.htm I have no idea if you can get > it stand-alone. As of a few months ago, it was based on a version of Solr > trunk from March 2010 and they have yet to update it. > > ~ David Smiley > > On Aug 29, 2011, at 2:27 PM, Mike Austin wrote: > >> Besides the full integration into solr for this, would you recommend any >> third party solr plugins such as " >> http://www.jteam.nl/products/spatialsolrplugin.html", or others? >> >> I can understand that spacial features can get complex and there could be >> many use cases, but this seems like a "basic" feature that you would use >> with a standard set of spacial features like what is in solr4 now. >> >> Thanks, >> Mike >> >> On Mon, Aug 29, 2011 at 12:38 PM, Darren Govoni <dar...@ontrenet.com> wrote: >> >>> It doesn't. >>> >>> >>> On 08/29/2011 01:37 PM, Mike Austin wrote: >>> >>>> I've been trying to follow the progress of this and I'm not sure what the >>>> current status is. Can someone update me on what is currently in Solr4 >>>> and >>>> does it support multi-valued location in a single document? I saw that >>>> SOLR-2155 was not included and is now lucene-spatial-playground. >>>> >>>> Thanks, >>>> Mike >>>> >>>> >>>