Custom Indexes in AEMaaCS not updating in build pipeline

[Rohan_Garg]

@aanchal-sikka - Thanks for your response!

No there were no updates other than the one which we wanted to originally deploy.

Using the same name without a version number has apparently led to this issue. The reindexing was not complete even after 6h post deployment which was weird.

We tried the below fix (without empty package installation) which worked as per Index Management - 

The <indexName>-custom-<customerVersionNumber> is needed for AEM as a Cloud Service to mark it as a replacement for an existing index.

[arunpatidar · Accepted solution]

Hi @Rohan_Garg 
In AEMaaCS The indexing happened even before the deployment, so if you don't have index with new version, the index changes will not be reflecting 

[Rohan_Garg]

Hi @arunpatidar, this actually happened for only 3/10 indexes we updated.

For the others the new index definition was available without the new version specification as well. But yes new version should always be added to the index. Thanks!

[aanchal-sikka]

Hello @Rohan_Garg 

Requesting you to please select the correct answer since the issue is resolved. It would help the consultants filter the threads with solutions.

[Rohan_Garg]

I tried but I didn't get the option to mark it as correct one - not sure why!

@kautuk_sahni - Can you please help here?

[arunpatidar]

@Rohan_Garg 

you can't mark discussion as correct answer, I think you have opened as discussion instead of question.