chema changes on my part. Something like that, or slightly
>> modified version of that, would handle user defined schemas.
>> --
>> View this message in context:
>> http://lucene.472066.n3.nabble.com/Private-data-within-SOLR-Schema-tp1376174p1376355.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>
>
>
> --
> Lance Norskog
> goks...@gmail.com
>
--
Lance Norskog
goks...@gmail.com
ed schemas.
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Private-data-within-SOLR-Schema-tp1376174p1376355.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
Lance Norskog
goks...@gmail.com
modified version of that, would handle user defined schemas.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Private-data-within-SOLR-Schema-tp1376174p1376355.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi all,
I'm wondering how to handle following scenario:
There is a pool of data which can be searched by all users via a web
interface. Now some users would like to add own documents, or private fields
to existing documents which shall not be accessable by others.
Concerning private fields
.. I
