Description
If index data is stored in the repository (for example under jcr:system/oak:indexes), then each change in the content might result in one or multiple changed in the affected indexes.
Observation events should only be created for content changes, not for index changes.
Attachments
Issue Links
- is related to
-
OAK-182 Support for "invisible" internal content
- Closed