[
https://issues.apache.org/jira/browse/ATLAS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275106#comment-15275106
]
ATLAS QA commented on ATLAS-491:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12802792/0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch
against master revision 2c0dc40.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 372 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.AdminJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.RexsterGraphJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.MetadataDiscoveryJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.TypesJerseyResourceIT
Test results:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/214//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/214//console
This message is automatically generated.
> Business Catalog / Taxonomy
> ---------------------------
>
> Key: ATLAS-491
> URL: https://issues.apache.org/jira/browse/ATLAS-491
> Project: Atlas
> Issue Type: New Feature
> Affects Versions: 0.7-incubating
> Reporter: Erik Bergenholtz
> Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments:
> 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch,
> business-catalog-WIP.patch
>
>
> s a Atlas UX user, I need to:
> Browse business taxonomy hieracharlically through tree
> Search by Tags
> Search by combination of keyword, tag, free text in search field
> All search from view context of taxonomy. If 3 levels deep, then the search
> should be narrow to that scope.
> expose search ordering capabilities available through SOLR.
> As a Data Steward, I need to:
> Manage the taxonomy of objects including
> Objects Management:
> Creating new objects
> Modify the object details - annotations, external links, tags, acceptable use
> policy, etc
> Delete objects (in UI - changing status in backend,and versioning changes)
> Relationship management:
> creating relationship of objects as a parent or child
> assigning tagging to taxonomy
> verify tag inheritance
> Verify tag impact on tag based policy - ranger API call
> Tag Management:
> List
> Search
> Edit
> Delete (change state to archive)
> All user should be able to comment on any business catalog entity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
