You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Sarath Subramanian (JIRA)" <ji...@apache.org> on 2017/01/16 22:22:26 UTC

[jira] [Updated] (ATLAS-1463) Mechanism to exclude specified entity attributes from getting stored in audit repository during entity create/update/delete operations

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

Sarath Subramanian updated ATLAS-1463:
--------------------------------------
    Attachment: ATLAS-1463.1.patch

> Mechanism to exclude specified entity attributes from getting stored in audit repository during entity create/update/delete operations
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-1463
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1463
>             Project: Atlas
>          Issue Type: Improvement
>    Affects Versions: 0.8-incubating
>            Reporter: Sarath Subramanian
>            Assignee: Sarath Subramanian
>         Attachments: ATLAS-1463.1.patch
>
>
> Atlas uses HBase as its store for audit repository and when new entities are created the entity definition string along with all its attributes are stored in audit repository. When size of the entity is greater than "hbase.client.keyvalue.maxsize" property then entity creation fails with "KeyValue size too large" exception.
> A property needs to be set in atlas-application.properties to specify list of attributes to be excluded from getting stored in audit repo. Also check needs to be made to make sure entity size is not greater than keyvalue max size.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)