GitHub user mattrpav added a comment to the discussion: Path forward for full UTF-8 correctness
@cshannon I think you are probably on the right path here. Protocol conversion is already a throughout/latency hotspot. This would also reduce risk and allow for a clean and certain "moving forward it is fix" approach. Perhaps a we could add a KahaDB conversion tool to look for invalid UTF-8 messages on older stores to warn users as part of an 'upgrade check' certification step. GitHub link: https://github.com/apache/activemq/discussions/2658#discussioncomment-18953706 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
