>> Otis
>> --
>> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>>
>>
>>
>> - Original Message
>>> From: pof
>>> To: solr-user@lucene.apache.org
>>> Sent: Thursday, June 25, 2009 7:40:12 PM
>>> Subje
side even if the URL is
> know.
>
> Otis
> --
> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>
>
>
> - Original Message
>> From: pof
>> To: solr-user@lucene.apache.org
>> Sent: Thursday, June 25, 2009 7:40:12 PM
>> Subj
Nutch
- Original Message
> From: pof
> To: solr-user@lucene.apache.org
> Sent: Thursday, June 25, 2009 7:40:12 PM
> Subject: Re: Solr document security
>
>
> Thats what I was going to do originally, however what is stopping a user from
> simply running a search throu
I speak for myself, not my employer. Contents may be hot. Slippery when
> wet.
> Reading disclaimers makes you go blind. Writing them is worse. You have
> been
> Warned.
>
>
--
View this message in context:
http://www.nabble.com/Solr-document-security-tp24197620p24212752.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Wed, 24 Jun 2009 23:20:26 -0700 (PDT)
pof wrote:
>
> Hi, I am wanting to add document-level security that works as following: An
> external process makes a query to the index, depending on their security
> allowences based of a login id a list of hits are returned minus any the
> user are mea
/Solr-document-security-tp24197620p24197620.html
Sent from the Solr - User mailing list archive at Nabble.com.
