CFP Consistent TS Format

[tvaron3]

Description

Timestamp format was inconsistent in lease throughout life cycle of change feed processor. Initial timestamp when a lease is created has an appended [utc] because a different data object is used at lease creation than during updates. Once change feed processor starts processing the lease, the lease will get updated and the format of the timestamp is changed.

Current Flow

• At time 0, lease created with [utc] appended to timestamp --> at time 1 and after, lease updated with [utc] not appended to timestamp

New flow

• At time 0, lease created with [utc] not appended to timestamp --> at time 1 and after, lease updated with [utc] not appended to timestamp

[tvaron3]

/azp run java - cosmos - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Copilot]

Pull Request Overview

This PR standardizes timestamp format in Change Feed Processor (CFP) lease objects by converting from ZonedDateTime.toString() to Instant.toString() format. The change removes inconsistent "[UTC]" suffixes that were appearing in some timestamps.

• Updated timestamp generation in ServiceItemLease and ServiceItemLeaseV1 classes to use Instant format
• Added comprehensive test to verify timestamp consistency across CFP lifecycle
• Updated changelog to document the formatting change

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
ServiceItemLease.java	Changed timestamp generation from ZonedDateTime.toString() to toInstant().toString()
ServiceItemLeaseV1.java	Applied same timestamp format change for consistency
CHANGELOG.md	Added entry documenting the timestamp format change
IncrementalChangeFeedProcessorTest.java	Added test to verify timestamps don't contain "[UTC]" suffix

[FabianMeiswinkel]

This is a breakign change - would need either to be gated on a new Lease version - I am not convinced that it is worth it

[FabianMeiswinkel]

This is a breakign change - would need either to be gated on a new Lease version - I am not convinced that it is worth it

Discussed offline - since the lease document in a flow of
T0: Initial creation
T1..TN: Lease document being updated when progress is recorded

Would have used the same format as now in T0 in T1 and later already this is not a breakign change but just a bug fix.

[FabianMeiswinkel]

LGTM