Uh, I'm not sure what your asking. The SDF API already has a void return on processElement means that a call to tryClaim must have returned false while a non void return allows the caller to either return STOP (tryClaim must have returned false) or return RESUME (with a time of when to resume). This allows the framework code to prevent user errors by ensuring the restriction has been completed.
Also, "" is the byte key range, the code could have just passed in range.getEndPosition() in to the final tryClaim, its just that "" is shorthand and would be similar to passing in Long.MAX_VALUE for the file offset range. On Fri, Nov 30, 2018 at 2:45 AM Robert Bradshaw <[email protected]> wrote: > In looking at the SDF examples, it seems error-prone to have to > remember to write > > tryClaim([fake-end-position]) > > to indicate that a restriction is finished. IIRC, this was done to > decide whether the entire restriction had been processed on return in > the case that tryClaim never returned false. It seems preferable to > encode this into the return value (with a void return meaning iff > tryClaim returned false, and a non-void return being able to indicate > any hints as to when, if ever, process should be called again). > > Can someone job my memory as to if there was a case in which this wouldn't > work? >
