-
Notifications
You must be signed in to change notification settings - Fork 36
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
RabbitMQ Connector does unnecessary message unsescape action. #2730
Comments
As discussed in our team meeting we will remove unnecessary unescaping from Connectors in the next alpha. |
After testing, removing |
I'm posting the forum comment I made here for visibility:
The way I see it, we might remove any unescaping (not only in the RabbitMQ connector), but let's wait for @sbuettner or @chillleader opinions. |
Right, that Zeebe issue was the reason we added it there. If the escaping issues are gone, we no longer need the workaround. |
@chillleader Should I make an update and modify it in every connector ? |
Yes please - although I imagine there might be some corner cases where we might decide to keep unescaping for certain reasons (or maybe not, let's see during the review 🙂). But in general I think we should remove it from all connectors now. |
Yes, lets remove unnecessary escaping but not backport it as previous zeebe releases faced this issue. |
Describe the Bug
I use out-of-the-box RabbitMQ Connector. Message for sending contains string fields with escaped symbols, like:
Connector sends my message but consumer receives wrong message and fells with MessageConversionException. There’s a message which consumer receives:
All symbols
"\"
disappeared. Connector’s source code contains logic with unescaping json.Steps to Reproduce
Expected Behavior
I expect the same message in my RabbitMQ CONSUMER, message should be without any transformation.
Environment
Camunda 8 forum topic
The text was updated successfully, but these errors were encountered: