atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-539) Store for entity audit events
Date Wed, 16 Mar 2016 08:39:33 GMT

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

Shwetha G S updated ATLAS-539:
------------------------------
    Attachment: ATLAS-539-v4.patch

Latest patch from reviewboard

> Store for entity audit events
> -----------------------------
>
>                 Key: ATLAS-539
>                 URL: https://issues.apache.org/jira/browse/ATLAS-539
>             Project: Atlas
>          Issue Type: Sub-task
>            Reporter: Shwetha G S
>            Assignee: Shwetha G S
>             Fix For: 0.7-incubating
>
>         Attachments: ATLAS-539-v2.patch, ATLAS-539-v3.patch, ATLAS-539-v4.patch, ATLAS-539.patch
>
>
> We need to store the entity update events in some store. The search supported should
return all events for a given entity id within some timerange.
> Two choices are:
> 1. Existing graph db - We can create a vertex for every update with properties for entity
id, timestamp, action and details. This will create disjoint vertices. The direct gremlin
search is enough to retrieve all events for the entity. 
> Pros - We already have configurations for graph and utilities to store/get from graph
> Cons - It will create extra data and doesn't fit the graph model
> 2. HBase - Store events with key = entity id + timestamp and columns for action and details.
The table scan supports the required search
> Pros - Fits the data model
> Cons - We will need the configurations and code to read and write from hbase
> In either case, we should expose an interface so that alternative implementations can
be added



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

Mime
View raw message