ValidationException is not in errors.go

[itsdax]

Please fill out the sections below to help us address your issue.

Version of AWS SDK for Go?

v1.29.3

Version of Go (go version)?

1.13

What issue did you see?

ValidationException is not in errors.go, but it is an exception that is returned

Steps to reproduce

	output, err := a.db.Query(queryInput)
	if err != nil {
		if e, ok := err.(awserr.Error); ok {
			switch e.Code() {
			case "ValidationException": // I have to use a custom string for this case
				return nil, "", &InvalidQueryError{err, "bad input"}
			case dynamodb.ErrCodeConditionalCheckFailedException:
				return nil, "", &InvalidQueryError{err, "failed things"}

[diehlaws]

Hi @itsdax, thanks for bringing this to our attention. Looking at the API model for DynamoDB it appears that ValidationException is not being modeled for this service. As a result it makes sense that this exception is not present in service/dynamodb/errors.go since the code surrounding a service's client and its associated methods & structures in each AWS SDK is generated based on the API model provided to us by the service team.

That being said, I'll be reaching out to the DynamoDB team internally regarding this exception not being modeled since it seems like it should be. Once I have more information on this I'll update the issue accordingly.

[itsdax]

any updates?

[diehlaws]

Unfortunately the DynamoDB team has not yet responded to this request. I've reached out to them again asking for attention on the issue.

[nikoremi97]

Same for Kinesis, I think there should be many more with the same issue.

[future-ito-masahiko]

I encountered the same problem, and found this issue.
I hope "ValidationException" will be treated as const in somewhere.

[stobrien89]

Created another ticket to track this: P51608118

[tim-finnigan]

We were informed that the DynamoDB team added this request to their backlog for further review. We recommend reaching out through AWS Support for updates going forward, but feel free to check back in here as well.

[github-actions]

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.