Why is deadLetterPolicy attribute in the ConsumerConfigurationData class marked as transient?

[AnuragReddy2000]

As a user of Apache Pulsar, I have been utilising PulsarSpout exposed by the pulsar-storm adaptor within an Apache Storm topology for message consumption from Pulsar topics. Recently, we encountered an issue where the deadLetterPolicy that we set on the PulsarSpout seems to be lost when the topology is started. Upon investigation, we found that this is due to the deadLetterPolicy attribute in ConsumerConfigurationData being marked as transient.

Due to Storm topologies being serialised and transferred from the nimbus to workers for execution, the transient nature of this attribute results in the loss of our specified configuration. I was wondering if anyone knows why this attribute needs to be transient?

Ideally implementing the java.io.Serializable interface in the DeadLetterPolicy class should eliminate the need for the transient keyword. If this is accurate and there is no other reason for it, then I am prepared to submit a pull request for the same.

[AnuragReddy2000]

I see that this change was introduced in this PR which aimed to integrate SpotBugs in the pulsar-client module. Considering that the ConsumerConfigurationData class extends the java.io.Serializable interface , SpotBugs would check if all the attributes of that class are serializable or not. The attribute deadLetterPolicy whose type DeadLetterPolicy did not extend the aforementioned interface, would surely be flagged by SpotBugs and I believe this led to the author of that PR to mark this attribute as transient to get around it.

If some one can confirm this, I can submit a PR with the changes to make the DeadLetterPolicy class serializable & remove the transient keyword before the deadLetterPolicy attribute.

[AnuragReddy2000]

@codelipenghui Can you comment on this, as the aforementioned PR was raised by you?