[ https://issues.apache.org/jira/browse/OAK-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996262#comment-15996262 ]
Chetan Mehrotra commented on OAK-6165: -------------------------------------- bq. In the meantime, do we have any evidence that there's an actual problem with the current workaround? Test case? Benchmark? None so far. The issue is just to ensure that we are consistent wrt indexes created in MongoDocumentStore and RDBDocumentStore as performance problem related to indexes only surface in large setups. Hence was looking for all cases where there is index mismatch between RDB support such that we can properly plan for eventual migration and support in code [~mreutegg] Would queries related to _sdType would be more frequent now? Thoughts around having an index? > Create compound index on _sdType and _sdMaxRevTime (RDB) > -------------------------------------------------------- > > Key: OAK-6165 > URL: https://issues.apache.org/jira/browse/OAK-6165 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: rdbmk > Reporter: Chetan Mehrotra > Assignee: Julian Reschke > Fix For: 1.8 > > > Clone for OAK-6129 for RDB i.e. create index on OAK-6129on _sdType and > _sdMaxRevTime. This is required to run queries issued by the Revision GC > efficiently. -- This message was sent by Atlassian JIRA (v6.3.15#6346)