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: https://issues.apache.org/jira/browse/LUCENE-2228 : AES Encrypted Directory - in lucene 3.x https://issues.apache.org/jira/browse/LUCENE-6966 : Codec for index-level encryption - at codec level, to have control on which column / field have personal identifiable information https://security.stackexchange.com/questions/111153/is-a-lucene-search-index-effectively-a-backdoor-for-field-level-encryption 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. https://stackoverflow.com/questions/36604551/adding-encryption-to-solr-lucene-indexes -- Kumaran R
