Support chained IndexReader wrappers for extensible custom features like Field Masking #130982
+85
−20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a flexible mechanism to chain multiple IndexReader wrappers inside Elasticsearch's security plugin. This allows custom extensions—such as field-level data masking (field desensitization)—to be implemented cleanly at the Lucene layer.
Elasticsearch natively supports FLS and DLS by wrapping Lucene DirectoryReader instances to filter unauthorized fields and documents per user roles. However, existing implementations have limited extensibility for other security-related features like field masking.
Adds a method to chain multiple CheckedFunction<DirectoryReader, DirectoryReader, IOException> wrappers that can be applied sequentially to the index reader.
Integrates this chaining mechanism into the security plugin’s index reader wrapping flow.
Provides a public API for SecurityExtension implementations to contribute custom reader wrappers, allowing third-party plugins to implement additional security or masking logic at the Lucene layer.
Ensures compatibility with existing DLS and FLS implementations.