Skip to content

Update non-streaming error unmarshaller with the new mapping function #6122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 22, 2025

Conversation

S-Saranya1
Copy link
Contributor

@S-Saranya1 S-Saranya1 commented May 20, 2025

Update non-streaming error unmarshalling with the new mapping function.

Motivation and Context

This change updates the non-streaming error unmarshalling to use the same mapping function that was previously implemented for streaming operations. This change deprecates BaseAwsJsonProtocolFactory#createErrorResponseHandler(JsonOperationMetadata). We have switched all usages in generated code to the replacement, createErrorResponseHandler(JsonOperationMetadata,Function).

Modifications

  • Updated non-streaming error unmarshalling to use exceptionMetadataMapper
  • Removed registerModeledException calls from initProtocolFactory
  • Updated codegen test files to match new exception mapping implementation

Testing

  • Added a test in kinesis service and verified it unmarshalled correctly
  • Ran integration tests

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

@S-Saranya1 S-Saranya1 requested a review from a team as a code owner May 20, 2025 20:25
.shardIterator("Invalid-Shard-Iterator")
.build();

client.getRecords(request);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's use assertThatThrownBy instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done, updated the tests.

.shardIterator("NonExistent-Shard-Iterator")
.build();

client.getRecords(request);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

@davidh44
Copy link
Contributor

Approved previously in earlier PR : #5991

Approving, pending test changes requested by Zoe

Copy link

@S-Saranya1 S-Saranya1 added this pull request to the merge queue May 22, 2025
Merged via the queue into master with commit 8450448 May 22, 2025
22 checks passed
@S-Saranya1 S-Saranya1 deleted the somepal/update-non-streaming-error-unmarshaller branch May 22, 2025 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants