Hi Satish and all, I wonder if https://issues.apache.org/jira/browse/KAFKA-14993 should be included in the 3.6 release plan. I'm thinking that when implemented, it would be a small, but still a change in the RSM contract: throw an exception instead of returning an empty InputStream. Maybe it should be included right away to save the migration later? What do you think?
Best, Ivan On Fri, Sep 8, 2023, at 02:52, Satish Duggana wrote: > Hi Jose, > Thanks for looking into this issue and resolving it with a quick fix. > > ~Satish. > > On Thu, 7 Sept 2023 at 21:40, José Armando García Sancio > <jsan...@confluent.io.invalid> wrote: > > > > Hi Satish, > > > > On Wed, Sep 6, 2023 at 4:58 PM Satish Duggana <satish.dugg...@gmail.com> > > wrote: > > > > > > Hi Greg, > > > It seems https://issues.apache.org/jira/browse/KAFKA-14273 has been > > > there in 3.5.x too. > > > > I also agree that it should be a blocker for 3.6.0. It should have > > been a blocker for those previous releases. I didn't fix it because, > > unfortunately, I wasn't aware of the issue and jira. > > I'll create a PR with a fix in case the original author doesn't respond in > > time. > > > > Satish, do you agree? > > > > Thanks! > > -- > > -José >
