That is the solution we had to go with as well.A feature request was made to have the runmode configurations for the replication agents match the runmode configurations for everything else. That ticket is GRANITE-14360.  I was told that the feature wouldn't even be considered until at least 6.4. If ...

There really aren't all that many replication configurations. It's just multiple sets, like "test", "prod", "staging", "preview", etc. So each set has its own specific publishers, flush agents, etc. We could just keep all the configurations separate and know that we need to install the staging repli...

There seems to be some inconsistency between how run modes are handled by the replication agent configuration and by other configurations in AEM.For reference, i am using AEM 6.2, com.adobe.granite.replication.core:6.0.14At issue here is the fact that when multiple run modes are appended to a replic...

Question 1 -The issue I face with manipulating the cost is that now the index (with its cost manipulated) is sometimes used when its the poorer choice; it ends up just reversing the problem: queries that were performing poorly because they weren't using this index now perform well, but other queries...

I will break this question down into two parts because I think they are probably related.The first relates to what seems like improper index selection, the second pertains to optimal configuration of indexes. In AEM most of the queries we do are based on @sling:resourceType, typically with some seco...