question

PapajohnApril-4314 avatar image
0 Votes"
PapajohnApril-4314 asked shashishailaj commented

Change feed continuation token: why is the EndTime sometimes a real time, and other times "+999999999-12-31T23:59:59.999999999-18:00" ?

On April 9th, when I was testing the change feed via the Java SDK, the continuation token had EndTime fields in them with real timestamps. Now I am seeing timestamps that look like this: "+999999999-12-31T23:59:59.999999999-18:00" ?

The latter "timestamp" is preferable, because the token was coming back before with an EndTime that rendered it unusable. But why is it now behaving differently?

azure-blob-storage
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@PapajohnApril-4314 ,
Thank you for sharing your findings with the community . It seems that the getEvents() function does lazy load of the events without any time range specification and hence the EndTime value comes as something which can be considered as infinity .

1 Vote 1 ·

1 Answer

PapajohnApril-4314 avatar image
1 Vote"
PapajohnApril-4314 answered

I just discovered why this is happening.

If I call BlobChangeFeedClient.getEvents(startTime,now) then the cursor that comes back will have an EndTime = now.
If I call BlobChangeFeedClient.getEvents(), then the cursor that comes back will have an EndTIme = +999999999-12-31T23:59:59.999999999-18:00

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.