Like Erick said, would something like using replace function on individual sensitive fields in fl param would work? replacing to something REDACTED etc.
On Thu, Oct 8, 2015 at 2:58 PM, Tarala, Magesh <mtar...@bh.com> wrote: > I already have the data ingested and it takes several days to do that. I > was 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 > > 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, Oct 7, 2015 at 5:09 PM, Tarala, Magesh <mtar...@bh.com> wrote: > > Folks, > > I have a strange question. We have a Solr implementation that we would > like to demo to external customers. But we don't want to display the real > data, which contains our customer information and so is sensitive data. > What's the best way to scramble the data of the Solr Query results? By best > I mean the simplest way with least amount of work. BTW, we have a .NET > front end application. > > > > Thanks, > > Magesh > > > > > > >
