lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lee Carroll <>
Subject Re: custom request handler
Date Fri, 09 Nov 2012 13:39:49 GMT
Hi Amit

I did not do this via a servlet filter as I wanted the solr devs to be
concerned with solr config and keep them out of any concerns of the
container. By specifying declarative data in a request handler that would
be enough to produce a service uri for an application.

Or have  I missed a point ? We have several cores with several apps all
with different data query needs. Maybe 20 request handlers needed to
support this with active development on going. Basically I want it easy for
devs to create a specific request handler suited to their needs. I thought
a servletfilter developed and mainatined every time would be over kill.
Again though I may have missed a point / over emphasised a difficulty?

Are you saying my custom request handler is to tightly bound to solr? so
the parameters my apps talk is not de-coupled enough from solr?

Lee C

On 7 November 2012 19:49, Amit Nithian <> wrote:

> Why not do this in a ServletFilter? Alternatively, I'd just write a front
> end application servlet to do this so that you don't firewall your internal
> admins off from accessing the core Solr admin pages. I guess you could
> solve this using some form of security but I don't know this well enough.
> If I were to restrict access to certain parts of Solr, I'd do this outside
> of Solr itself and do this in a servlet or a filter, inspecting the
> parameters. It's easy to create a "modifiable" parameters class and
> populate that with acceptable parameters before the Solr filter operates on
> it.
> Amit

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message