[ https://issues.apache.org/jira/browse/ATLAS-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189392#comment-15189392 ]
ATLAS QA commented on ATLAS-512: -------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12792510/ATLAS-512-1.patch against master revision 1610791. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 6 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler 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 335 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 : org.apache.atlas.services.DefaultMetadataServiceMockTest ./repository/target/surefire-reports/junitreports/TEST-org.apache.atlas.services.DefaultMetadataServiceMockTest Test results: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningsnotification.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningscommon.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningsclient.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningstitan.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningsrepository.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningswebapp.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/63//console This message is automatically generated. > Decouple currently integrating components from availability of Atlas service > for raising metadata events > --------------------------------------------------------------------------------------------------------- > > Key: ATLAS-512 > URL: https://issues.apache.org/jira/browse/ATLAS-512 > Project: Atlas > Issue Type: Sub-task > Reporter: Hemanth Yamijala > Assignee: Hemanth Yamijala > Attachments: ATLAS-512-1.patch, ATLAS-512.patch > > > The components that currently integrate with Atlas (Hive, Sqoop, Falcon, > Storm) all communicate their metadata events using Kafka as a messaging > layer. This effectively decouples these components from the Atlas server. > However, all of these components have some initialization that checks if > their respective models are registered with Atlas. For components that > integrate on the server, like HiveServer2 and Falcon, this initialization is > a one time check and hence, is manageable. Others like Sqoop, Storm and the > Hive CLI are client side components and hence the initialization happens for > every run or session of these components. Invoking the initialization (and > the one time check) every time like this effectively means that the Atlas > server should be always available. > This JIRA is to try and remove this dependency and thus truly decouple these > components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)