Handling of unknown partition number when using partitioner callback

[winbatch]

Magnus- finding different behavior when using a partitioner callback and intentionally picking a number larger than the number of partitions. If I don't use a partitioner callback and specify a bad number, I get an unknown partition error and the produce returns -1 (good). If I do use a partitioner and have it use a bad partition, produce does not return a -1 and I get a Local Message Timeout error instead. Any idea?

[edenhill]

Good catch.
Its a bug in the code that decides whether a topic/partition exists or not, based on last received metadata, etc.

[edenhill]

Should be fixed now. Can you verify on your end?

[winbatch]

Confirmed fixed. Thanks!