Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
@graben
re: Transacted: if the PostOffice is transacted by default, that's great.
The option in 5.x felt more like a "shore-up" to get to transacted. I don't see
a compelling reason to support non-transacted broker-side message movement. A
note in the migration guide would suffice.
re: Concurrency: I see this having value, and agree it should be a separate
JIRA/PR.
re: Selector/Filter: that's great that you have it on your radar. You
mentioned filter, so I feel obligated to clarify-- this selector is determined
by the _consumer_ using the standard JMS selector available in the API. The
broker then store these to properly filter messages if the consumer goes
offline. Does Artemis' filter support this behavior, or is filtering
broker-side configuration?
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
