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] [Updated] (ATLAS-2804) Export & Import Process: Add Support to Use Detailed Audits
Date Thu, 02 Aug 2018 15:39:00 GMT

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

Ashutosh Mestry updated ATLAS-2804:
-----------------------------------
    Description: 
*Background*

The implementation for ATLAS-2798, allowed for detailed audits to be captured. The implementation
for ATLAS-2797 allowed for representation of Cluster entity.

This Jira captures the integration of the 2 new entities within the Export and Import process.

*Approach Guidance*
 * Additional attribute in _AtlasExportRequest_ and _AtlasImportRequest_ say _updateMetaInfo_,
will indicate that audits need to be captured.
 * Within Export process, the value of _updateMetaInfo_ will indicate the cluster for which
the export operation was destined for. 
 * Within Import process, the value of _updateMetaInfo_ will indicate the cluster from which
the exported ZIP originated.
 * Searching on _AtlasCluster_ entity will indicate the operations performed on that cluster.
Detailed logs can be searched using approach. 
 * Ideally, web user interface should be updated to display audits in the properties view
of an _AtlasCluster_.

  was:
*Background*

The implementation for ATLAS-2798, allowed for detailed audits to be captured. The implementation
for ATLAS-2797 allowed for representation of Cluster entity.

This Jira captures the integration of the 2 new entities within the Export and Import process.

Approach Guidance
 * Additional attribute in _AtlasExportRequest_ and _AtlasImportRequest_ say _updateMetaInfo_,
will indicate that audits need to be captured.
 * Within Export process, the value of _updateMetaInfo_ will indicate the cluster for which
the export operation was destined for. 
 * Within Import process, the value of _updateMetaInfo_ will indicate the cluster from which
the exported ZIP originated.
 * Searching on _AtlasCluster_ entity will indicate the operations performed on that cluster.
Detailed logs can be searched using approach. 
 * Ideally, web user interface should be updated to display audits in the properties view
of an _AtlasCluster_.


> Export & Import Process: Add Support to Use Detailed Audits
> -----------------------------------------------------------
>
>                 Key: ATLAS-2804
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2804
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: 0.8.3
>            Reporter: Ashutosh Mestry
>            Assignee: Ashutosh Mestry
>            Priority: Major
>             Fix For: 0.8.3
>
>
> *Background*
> The implementation for ATLAS-2798, allowed for detailed audits to be captured. The implementation
for ATLAS-2797 allowed for representation of Cluster entity.
> This Jira captures the integration of the 2 new entities within the Export and Import
process.
> *Approach Guidance*
>  * Additional attribute in _AtlasExportRequest_ and _AtlasImportRequest_ say _updateMetaInfo_,
will indicate that audits need to be captured.
>  * Within Export process, the value of _updateMetaInfo_ will indicate the cluster for
which the export operation was destined for. 
>  * Within Import process, the value of _updateMetaInfo_ will indicate the cluster from
which the exported ZIP originated.
>  * Searching on _AtlasCluster_ entity will indicate the operations performed on that
cluster. Detailed logs can be searched using approach. 
>  * Ideally, web user interface should be updated to display audits in the properties
view of an _AtlasCluster_.



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

Mime
View raw message