- 
                Notifications
    
You must be signed in to change notification settings  - Fork 9
 
refactor consumer stream options #75
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
Conversation
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>
There was a problem hiding this 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>
| 
           @Zerpet I renamed  Following the Goland  type Message struct {
      Properties *MessageProperties
      ApplicationProperties map[string]any
 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>
| 
           merged per conversation with @Zerpet  | 
    
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