Running .kfk.Metadata[client]; from consumer can present callback msg as follows:
mtype topic client partition offset msgtime data key headers rcvtime
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
UNKNOWN_TOPIC_OR_PART test1 0 0 -1001 "Subscribed topic not available: test1: Broker: Unknown topic or partition" `byte$() (`symbol$())!`symbol$() 2024.01.22D15:46:39.829536000
when doing this after doing a subscribe, it can make it look like the subscription had failed (when it hasn't).
Temp removing .kfk.Metadata[client]; after any subscription, the callback no longer fires with a UNKNOWN_TOPIC_OR_PART. It doesn't appear to stop the subscription from occurring, whether its there or not.
Will find out why & change this effect
Running
.kfk.Metadata[client];from consumer can present callback msg as follows:when doing this after doing a subscribe, it can make it look like the subscription had failed (when it hasn't).
Temp removing
.kfk.Metadata[client];after any subscription, the callback no longer fires with a UNKNOWN_TOPIC_OR_PART. It doesn't appear to stop the subscription from occurring, whether its there or not.Will find out why & change this effect