Skip to content

Conversation

@Gsantomaggio
Copy link
Member

Refactor consumer stream options and the stream filter options. This implementation is similar to the golang implementation. So the idea is to have the same API ( as much as possible ) for all the amqp 1.0. clients. Add a new class StreamFilterOptions to configure only the filtering and leave the StreamConsumerOptions for offset and other future implementations

the stream consumer options and the stream filter options. This implementation is similar to the
golang implementation. So the idea is to have the same API ( as much as possible ) for all the amqp 1.0. clients.
Add a new class StreamFilterOptions to configure only the filtering and leave the StreamConsumerOptions for offset
and other future implementations

Signed-off-by: Gabriele Santomaggio <G.santomaggio@gmail.com>
Signed-off-by: Gabriele Santomaggio <G.santomaggio@gmail.com>
@Gsantomaggio Gsantomaggio added this to the 0.1.1 milestone Sep 10, 2025
Copy link
Member

@Zerpet Zerpet left a comment

Choose a reason for hiding this comment

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

I don't see anything immediately wrong. I'm unsure about renaming the field in the qpid message from properties to message_properties, but if it doesn't break anything 🤷‍♂️

Signed-off-by: Gabriele Santomaggio <G.santomaggio@gmail.com>
@Gsantomaggio
Copy link
Member Author

@Zerpet I renamed Properties to ApplicationProperties to avoid confusion.

Following the Goland Message struct:

type Message struct {
      Properties *MessageProperties
      ApplicationProperties map[string]any

Properties is now ApplicationProperties because it represents the actual Application Properties.

In the QPID message, you can set the message properties using the specific API(s), like:

   msg = Message(subject="subject", ttl=1)
   msg.application_properties = {"app_property": "value"}
   print(f"message subject: {msg.subject}, ttl: {msg.ttl}, app_property: {msg.application_properties['app_property']}")

Signed-off-by: Gabriele Santomaggio <G.santomaggio@gmail.com>
Signed-off-by: Gabriele Santomaggio <G.santomaggio@gmail.com>
Signed-off-by: Gabriele Santomaggio <G.santomaggio@gmail.com>
@Gsantomaggio Gsantomaggio self-assigned this Sep 11, 2025
@Gsantomaggio Gsantomaggio added the enhancement New feature or request label Sep 11, 2025
@Gsantomaggio Gsantomaggio marked this pull request as ready for review September 11, 2025 09:47
@Gsantomaggio Gsantomaggio merged commit 36bb249 into main Sep 11, 2025
1 check passed
@Gsantomaggio
Copy link
Member Author

merged per conversation with @Zerpet

@Gsantomaggio Gsantomaggio deleted the feat/refactor_filtering branch September 11, 2025 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants