Failed to create query: [nested] nested object under path [ddmFieldArray] is not of nested type

Issue

• When Liferay starts up and the user tries to fetch the home page where images are uploaded, the below errors are shown in the Liferay logs:
  

  {"error":{"root_cause":[{"type":"query_shard_exception","reason":"failed to create query: [nested] nested object under path [ddmFieldArray] is not of nested type","index_uuid":"xmym0ZbiQ4al2XNOAVKnUw","index":"liferay-20115"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"liferay-20115","node":"WdAACjoRSZ-mx6U_5gYPuQ","reason":{"type":"query_shard_exception","reason":"failed to create query: [nested] nested object under path [ddmFieldArray] is not of nested type","index_uuid":"xmym0ZbiQ4al2XNOAVKnUw","index":"liferay-20115","caused_by":{"type":"illegal_state_exception","reason":"[nested] nested object under path [ddmFieldArray] is not of nested type"}}}]},"status":400}

Environment

• Liferay Quarterly Release

Resolution

• Navigate to System Settings → Dynamic Data Mapping → Dynamic Data Mapping Indexer, select Enable Legacy Dynamic Data Mapping IndexFields and execute a full reindex.
• Possible root cause: The dynamic data mapping fields in Elasticsearch that start with ddm__keyword__ and ddm__text__ have been moved to a new nested document ddmFieldArrayin DXP 7.3. This issue might be caused by anyone with custom developments that execute queries in the Elasticsearch index using ddm__keyword__* and ddm__text__* fields.
• Hence, to avoid this, the user needs to use a new nested document ddmFieldArray in their Elasticsearch queries.
• Here are some examples in the Liferay code. For example, DDMIndexerImpl and AssetHelperImpl use the DDM_FIELD_ARRAY constant. 

Additional Information

• Dynamic Data Mapping fields in Elasticsearch have changed to a nested document
• LPS-103224