You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2018/05/08 07:40:00 UTC

[jira] [Updated] (ATLAS-2656) Update entity notifications to replace AtlasEntity with AtlasEntityHeader

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

Madhan Neethiraj updated ATLAS-2656:
------------------------------------
    Attachment: ATLAS-2656.patch

> Update entity notifications to replace AtlasEntity with AtlasEntityHeader
> -------------------------------------------------------------------------
>
>                 Key: ATLAS-2656
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2656
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: 1.0.0
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>            Priority: Major
>         Attachments: ATLAS-2656.patch
>
>
> Replacing AtlasEntity used in entity notifications with AtlasEntityHeader (which includes fewer attributes) can improve performance, especially for entities having large number of attribute or attributes having large number of array/map elements (like a hive_table containing 1000s of columns).
> In addition, it should be possible to specify which entity attributes to include in the notification via type-def - for example by updating AtlasAttributeDef with addition of a flag named 'includeInNotification'.



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