so, in order to avoid the main problem (history update), is it a solution to enhance the xwiki.store.versioning setting of xwiki.cfg to allow a list of pages that are exceptions from the rule?
Then, on a specific setup, one would be able to disable history alltogether for the pages that are large groups. Those groups will not have history anymore, but we would not have a performance issue anymore. In my view, this workaround would also be more merge-able in an LTS / bugfix version, so we could have it earlier. Also, it doesn't look like a complex logic or risky change - we already support not having history saved, we just need to make the check page by page rather than global.
Vincent MassolThomas Mortagne WDYT? Can I create the improvement for the enhancement of the xwiki.store.versioning setting in order to have a quick workaround for this?
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.