Well, Solr just bundled a set of Hadoop jars that does not actually contribute anything to Solr itself (not really integrated, etc). So, I am not sure how the "may not want" process happened there. Would be nice to have one actually, because there is a slow building wave of external components for Solr which are completely not discoverable by the Solr community at large.
So, I would love us to (re-?)start the serious discussion on the plugin model for Solr. Probably on the dev list. I would even commit to building an initial package discovery/search website if the dev-list powers would agree on how that mechanism (package/plugins/downloads) should look like. ElasticSearch is very obviously benefiting from having a plugin system. Solr's kitchen-sync approach worked when it was the only one. But with increased speed of releases and the growing packages, it is becoming very noticeably pudgy. It even had to be excused during the Solr vs. ElasticSearch presentation at the BerlinBuzz a couple of days ago. Regards, Alex. P.s. Regarding the specific issue, I know of another Redis plugin. Not sure how relevant or useful it is, but at least it exists: https://github.com/dfdeshom/solr-redis-cache Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Thu, May 29, 2014 at 2:50 AM, Otis Gospodnetic <otis.gospodne...@gmail.com> wrote: > Hi, > > I think the question is not really "how" to do it - that's clear - > http://wiki.apache.org/solr/HowToContribute > > The question is really about whether something like this would be of > interest to Solr community, whether it is likely it would be accepted into > Solr core or contrib, or whether, perhaps because of potentially unwanted > dependency on Redis, Solr dev community might not want this in Solr and > this might be better done outside Solr. > > Not sure what the answer is..... maybe active Solr developers can chime in > here? Or maybe dev list is a better place to ask? > > Otis > -- > Performance Monitoring * Log Analytics * Search Analytics > Solr & Elasticsearch Support * http://sematext.com/ > > > On Wed, May 28, 2014 at 2:03 PM, Alan Woodward <a...@flax.co.uk> wrote: > >> Hi Pawel, >> >> The easiest thing to do is to open a JIRA ticket on the Solr project, >> here: https://issues.apache.org/jira/browse/SOLR, and attach your patch. >> >> Alan Woodward >> www.flax.co.uk >> >> >> On 28 May 2014, at 16:50, Pawel Rog wrote: >> >> > Hi, >> > I need QParserPlugin that will use Redis as a backend to prepare filter >> > queries. There are several data structures available in Redis (hash, set, >> > etc.). From some reasons I cannot fetch data from redis data structures, >> > build and send big requests from application. That's why I want to build >> > that filters on backend (Solr) side. >> > >> > I'm wondering what do I have to do to contribute QParserPlugin into Solr >> > repository. Can you suggest me a way (in a few steps) to publish it in >> Solr >> > repository, probably as a contrib? >> > >> > -- >> > Paweł Róg >> >>
