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...

I'm attempting to upgrade to the latest SDK and I'm getting an error saying that Geronimo and the SDK are both trying to export the same version of the directive `javax.json`. I've never seen this before and it's unclear why simply upgrading the SDK would cause this.  [INFO] BUILD FAILURE [INFO] ---...

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. 

Interesting. Will this fall back to a different index if it doesn't hit with that index? 

Thanks for the reply. I asked this of @aanchal-sikka , but I'm curious if you have some insight as well. Currently since the query in question is using damAssetLucene, if we begin adding a custom index or indexes that refer to properties of content fragments that will mean that index won't be useful...