Closed AishD3 closed 1 month ago
I suspect it would be difficult to do this through configuration alone in a generic way that would work with all use cases.
For specific requirements like this, I recommend writing your own custom RecordBuilder
class. This would involve creating a new class by subclassing the existing record builder you are already using (the class that you've set the config option mq.record.builder
to point to) to reuse almost all of the existing implementation. You can override the existing getKey(JMSContext, String, Message)
method so that it returns a struct to your specific requirements. Then you just need to update the mq.record.builder
config option to point at your new class.
You could do this with a custom DefaultMessageBuilder, we won't make this a generic feature. Here the link to one of the example to do this https://ibm.github.io/event-automation/es/connecting/mq/sink/#enabling-mqmd
Description
JMSMessageID right now coming as String , Is there any configuration that can send it as Struct.
Suggested Solution
JMSMessageID right now coming as String , Is there any configuration that can send it as Struct.
Alternatives
JMSMessageID right now coming as String , Is there any configuration that can send it as Struct.
Additional Context
JMSMessageID right now coming as String , Is there any configuration that can send it as Struct.