btw. It would be useful context to explain the issue that you ran into with pulsar-storm. That seems to require serialization support?

Please also explain the context around #9630 which you explained in the GitHub Discussions question.

btw. It would be useful context to explain the issue that you ran into with pulsar-storm. That seems to require serialization support?

Sure.

We use pulsar-storm adaptor to consume messages in Storm topologies. In a Storm cluster, there is a leader Nimbus node (analogous to a master / controller node) which controls the lifecycle of any topology.

Whenever a new instance of a topology needs to be created, the topology initialization code executes on the Nimbus. Once the topology components are all initialized, the Nimbus serializes them and sends them to the worker nodes, where the execution continues.

Now the PulsarSpout provided by the pulsar-storm adaptor is one such topology component that gets initialized on the Nimbus and later gets transferred to some workers. The deadLetterPolicy is one of the many configurations that we provide during the initialization of the PulsarSpout. But due to it being marked transient, the resultant instances of the configuration object on the workers do not contain any deadLetterPolicy.