Sajjad Moradi

Now that we can use pause and resume endpoints, we can: 1. pause the table 2. make stream config changes to point to different topic or cluster 3. resume the...

I did not close the issue! Anyways, so the ideal scenario for your use case would be to provide the mapping of `partition id -> start offset` along with the...

I believe now with pause/resume feature, specifically consumeFrom option of resume endpoint, we can address the requirements of this issue. @Jackie-Jiang what do you think? Should we close this issue?

@npawar you're saying kafka consumer tries to fetch messages and it's unsuccessful, but the consumer doesn't throw exception?

I'm working on a design doc for this and will share it here soon.

> > > > > > > > > @Jackie-Jiang I am not sure this will solve my current issue which is that, the function where the force commit is...

Yes, force commit helps with creating new consuming segments which pull the latest schema. The challenge, however, is to know which completed segments to reload. Since we don't know when...

I thought we're using the original schema to load the locally built segment, but you're right. We always fetch the latest schema when a segment is going to be loaded.

+1 on always using force commit to reload. IMO we don't need to have a config for this.