Hi Guy,
I needed to unsub this mailing account from @lucene.apache.org
I have sent email to unsubscribe mailing address. But it didn't work
Any idea.
Much appreciated
From: Khurram Shehzad
Sent: Monday, August 7, 2017 8:29 AM
To: java-user-unsubscr...@luc
How about Solr's exists function query? How does it work?function queries are
now part of Lucene (org.apache.lucene.queries.function.) right?
Ahmet
On Sunday, July 16, 2017, 11:19:40 AM GMT+3, Trejkaz
wrote:
On Sat, Jul 15, 2017 at 8:12 PM, Uwe Schindler wrote:
> That is the "Solr" answer.
Hi,
I am traversing posting list of a given term/word using the following code. I
am accessing/processing term frequency and document length.
Term term = new Term(field, word);
PostingsEnum postingsEnum = MultiFields.getTermDocsEnum(reader, field,
term.bytes());
if (postingsEnum == null) return
Harry Ochiai (Hitachi) has some index encryption solution,
https://www.slideshare.net/maggon/securing-solr-search-data-in-the-cloud
I think it is proprietary, but I'm not sure. Maybe more googling might help
find the exact page where his solution is described.
On Mon, Aug 7, 2017 at 9:59 PM, Kumar
Hi Erick, i want to encrypt some fields of an document which has personal
identifiable information ( both indexed and stored data)... for eg: email,
mobilenumber etc.. i am able to find LUCENE-6966 alone while googling it..
any related pointers in solr or latest lucene version?
-
-
Kumaran R
O
No, since you haven't defined what you want to encrypt, what your
requirements are, what you hope to get out of "encryption" etc.
Put the index on an encrypting filesystem and forget about it if you
possibly can, because anything else is a significant amount of work.
To encrypt the searchable toke
Hi Erick,
Thanks for the information. Any pointers about encryption options in
solr?
--
Kumaran R
On Mon, Aug 7, 2017 at 9:17 PM, Erick Erickson
wrote:
> Encryption in Solr has a bunch of ramifications. Do you care about
>
> - encryption at rest or in memory?
> - encrypting the _searcha
Encryption in Solr has a bunch of ramifications. Do you care about
- encryption at rest or in memory?
- encrypting the _searchable_ tokens?
- encrypting the searchable tokens per-user?
- encrypting the stored data (which a filter won't do BTW).
It's actually a fairly complex topic the discussion
