[jira] [Commented] (SAMZA-1697) Flush hung on using default serde with MetricsSnapshotReporter

["Prateek Maheshwari (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SAMZA-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796385#comment-16796385 ] 

Prateek Maheshwari commented on SAMZA-1697:
-------------------------------------------

[~rayman7718] Is this still relevant?

> Flush hung on using default serde with MetricsSnapshotReporter
> --------------------------------------------------------------
>
>                 Key: SAMZA-1697
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1697
>             Project: Samza
>          Issue Type: Bug
>          Components: build
>            Reporter: Rayman
>            Priority: Minor
>
> If a serde is not specified for the snapshot stream then the reporter's send to kafka 
>  simply hangs, and no subsequent event is scheduled. The same thing happens when 
> the serde is specified to be anything other than metrics e.g., string.
> producer.send(source, new OutgoingMessageEnvelope(out, host, null, maybeSerialized))
> Serde for a metrics stream is specified in the config via:
>  by doing systems.kafka.streams.metrics.msg.serde=metrics,
> If this is not specified, the snapshot reporter should default to using a default-serde, and not hang on send.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)