Skip to content

Allow MessageGroupId for standard queues #1138

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
Jul 24, 2025

Conversation

sawadashota
Copy link
Contributor

Remove validation that prevented MessageGroupId from being used with standard (non-FIFO) queues. This aligns ElasticMQ with AWS SQS's new "fair queues" feature that allows MessageGroupId on standard queues.

Fixes #1137

Remove validation that prevented MessageGroupId from being used with
standard (non-FIFO) queues. This aligns ElasticMQ with AWS SQS's new
"fair queues" feature that allows MessageGroupId on standard queues.

Fixes softwaremill#1137
@sawadashota sawadashota marked this pull request as ready for review July 22, 2025 11:22
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR removes validation that prevented MessageGroupId from being used with standard (non-FIFO) SQS queues, enabling support for AWS SQS's "fair queues" feature. The change aligns ElasticMQ's behavior with AWS SQS's updated functionality.

  • Removed validation check that rejected MessageGroupId on standard queues
  • Updated validation logic and comments to reflect support for both queue types
  • Modified test suite to verify MessageGroupId works with standard queues

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
SendMessageDirectives.scala Removes FIFO-only restriction for MessageGroupId and updates validation comments
AmazonJavaSdkTestSuite.scala Changes test from expecting rejection to verifying acceptance of MessageGroupId on standard queues
Comments suppressed due to low confidence (1)

rest/rest-sqs-testing-amazon-java-sdk/src/test/scala/org/elasticmq/rest/sqs/AmazonJavaSdkTestSuite.scala:451

  • The test assertion 'result should not be null' is too weak and doesn't verify the key behavior. Consider asserting that the message was actually sent successfully by checking result.getMessageId or retrieving the message from the queue to verify MessageGroupId was preserved.
    result should not be null

@micossow micossow merged commit 522387c into softwaremill:master Jul 24, 2025
9 checks passed
@sawadashota sawadashota deleted the fix-1137 branch July 25, 2025 05:19
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.

Remove messageGroupID validation for standard queues to support AWS SQS fair queues
2 participants