On 11/12/13 5:20 PM, Shawn Heisey wrote:
> Ensure that all handler names start with a slash character, so they are
> things like "/query", "/select", and so on. Make sure that handleSelect
> is set to false on your requestDispatcher config. This is how Solr 4.x
> examples are set up already.
>
>
On 11/12/2013 6:13 AM, Christian Ramseyer wrote:
> So I'm worried about something that uses these URL paths, say
>
> https://reverse-proxy/mapping-to-solr/searchui_client?qt=update&;
> commit=true&stream.body=*:*
Ensure that all handler names start with a slash character, so they are
things like
On 11/12/13 1:51 PM, Erick Erickson wrote:
> When you mention velocity, you're talking about the stock Velocity Response
> Writer that comes with the example? Because if you're exposing the Solr
> http address to the world, accessing each others data is the least of your
> worries. To whit:
>
> ht
When you mention velocity, you're talking about the stock Velocity Response
Writer that comes with the example? Because if you're exposing the Solr
http address to the world, accessing each others data is the least of your
worries. To whit:
http://machine:8983/solr/collection/update?commit=true&st
Hi guys
I'm prototyping a multi-tenant search. I have various document sources and a
tenant can potentially access subsets of any source.
Also tenants have overlapping access to the sources, why I'm trying to do it in
a single core.
I'm doing this by labeling the source (origin, single value)
