"I have processed 5/15 records, next run I need to start at record 6". Bookmarking is a common concept for working through a large job in several small runs.
I wonder if this difference in jargon has origins in different sub-fields. I recognize that concept as "checkpoints" across different companies but I also remember seeing the term from data science folks and thinking that I just don't know the concept.
Often called a Waterline/Watermark as well.
I'd call it a watermark too; "checkpoint" can mean an intermediate point in a multi-step database transaction.
I've always called them offsets.
I would call it "a read cursor (that's updated within the transaction)", but I'm boring.
Cursor nomenclature is used for describing where in a sequence the operator is during a code execution pass in database query or similar right?
I think I kind of immediately understand "cursor" the best in this context. I also agree, it's a little boring and definitely old school:).