Due to CONFSERVER-52489, after restoring Confluence from a backup, Content properties are no longer indexed in Lucene. This completely breaks our plugin's search behavior.
Since it doesn't look like the Issue is going to be resolved any time soon - Is there a way to programmatically run a reindex for Content properties in Confluence? (Or in other words, re-apply all Extractors, since that's the way Content property indexing is implemented).
Inject ConfluenceIndexer and use the index/reIndex methods to add the Searchables that you want to reindex.
Hi Christoph,
Unfortunately I cannot provide a timeline for when this issue will be resolved by our development team. I noticed you commented on the ticket - this is good as it will help provide more visibility to our product team on how this is impacting you and other users.
You posed a great question which might be better posed in our Developers' Community which is more geared toward development questions. Please try posting this same question at the link below to see if any other developers have some insight for you:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.