[jira] [Commented] (ATLAS-539) Store for entity audit events

["ATLAS QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187115#comment-15187115 ] 

ATLAS QA commented on ATLAS-539:
--------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12792210/ATLAS-539-v2.patch
  against master revision 0defc6e.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

      {color:red}-1 javac{color}.  The applied patch generated 98 javac compiler warnings (more than the master's current 94 warnings).

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    +1 checkstyle.  The patch generated 0 code style errors.

    {color:red}-1 findbugs{color}.  The patch appears to introduce 338 new Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in :
 ./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.EntityJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.MetadataDiscoveryJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.RexsterGraphJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.AdminJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.TypesJerseyResourceIT

Test results: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Javac warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/59//console

This message is automatically generated.

> 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.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)