Can you just generate a fake data set for testing? There are numerous
libraries that create fake names, phone numbers, etc that you can use to
create mock data. Faker is one we have used in sensitive situations
https://github.com/joke2k/faker
I think this is going to be a better long-term solutio
Or you could also apply XSL to returned records:
https://wiki.apache.org/solr/XsltResponseWriter
On Thu, Oct 8, 2015 at 5:06 PM, Uwe Reh wrote:
> Hi,
>
> my suggestions are probably to simple, because they are not a real
> protection of privacy. But maybe one fits to your needs.
>
> Most simple:
Hi,
my suggestions are probably to simple, because they are not a real
protection of privacy. But maybe one fits to your needs.
Most simple:
Declare your 'hidden' fields just as "indexed=true stored=false", the
data will be used for searching, but the fields are not listed in the
query respo
trying to avoid re-ingesting the data.
>
> Thanks,
> Magesh
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Wednesday, October 07, 2015 9:26 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Scramble data
>
> Prob
: Re: Scramble data
Probably sanitize the data on the front end? Something simple like put
"REDACTED" for all of the customer-sensitive fields.
You might also write a DocTransformer plugin, all you have to do is implement
subclass DocTransformer and override one very simple "tr
Probably sanitize the data on the front end? Something simple like put
"REDACTED" for all of the customer-sensitive fields.
You might also write a DocTransformer plugin, all you have to do is
implement subclass DocTransformer and override one
very simple "transform" method,
Best,
Erick
On Wed, O
