能否基于Message Attribute从Amazon SQS向MSSQL发送指定消息？

Absolutely! You can totally filter messages by their Message Attributes when moving them from Amazon SQS to your MSSQL database. Let me walk you through how to make this work for your specific use case (sending only Class B messages):

Step 1: Add Attribute Filtering Logic to Your Listener #

When your button triggers the message pull, don’t just fetch all messages from SQS. Instead, tweak your code to:

• First, request the Class Message Attribute when calling SQS’s ReceiveMessage API
• Then, filter the received messages to only keep those where the Class attribute equals B

Here’s a quick example using Python and boto3 (adjust to your preferred language):

import boto3

sqs_client = boto3.client('sqs', region_name='your-region')
QUEUE_URL = "your-sqs-queue-url"

def get_class_b_messages():
    # Fetch messages and explicitly request the 'Class' attribute
    response = sqs_client.receive_message(
        QueueUrl=QUEUE_URL,
        MessageAttributeNames=['Class'],  # Only pull the attribute we care about
        MaxNumberOfMessages=10,  # Adjust based on your needs
        VisibilityTimeout=30
    )

    class_b_messages = []
    if 'Messages' in response:
        for msg in response['Messages']:
            # Check if the message belongs to Class B
            class_attr = msg['MessageAttributes'].get('Class')
            if class_attr and class_attr['StringValue'] == 'B':
                class_b_messages.append(msg)
    
    return class_b_messages

Step 2: Write Filtered Messages to MSSQL #

Once you have your filtered Class B messages, you can write them to your MSSQL database using your preferred database driver. For example, with pyodbc in Python:

import pyodbc
import json

def insert_into_mssql(messages):
    # Set up your MSSQL connection string
    conn_str = (
        "DRIVER={ODBC Driver 17 for SQL Server};"
        "SERVER=your-mssql-server;"
        "DATABASE=your-database;"
        "UID=your-username;"
        "PWD=your-password"
    )

    with pyodbc.connect(conn_str) as conn:
        cursor = conn.cursor()
        for msg in messages:
            # Parse the message body (adjust based on your message format)
            msg_content = json.loads(msg['Body'])
            
            # Execute your INSERT query
            cursor.execute(
                "INSERT INTO YourTable (Name, [OtherColumns]) VALUES (?, ?)",
                (msg_content['name'], msg_content['other_field'])
            )
            
            # Optional: Delete the message from SQS after successful insertion to avoid reprocessing
            sqs_client.delete_message(
                QueueUrl=QUEUE_URL,
                ReceiptHandle=msg['ReceiptHandle']
            )
        
        conn.commit()

Step 3: Tie It All to Your Button’s Click Event #

Finally, hook these functions up to your listener’s button click. When the button is pressed:

1. Run get_class_b_messages() to fetch only the messages you want
2. Pass the filtered list to insert_into_mssql() to write them to the database

Bonus: If You’re Using AWS Services Like Lambda #

If you ever switch to an automated workflow (instead of a button-triggered listener), you can use SQS Event Filtering with Lambda. This lets you configure Lambda to only trigger when a message has the Class: B attribute, so you don’t have to handle filtering in code at all. But for your current button-based setup, the code-level filtering is perfect.

This approach ensures only the messages with your target Message Attribute get sent to MSSQL—exactly what you need for your Class B use case!

内容的提问来源于stack exchange，提问作者Shubham Khandelwal