> When making a query these fields should be required. Is it possible to
configure handlers on the solr server so that these field are required whith
each type of query? So for adding documents, deleting and querying?
have a look at 'invariants' (and 'appends') in the example solrconfig.
They can
ene.apache.org
Sent: Tue, November 23, 2010 6:45:12 AM
Subject: Re: SOLR and secure content
The setup of multiple cores is a good option, thanks for the advice.
I agree the "required" field should be in the application layer, but i also
think some "error" handling should co
Dennis,
We will we serving the content to de indexed websites. As i wrote we will be
looking into setting up different cores, 1 core for each website. This wil
make sure the content is sperated for each individual indexed website.
The so called "error" handling is only needed, in case of bad pro
ene.apache.org
Sent: Tue, November 23, 2010 6:45:12 AM
Subject: Re: SOLR and secure content
The setup of multiple cores is a good option, thanks for the advice.
I agree the "required" field should be in the application layer, but i also
think some "error" handling should co
lf.
from 'http://blogs.techrepublic.com.com/security/?p=4501&tag=nl.e036'
EARTH has a Right To Life,
otherwise we all die.
- Original Message
From: Jos Janssen
To: solr-user@lucene.apache.org
Sent: Tue, November 23, 2010 4:35:09 AM
Subject: Re: SOLR and secure content
Hi every
The setup of multiple cores is a good option, thanks for the advice.
I agree the "required" field should be in the application layer, but i also
think some "error" handling should come from the Solr server to prevent
incorrect usage. If i only knew how to do this for each request.
Regards,
Jos
Sounds like a good plan. I'd probably also set multiple cores for each
website. This could give you more accurate results scoring.
Good question about the "required" configuration option.. any input?
Although on the other hand, this is a rule which seems to better fit in your
application's Validat
Hi everyone,
This is how we think we should set it up.
Situation:
- Multiple websites indexed on 1 solr server
- Results should be seperated for each website
- Search results should be filtered on group access
Solution i think is possible with solr:
- Solr server should only be accesed through
On Tue, Nov 23, 2010 at 5:26 AM, Peter Sturge wrote:
> Document-level access control can be a real 'can of worms', and it can
> be worthwhile spending a bit of time defining exactly what you need.
I agree, "document-level access control" is an anti-feature.
You can't just give someone access to
Yes, as mentioned in the above link, there's SOLR-1872 for maintaing
your own document-level access control. Also, if you have access to
the file system documents and want to use their existing ACL, have a
look at SOLR-1834.
Document-level access control can be a real 'can of worms', and it can
be
maybe this older thread on Modeling Access Control might help:
http://lucene.472066.n3.nabble.com/Modelling-Access-Control-td1756817.html#a1761482
Regards,
-- Savvas
On 22 November 2010 18:53, Jos Janssen wrote:
>
> Hi,
>
> We plan to make an application layer in PHP which will communicate to
Hi,
We plan to make an application layer in PHP which will communicate to the
solr server.
Direct calls will only be made for administration purposes only.
regards,
jos
--
View this message in context:
http://lucene.472066.n3.nabble.com/SOLR-and-secure-content-tp1945028p1947970.html
Sent fro
Hi,
Could you elaborate a bit more on how you access Solr? are you making direct
Solr calls or is the communication directed through an application layer?
On 22 November 2010 11:05, Jos Janssen wrote:
>
> Hi,
>
> We are currently investigating how to setup a correct solr server for our
> goals.
13 matches
Mail list logo
