Two of the three message chunking related settings in the ConsumerConfiguration have already been exposed to the consumer. Namely, maxPendingChunkedMessage and autoAckOldestChunkedMessageOnQueueFull. However, the third one, expireTimeOfIncompleteChunkedMessageMs, has not yet been exposed. If this third one can be exposed then the python client consumer would have full control over how they want to handle chunked messages.
Motivation
Two of the three message chunking related settings in the ConsumerConfiguration have already been exposed to the consumer. Namely, maxPendingChunkedMessage and autoAckOldestChunkedMessageOnQueueFull. However, the third one, expireTimeOfIncompleteChunkedMessageMs, has not yet been exposed. If this third one can be exposed then the python client consumer would have full control over how they want to handle chunked messages.
TLDR: Expose expireTimeOfIncompleteChunkedMessageMs of the ConsumerConfiguration to the consumer, which can be found here: https://github.com/apache/pulsar-client-cpp/blob/1e7d259bb94379ef6e4618fdac283912d0be6861/lib/ConsumerConfigurationImpl.h#L61.