Yes. This was very helpful. 

Kostiantyn, This did work for us. It's unclear what AEM does with that index as we can still see it in oak:index, but it stops being used. Did you see it eventually cleaned up? Preston

Konstantyn, Something I'm unclear on here is if there's any way to completely remove this customization or if it has to be basically a copy of the originally fragments-10. Do you know?Preston

Adobe's documentation on custom indexes indicates that they expect you would use custom tags. I agree that the custom queryPaths and includedPaths might be a case for a fully custom index. If we were to do that, would we simply create a "dummy" version of the existing custom index? If that didn't wo...

<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:oak="http://jackrabbit.apache.org/oak/ns/1.0" xmlns:dam="http://www.day.com/dam/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" xmlns:rep="internal" jcr:primaryType="oak:QueryIndexDefinition" async="[...

It's not. We based it on "fragments" and it's literally called "fragments-10-custom-2" (numbers vary, obviously). 

This is a custom index meant for Content Fragments, though, and as far as we could tell the underlying search was using the "fragments" index if we didn't create our own index. 

We have a custom index we created to address some specific needs for searching Content Fragments. We noticed a side effect where the Content Fragment browser stopped showing fragments on the initial screen.  Digging in to Splunk when the browser attempts to load this screen it makes the following OO...

One more question since you've been so helpful. Is there a way to tell how out of the box indexes are used? We're trying to figure out how to pick the right index to customize and we think "fragments" is the most helpful to us, but we can't find any documentation on these OOTB indexes and what their...

Okay. Thanks. Thanks for all of your help, btw.