To put a fine point on this. That Oak issue is from 2023. That should be repaired in AEMaaCS, right? 

Thanks. That's the best I could do in terms of documentation as well. I was hoping to find some official Adobe documentation that discussed this state and how to get an index to exit this state. 

Right. So what causes it to get set to "temp-async" instead?

We have a customization of an OOTB index that after our last deployment was merged and the "async" attribute was set to "temp-async".   jcr:primaryType="oak:QueryIndexDefinition" async="temp-async" async-previous="[async,nrt]" I'm having trouble finding documentation on this, ...

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