[jira] [Commented] (SOLR-5005) JavaScriptRequestHandler

["Noble Paul (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798081#comment-13798081 ] 

Noble Paul commented on SOLR-5005:
----------------------------------

Thanks [~dsmiley]
I'm not sure we should support many languages now. I know it is easy and tempting. But i shudder at the thought of someone using some esoteric JVM language which I'll find difficult to support. I wish to keep the option limited to 1 or 2 languages and extending the list as and when there is a need. 

yes.
The Docs.java should be a generic component to stream docs from a ResultContext. It can live as a separate utility

I somehow fee that the DSL is kind of required for completeness. People should have a standard way of doing standard operations and the DSL helps in that. Once the JS thing becomes popular we as people who support users would like to see standard code. But it makes sense to keep it a separate issue


> JavaScriptRequestHandler
> ------------------------
>
>                 Key: SOLR-5005
>                 URL: https://issues.apache.org/jira/browse/SOLR-5005
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: David Smiley
>            Assignee: Noble Paul
>         Attachments: patch, SOLR-5005.patch, SOLR-5005.patch, SOLR-5005.patch, SOLR-5005_ScriptRequestHandler_take3.patch
>
>
> A user customizable script based request handler would be very useful.  It's inspired from the ScriptUpdateRequestProcessor, but on the search end. A user could write a script that submits searches to Solr (in-VM) and can react to the results of one search before making another that is formulated dynamically.  And it can assemble the response data, potentially reducing both the latency and data that would move over the wire if this feature didn't exist.  It could also be used to easily add a user-specifiable search API at the Solr server with request parameters governed by what the user wants to advertise -- especially useful within enterprises.  And, it could be used to enforce security requirements on allowable parameter valuables to Solr, so a javascript based Solr client could be allowed to talk to only a script based request handler which enforces the rules.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org