if i’m creating a source for use in batch mode, do i need a

Split

as well as a

SplitState

? if i understand correctly, the

SplitState

would be the thing maintaining state as the

SourceReader

reads through the split… but if we’re in Batch execution mode, would it matter? if the source is not checkpointed (batch mode), wouldn’t the

SourceReader

need to resume from zero and reread the entire split? i feel like i’m missing something. concrete example: a dynamo scan. segments map to splits, but within a segment the results may be paginated. i could store that pagination key… but does it matter? if the task fails, wouldn’t all data in the immediate downstream persistence layer be wiped anyway? and if so i’d need to resume from zero, not the partially paginated result. the connection between batch recovery and the persisted intermediate storage isn’t super clear to me in this mode