Yeah, it's currently just for the update side of things.  But this issue is 
open <https://issues.apache.org/jira/browse/SOLR-3669> and assigned to me, for 
one of these days.  I set it for my 5.0 radar.  Certainly anyone that wants to 
make this happen sooner than I maybe will possibly hopefully one week will 
delve into, go for it!

        Erik

p.s. [infomercial] We do have update-side scripting (JavaScript) and business 
rules (via Drools) capabilities in our LucidWorks Search platform* 
<http://www.lucidworks.com/products/lucidworks-search> with the update-side 
scripting running in the connector framework by design rather than on the Solr 
side of things to allow it to scale in a separate tier.

On Jun 3, 2013, at 14:31 , Achim Domma wrote:

> Looks interesting, but it's just for the UpdateHandler. Right? Does a similar 
> handler for searching already exist?
> 
> Achim
> 
> Am 03.06.2013 um 17:22 schrieb Jack Krupansky:
> 
>> Check out the support for external scripting of update request processors:
>> 
>> http://lucene.apache.org/solr/4_3_0/solr-core/org/apache/solr/update/processor/StatelessScriptUpdateProcessorFactory.html
>> 
>> Are there any of your requirements that that doesn't address?
>> 
>> -- Jack Krupansky
>> 
>> -----Original Message----- From: Achim Domma
>> Sent: Monday, June 03, 2013 3:07 AM
>> To: solr-user@lucene.apache.org
>> Subject: Solr + Groovy
>> 
>> Hi,
>> 
>> I have some query building and result processing code, which is currently 
>> running as "normal" Solr client outside of Solr. I think it would make a lot 
>> of sense to move parts of this code into a custom SearchHandler or 
>> SearchComponent. Because I'm not a big fan of the Java language, I would 
>> like to use Groovy.
>> 
>> Searching the web I got the impression that "Solr + alternative JVM 
>> languages" is not a very common topic. So before starting my project, I 
>> would like to know: Is there a well known good reason not to use Groovy (or 
>> Clojure, Scala, ...) for implementing custom Solr code?
>> 
>> kind regards,
>> Achim= 
> 

Reply via email to