Description
In our Topology we are serializing an object that requires its Kryo serializer to be configured with the data schema before use.
Registering the serializers when submitting the topology only takes class names, not configured serializer instances. The KryoDecorators are run before topology hooks so we cannot access topology-specific configurations that way.
Our workaround has been to pass a file path to the schema file to the workers as a TOPOLOGY_WORKER_CHILDOPTS argument and we can access that in the KryoDecorator that way.
However, we would rather not be dependent on accessing the filesystem from within our topology for multiple reasons. If we could access the topology configuration from within the KryoDecorator we could just serialize the data schema file when submitting the topology.
If there are any existing solutions for this scenario please let me know.