littleeleventhwolf commented on PR #6524: URL: https://github.com/apache/hudi/pull/6524#issuecomment-1370415430
> > > Does #7399 solve your problem here ? > > > > > > Yeah, we cherry-pick [#7399](https://github.com/apache/hudi/pull/7399). But if user enable latency-marker, there is still thread-safety problem. > > Does the Operator has any interface to handle the latency-marker yet ? Just like what we do to watermark. We can provide an empty method `processLatencyMarker(LatencyMarker latencyMarker)` to not propagate the latency-marker. But I don't think this is an elegant way, for two reasons: 1) if Flink generates a new `StreamElement` in future version, we also need to provide an empty method for compatibility; 2) if users want to use `Watermark` or `LatencyMarker` do some other work in Operator `Sink:compact_commit`, an empty method that does not propagate these events cannot support users' requirement. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
