What does the async state "temp-async" indicate in a merged custom index? Help finding documentation on this.

[Preston]

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, so I'm hoping someone here can help. 

[Saravanan_Dharmaraj]

@Preston  Please check the below documentation, you can set async="async" if it wants to run as background thread

• The async property which must be set to async. This sends the index update process to a background thread.

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/depl...

[Preston]

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

[Tethich]

Hi @Preston 

I believe your answer is here: https://issues.apache.org/jira/browse/OAK-10265

There is a small comment that mentions the temp-async also in the Apache Oak implementation: https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak...

Also if you need to understand more about indexes, this one is useful as well: https://lists.apache.org/thread/q6kjgdc8fmx3f7tlx4dzvnnf93mmvttp

[Preston]

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. 

[Preston]

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