You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Ashutosh Mestry (JIRA)" <ji...@apache.org> on 2019/08/08 21:21:00 UTC

[jira] [Updated] (ATLAS-3362) Import Service: Table-level Imports: Updating Replication Info Improvements

     [ https://issues.apache.org/jira/browse/ATLAS-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashutosh Mestry updated ATLAS-3362:
-----------------------------------
    Attachment: ATLAS-3362-Using-different-scheme-for-storing-repl-d.patch

> Import Service: Table-level Imports: Updating Replication Info Improvements
> ---------------------------------------------------------------------------
>
>                 Key: ATLAS-3362
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3362
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: trunk
>            Reporter: Ashutosh Mestry
>            Assignee: Ashutosh Mestry
>            Priority: Major
>         Attachments: ATLAS-3362-Using-different-scheme-for-storing-repl-d.patch
>
>
> *Background*
> During import of files that have _changeMarker_, _AuditsWriter_ updates _AtlasServer_ with change marker using the parent entity. So far this worked since the mechanism was used mostly for database-level exports (and imports).
> With the introduction of table-level exports, this does not work very well since the list of tables exported to be exported can be large. 
> *Solution*
> For requests that are made for tables, fetch the guid for the table it belongs to. This will address the problem.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)