Zike Yang
Zike Yang
> but I noticed that the [v0.13.0](https://github.com/apache/pulsar-client-go/milestone/15) milestone has a deadline in 2 days. > And was wondering, due to the nature of the change, if it would be feasible...
> Hi I am a new coder and would really like to contribute, Please can I pick this one up ? Thank You! Sure. Thanks. I assigned this to you.
Thanks for reporting it. I'm +1 for this. Just to make sure we need to handle the backward compatibility carefully.
I think we could add an interceptor in the DLQPolicy so that we can let users choose whether each message need to be retried. Does it make sense to you?...
Thanks for your issue. I paste the email discussion about this issue here: https://lists.apache.org/thread/ryn7pq0ctfd5372ww1gsplkplz2sjc0d to add more context.
The consumer would print the error log here: https://github.com/apache/pulsar-client-go/blob/024e230d32fc6a0d5586b8c8bc6b34a208b9e9d0/pulsar/internal/connection.go#L765-L770 Could you check this log? Here is an example: ``` time="2025-02-20T18:29:28+08:00" level=error msg="handle message Id: ledgerId:97 entryId:2 partition:-1" consumerID=1 error="fake decompress...
Sorry for the late reply. Seems I misunderstood and thought it was just a logging issue. > {"log":{"consumerID":76, "error":"unexpected EOF","level":"ERROR","local_addr":{"IP":"10.108.35.29","Port":51180,"Zone":""}, "msg":"handle message Id: ledgerId:60350 entryId:361 partition:-1", "remote_addr":{"ForceQuery":false,"Fragment":"","Host":"platform-pulsar-broker-0.platform-pulsar-broker.t-bt.svc.cluster.local:6650","OmitHost":false,"Opaque":"","Path":"","RawFragment":"","RawPath":"","RawQuery":"","Scheme":"pulsar","User":null},"time":"2025-02-20T13:46:26.095528909Z"},"stream":"stdout","timestamp":1740059186095} Which compression algorithm...
> we are using CompressionType.LZ4 That's strange. The LZ4 decompression doesn't seem to use the reader, so it shouldn't cause the EOF error. Maybe I missed something. However, I noticed...
@nodece I can help move the release forward. Or would you like to hand it over to me for 0.15.0 release?
I believe the main issue is that the buffer is sent to the connection when the data is flushed at this line: `https://github.com/apache/pulsar-client-go/blob/0ab28c229e4dab2adb505a135325b6ede6e0e4f4/pulsar/producer_partition.go#L910`. Because of this, both the data request...