[ATLAS-2862] Export Service: Incremental Export: Next Increment Should Consider All Existing Request Contexts

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.3
• Fix Version/s: 0.8.3, 1.2.0, 2.0.0
• Component/s: atlas-core
• Assignee: Ashutosh Mestry
• Reporter: Ashutosh Mestry
• Created: 07/Sep/18 18:47
• Updated: 26/Sep/19 00:39
• Resolved: 12/Sep/18 16:18

Description

Background

When performing incremental Export, the existing implementation computes the next increment timestamp by finding the maximum value of exported entities' modificationTimestamp. This may work for majority of cases, however it has a drawback.

Consider a scenario where export is in progress and one of the entities that has already been written to the zip stream is modified by another request, this will be missed from the the subsequent export operation.

Solution Approach

• Compute timestamps by enumerating all the requests in progress and finding the earliest request. If no requests in progress, return current timestamp.
• Use the timestamp from step above for the change timestamp in AtlasExportResult.