atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Mestry (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ATLAS-2862) Export Service: Incremental Export: Next Increment Should Consider All Existing Request Contexts
Date Fri, 07 Sep 2018 18:48:00 GMT
Ashutosh Mestry created ATLAS-2862:
--------------------------------------

             Summary: Export Service: Incremental Export: Next Increment Should Consider All
Existing Request Contexts
                 Key: ATLAS-2862
                 URL: https://issues.apache.org/jira/browse/ATLAS-2862
             Project: Atlas
          Issue Type: Bug
          Components:  atlas-core
    Affects Versions: 0.8.3
            Reporter: Ashutosh Mestry
            Assignee: Ashutosh Mestry
             Fix For: 0.8.3


*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_.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message