Deployment pipeline is failing while deploying oak index changes on environment

[anurag_dang]

We are using AEMaaCS. We have made some oak index changes to incorporate new custom filters as per business requirements. We deployed the feature branch (with oak index changes) to local aem instance, the code is successfully deployed with no errors. However, when deploying code on cloud instance then the pipeline is failing.

When the last custom changes were made to oak index that time we made damAssetLucene-9-custom-2. However when this time we wanted to make custom changes, we observed that damAssetLucene-10 and damAsset-Lucene-10-custom-1 were created from backend(may be by Adobe during new release). So we created the new custom index named as damAssetLucene-10-custom-2 by copying the custom-1 index and adding the new property "collateralType" to it. We doubt that we are missing something in the new configuration of Lucene-10.

We are using below tika configuration:

<tika jcr:primaryType="nt:unstructured"> <config.xml jcr:primaryType="nt:file" > <jcr:content jcr:primaryType="nt:unstructured" jcr:data=":blobId:PHByb3BlcnRpZXM+CiAgPGRldGVjdG9ycz4KICAgIDxkZXRlY3RvciBjbGFzcz0ib3JnLmFwYWNoZS50aWthLmRldGVjdC5UeXBlRGV0ZWN0b3IiLz4KICA8L2RldGVjdG9ycz4KICA8cGFyc2Vycz4KICAgIDxwYXJzZXIgY2xhc3M9Im9yZy5hcGFjaGUudGlrYS5wYXJzZXIuRGVmYXVsdFBhcnNlciI+CiAgICAgIDxtaW1lPnRleHQvcGxhaW48L21pbWU+CiAgICA8L3BhcnNlcj4KICA8L3BhcnNlcnM+CiAgPHNlcnZpY2UtbG9hZGVyIGluaXRpYWxpemFibGVQcm9ibGVtSGFuZGxlcj0iaWdub3JlIiBkeW5hbWljPSJ0cnVlIi8+CjwvcHJvcGVydGllcz4=" jcr:mimeType="text/xml"/> </config.xml> </tika>

The logs show below exception:

java.lang.NullPointerException: Cannot invoke "org.apache.jackrabbit.oak.api.Blob.getNewStream()" because the return value of "org.apache.jackrabbit.oak.plugins.index.search.util.ConfigUtil.getBlob(org.apache.jackrabbit.oak.spi.state.NodeState, String)" is null

Looking out for support on this.

Thanks.

[aanchal-sikka]

@anurag_dang 

damAsset-Lucene-10-custom-1 might have been created by merging damAssetLucene-9-custom-2 with damAssetLucene-10. It might have been done automatically during upgrade.

Can you please try following?

- Create damAsset-Lucene-10-custom-2 from damAsset-Lucene-10 and then add your changes to it

This will rule-out if the issue is with auto-merge of indexes.

Please check the logs of the Upgrade pipeline, it might suggest the origin of damAsset-Lucene-10-custom-1. If no details are available, please raise an Adobe ticket, maybe they can help with more details.