Neha Pawar

Since this is more than a month old, and I believe Deena since asked this on slack, closing this issue.

Looks like this has been addressed. Closing.

Assuming we are okay with these dependencies in pinot-client @xiangfu0 , labeling this as beginner as it looks straightforward enough to fix. Lmk if it is not.

Seems we can close this issue, as the specific thing to address has been identified in #9177 ?

> Design doc: https://docs.google.com/document/d/1kTUfBud1SBSh_703mvu6ybkbIwiKKH9eXpdcpEmhC2E/edit > > This is an extension of PR #9096 > > # Motivation > Most stream systems provide a message envelope, which encapsulates the record payload,...

@ankitsultana did this work for you? can this issue be closed?

@mcvsubbu validation manager doesn't fix this. I see validation manager checking for this only in the scenario of ` if (isAllInstancesInState(instanceStateMap, SegmentStateModel.OFFLINE)) {` @richardstartin I think this is a separate...

Thanks @lfernandez93 for the additional logs. As discussed, this looks like Kafka side is claiming to reset offset to what's available, but after that either the message batch doesn't contain...

Yes, after resetting offset to latest, the Kafka consumer should be returning the messages from new offset. So either it's not, or Pinot consumer is rejecting those messages. Hence responded...

@lfernandez93 yes, i was able to reproduce. I've submitted a fix