You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/09/10 18:52:00 UTC

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

    [ https://issues.apache.org/jira/browse/ATLAS-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16609674#comment-16609674 ] 

ASF subversion and git services commented on ATLAS-2862:
--------------------------------------------------------

Commit 833fb20a182a1a9e43357e66161aaf094302bc72 in atlas's branch refs/heads/branch-0.8 from [~ashutoshm]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=833fb20 ]

ATLAS-2862: Incremental Export now uses request context to determine change marker.


> 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
>            Priority: Major
>             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)