Skip to main content
print this page

Catalog Indexing Field limits

· 2 min read
Fix Available
Fix Available
This bug has been fixed

Catalog indexing failed with field limit exceeded error

Affected Versions: 3.0 3.0.3 3.0.6

Fix Version: 3.1

Root cause(s)​

For generation of OpenSearch( underlying service) indexing queries via Amorphic(backend purposes only), there is a hard field limit on the size(character limit) for the query which exceeds in case of nested metadata(which are used for indexing resource metadata in Amorphic) leading to failure in indexing. The metadata in question is the AssetSchema to the resource to be put into OpenSearch cluster which can lead to very huge indexing queries.

Due to usage of dynamic mapping within the underlying OpenSearch index, more than the required fields were introduced based on the data being indexed. A reduction was made to these attributes to avoid future errors.

Impact​

  • Indexing of metadata was consistently failing
  • Failed operations in Amorphic Catalog due to no indexed metadata

Mitigation​

Fix available

Fix is available from Amorphic version 3.1. Please upgrade to the aforementioned version or beyond to resolve this issue.

Timeline​

  • 2025-06-10: Bug reported/identified (CLOUD-5726)
  • 2025-06-30: Bug triaged and documented
  • 2025-07-01: Root cause analysis and fix development
  • 2025-07-07: Fix done and testing completed
  • 2025-07-30: Solution merged and newer version having the fix