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

Thanks for the reply and especially for clearing up the different parts of the index. That makes sense. I'll ask Adobe about the proper way to format this.  As an aside, we dug into this more today and it appears that we already have a custom index for Media Assets. Is there a way that you're aware ...

I think the part that's throwing me is this from that documentation.  "Introducing new indexes on the dam:Asset nodetype (particularly fulltext indexes) is strongly discouraged as these can conflict with OOTB product features leading to functional and performance issues. In general, adding additiona...

We are experiencing slowdown while performing Query Builder queries against content fragments. While digging into this, I believe I discovered that it has to do with a field in the content fragments not being indexed. I added a custom index locally and the query improved from 200 ms to 2 ms. Accordi...

Thanks. To be clear, this works great for me with the Content Fragment API. 

We see the issue solely on author as well. So working locally I will see the correct, updated field in jcr:content/data/master, but not in jcr:content/indexedData/master if I'm using the Sling API to update the fragment. This code is running in an implementation of the PreProcessor interface, so the...

The team I'm on is running into a strange issue when editing content fragments in Java. A common pattern we use based on years of working with AEM is to adapt a resource as a ModifiableValueMap in Java code and then edit one of the values of that ModifiableValueMap, commit the resourceResolver, thus...

That's good news and a good tip on setting up logging. Good luck with debugging this further.