Key and partitioning support for arbitrary JMS Headers

[j0xaf]

Currently, kafka-connect-mq-source supports three distinct (logical) sources for specifying the kafka key: JMSMessageID, JMSCorrelationID (as well as the Bytes variant) and JMSDestination (see https://github.com/ibm-messaging/kafka-connect-mq-source#key-support-and-partitioning).

We would like, however, to use a custom JMS Header for populating the kafka key. Is there any specific reason why you chose to limit support to those three possibilities and not arbitrary JMS Headers? Would you accept a PR to support arbitrary JMS Headers?

Thank you for providing this connector!

[jhughes24816]

Hi @j0xaf Apologies for the long wait on this issue. This seems a worthwhile addition to the connector and we would happily welcome any contributions (you can find the contributions guide here)

I will also raise this with the development team to take a look at.