Error handling question "treat any error that has neither retriable, abortable, or fatal set, as a fatal error" about librdkafka HOT 4 OPEN

this is a interface design issue ... and am confused how to handle this in our application.
How can I request for interface upgrade for this functionality and get this prioritized?

from librdkafka.

'Set' here means that they are true, not that they can be set or unset. So if all of rd_kafka_error_is_retriable, rd_kafka_error_is_fatal and rd_kafka_error_txn_requires_abort are false, then the reccomendation is to treat it as a fatal error. So to recreate the producer and possibly the consumer(s) whose offsets are included in the transaction too.

from librdkafka.

Thanks @emasab for clarification, so as I expected. 'Set' has the meaning of kind of 'bit set' which means true. I would still update the docs to be clearer here.

from librdkafka.

@flojdek Would this be clearer?
For all other errors returned from the transactional API: the current recommendation is to treat any error that has neither retriable, abortable, or fatal functions returning true, as a fatal error.

from librdkafka.