Skip to content

Amazon DataZone CreateAssetRevision API: Documentation says 20 glossary terms allowed but API enforces limit of 10

0

I am using the CreateAssetRevision API in Amazon DataZone to add glossary terms to an asset.

According to the documentation for CreateAssetRevision API [https://docs.aws.amazon.com/datazone/latest/APIReference/API_CreateAssetRevision.html], the glossaryTerms field supports up to 20 items. However, when I try to add more than 10 glossary terms, the API returns the following validation error:

ValidationException: $.DZ_Internal_Basic_Form.glossaryTerms: there must be a maximum of 10 items in the array

This happens when adding the 11th glossary term using the AWS CLI.

Could someone confirm whether the actual limit is 10 or 20, and whether the documentation needs to be updated?

Also I am getting following error from console! Term Error

asked 2 months ago47 views
1 Answer
0

Based on the Amazon DataZone API documentation, the CreateAssetRevision API's glossaryTerms parameter is documented to support a maximum of 20 items. The documentation specifies that glossaryTerms is an "Array of strings" with "Array Members: Minimum number of 1 item. Maximum number of 20 items."

However, you're encountering a validation error indicating a limit of 10 glossary terms. This discrepancy suggests there may be an inconsistency between the documented limit and the actual implementation or configuration in your specific use case.

There are a few possibilities to consider:

  1. Form-specific constraints: The error message mentions "$.DZ_Internal_Basic_Form.glossaryTerms", which suggests the limitation might be coming from the specific form type associated with your asset rather than the API itself. Different asset types or forms may have their own constraints that are more restrictive than the general API limit.

  2. Service quota or domain configuration: There could be service quotas or domain-level configurations that impose a lower limit than what the API documentation states.

I recommend:

  • Verifying the asset type and form configuration you're using to see if there are form-specific constraints
  • Checking your domain's service quotas and configurations
  • Contacting AWS Support to clarify the actual limit and report the documentation discrepancy if confirmed

If the limit is indeed 10 for your use case due to form constraints, then the documentation may need clarification to indicate that while the API parameter supports up to 20 terms, actual limits may vary based on the asset type and form configuration being used.
Sources
CreateAssetRevision - Amazon DataZone

answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.