lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kumaran Ramasubramanian <>
Subject Encryption at lucene index
Date Mon, 07 Aug 2017 06:30:52 GMT
Hi All,

After looking at all below discussions, i have one doubt which may be silly
or novice but i want to throw this to lucene user list.

if we have encryption layer included in our analyzer's flow of filters like
EncryptionFilter to control field-level encryption. what are the
consequences ? am i missing anything basic?

Thanks in advance..

Related links: : AES Encrypted Directory
- in lucene 3.x :  Codec for index-level
encryption - at codec level, to have control on which column / field have
 personal identifiable information

A decent encrypting algorithm will not produce, say, the same first portion
> for two tokens that start with the same letters. So wildcard searches won't
> work. Consider "runs", "running", "runner". A search on "run*" would be
> expected to match all three, but wouldn't unless the encryption were so
> trivial as to be useless. Similar issues arise with sorting. "More Like
> This" would be unreliable. There are many other features of a robust search
> engine that would be impacted, and an index with encrypted terms would be
> useful for only exact matches, which usually results in a poor search
> experience.

Kumaran R

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message