mattrpav commented on PR #2634: URL: https://github.com/apache/activemq/pull/2634#issuecomment-6017006847
This is a significant change, and I'm wondering if there is a better way to update this (perhaps add new first-class methods to the store) vs branching logic based on the back-end store type. Is there a way to address the first part-- add a limit query based on maxBrowsePageSize without dissecting the entire Topic expiry code flow? That would allow us to address the core issue quickly, and then spend some time on the design to optimize expiry processing as a follow-on. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
