Currently search ignores the typesOnly and attributes settings in search requests, and always returns the whole entry.
Implementing this would require creating reduced SearchResultEntry responses with attributes or values removed. Note that we still need the initial full SearchResultEntry for filtering correctly. The response could be created either by deleting the attributes/values from the full entry, or by creating new entries with the attributes/values omitted. Note if we are caching full entries created from user/group scans, it means we need to create new entries for the response. This would probably also solve the problem of avoiding problems with in-flight responses during cache updates.
Currently search ignores the typesOnly and attributes settings in search requests, and always returns the whole entry.
Implementing this would require creating reduced SearchResultEntry responses with attributes or values removed. Note that we still need the initial full SearchResultEntry for filtering correctly. The response could be created either by deleting the attributes/values from the full entry, or by creating new entries with the attributes/values omitted. Note if we are caching full entries created from user/group scans, it means we need to create new entries for the response. This would probably also solve the problem of avoiding problems with in-flight responses during cache updates.