[jira] [Comment Edited] (ATLAS-2974) Docker build: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin...

[Nigel Jones (Jira)]

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

Nigel Jones edited comment on ATLAS-2974 at 5/16/20, 12:42 PM:
---

I do think that for anyone consuming Atlas it would be pretty nice for the 
atlas project to create/maintain docker images - we really don't want to do 
that and so would be happy to aid in that discussion if there's interest? 


was (Author: jonesn):
I do think that for anyone consuming Atlas it would be pretty nice for the 
atlas project to create/maintain docker images - we really don't want to do 
that but would be happy to aid in that discussion if there's interest? 

> Docker build: Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin...
> --
>
> Key: ATLAS-2974
> URL: https://issues.apache.org/jira/browse/ATLAS-2974
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dmitry Goryunov
>Assignee: Xinran Tinney
>Priority: Major
> Attachments: tmp
>
>
> Version: commit 945de013f5466ffcf71d16c6ec1772fdee83e2f6 (Also reproducable 
> with 1.1.0-rc2)
>  
> Runnign command:
> {code:java}
> docker build -t atlas_docker .
> {code}
> Breaks at some point with:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce 
> (enforce-versions) on project apache-atlas: Some Enforcer rules have failed. 
> Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :apache-atlas
> The command '/bin/sh -c mvn clean install -DskipTests 
> -Pdist,embedded-hbase-solr -f ./atlas/pom.xml' returned a non-zero code: 1
> {code}
> The complete logs are attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-2974) Docker build: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin...

[Nigel Jones (Jira)]

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

Nigel Jones commented on ATLAS-2974:


I do think that for anyone consuming Atlas it would be pretty nice for the 
atlas project to create/maintain docker images - we really don't want to do 
that but would be happy to aid in that discussion if there's interest? 

> Docker build: Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin...
> --
>
> Key: ATLAS-2974
> URL: https://issues.apache.org/jira/browse/ATLAS-2974
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dmitry Goryunov
>Assignee: Xinran Tinney
>Priority: Major
> Attachments: tmp
>
>
> Version: commit 945de013f5466ffcf71d16c6ec1772fdee83e2f6 (Also reproducable 
> with 1.1.0-rc2)
>  
> Runnign command:
> {code:java}
> docker build -t atlas_docker .
> {code}
> Breaks at some point with:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce 
> (enforce-versions) on project apache-atlas: Some Enforcer rules have failed. 
> Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :apache-atlas
> The command '/bin/sh -c mvn clean install -DskipTests 
> -Pdist,embedded-hbase-solr -f ./atlas/pom.xml' returned a non-zero code: 1
> {code}
> The complete logs are attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-2974) Docker build: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin...

[Nigel Jones (Jira)]

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

Nigel Jones commented on ATLAS-2974:


Hi [~sonnyhcl] . I'm not actively working on any atlas specific work right now, 
but we do build atlas images in our Egeria project. We have a helm chart (for 
k8s) that sets up an environment to test/demo/develop interop between Egeria 
and atlas

That image build can be found at 
[https://github.com/odpi/egeria/tree/master/open-metadata-resources/open-metadata-deployment/docker/build-images/apache/atlas]
 . That is building Atlas 2.0 rather than master. We used to build, but since 
we've not done anything atlas related for a while the build got dropped when we 
moved infrastructure. The last build is from 8 months ago at 
[https://hub.docker.com/repository/docker/odpi/apache-atlas?ref=login] . I do 
built it manually occasionally, and we are moving it's repo in the next few 
weeks so I may revisit it then. 
We use this as a base image, then also build 
[https://github.com/odpi/egeria/blob/master/open-metadata-resources/open-metadata-deployment/docker/apache-atlas/Dockerfile]
 for a few specific configuration steps. This is part of our build pipelines at 
[https://dev.azure.com/ODPi/Egeria/_build?definitionId=13&_a=summary]

Hope that background helps.

But for your specific question on port 2181 - that's zookeeper – I haven't run 
a 'normal' atlas build for well over a year, and I can't remember that aspect 
of setup sorry, but we do slightly modify the normal atlas config for kafka 
(which uses zookeeper) in the second image - so we don't clash with the 
zookeeper/kafka configuration we use with our code. So I would look at whether 
zookeeper is starting up correctly, and which port it is using.

You could also try the image above to see if it works - I've not tested 
recently. I'll take a quick look to see if it works if I get a chance in the 
next few days.

> Docker build: Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin...
> --
>
> Key: ATLAS-2974
> URL: https://issues.apache.org/jira/browse/ATLAS-2974
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dmitry Goryunov
>Assignee: Xinran Tinney
>Priority: Major
> Attachments: tmp
>
>
> Version: commit 945de013f5466ffcf71d16c6ec1772fdee83e2f6 (Also reproducable 
> with 1.1.0-rc2)
>  
> Runnign command:
> {code:java}
> docker build -t atlas_docker .
> {code}
> Breaks at some point with:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce 
> (enforce-versions) on project apache-atlas: Some Enforcer rules have failed. 
> Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :apache-atlas
> The command '/bin/sh -c mvn clean install -DskipTests 
> -Pdist,embedded-hbase-solr -f ./atlas/pom.xml' returned a non-zero code: 1
> {code}
> The complete logs are attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-1773:


Fixup patch removed as no longer relevant given changes (omrs->egeria, latest 
1773 patch)

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-08-31.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-1773:
---
Attachment: (was: ATLAS-1799-nigel-fixup-20180718a,.patch)

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-08-31.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-1773:
---
Attachment: ATLAS-1799-nigel-fixup-20180718a,.patch

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-07-12.patch, 
> ATLAS-1799-nigel-fixup-20180718a,.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-1773:


Updated with new patch to accomodate more Egeria changes. UT ok.. Needs 
review/comments from Graham, sharing to help anyone else trying to use the 
connector[^ATLAS-1799-nigel-fixup-20180718a,.patch]

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-07-12.patch, 
> ATLAS-1799-nigel-fixup-20180718a,.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-1773:
---
Attachment: (was: ATLAS-1773-intellijfix_pom_spring_latestegeria.patch)

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-07-12.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-1773:
---
Attachment: ATLAS-1773-intellijfix_pom_spring_latestegeria.patch

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-07-12.patch, 
> ATLAS-1773-intellijfix_pom_spring_latestegeria.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-1773:


There was a change to egeria yesterday which now requires a change in 
OpenMetadataRepositoryConnector.java

in saveRelationshipReference in the fragment after 'create the RelationshipDef' 
modify the assignment of the metadataCollectionId to:

metadataCollectionId = 
restAPI.getMetadataCollectionId().getMetadataCollectionId();

With those patches (plus a webapp/pom.xml atlas dependency change I missed) the 
connector can be started

Also in webapp/src/main/webapp/WEB-INFO/openMetadataContext.xml I *think* we 
need to inclde org.odpi.openmetadata in the spring component scan

My additions so far are attached (intellij 
patch)[^ATLAS-1773-intellijfix_pom_spring_latestegeria.patch]

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-07-12.patch, 
> ATLAS-1773-intellijfix_pom_spring_latestegeria.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-1773:


with the 20180712 patch I found I had to update the openmetadata pom.xml to 
change atlas dependency versions from 1.0.0-SNAPSHOT to 2.0.0-SNAPSHOT for 
apache-atlas & atlas-repository

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-07-12.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-1696) Governance Engine OMAS

[Nigel Jones (JIRA)]

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

Nigel Jones resolved ATLAS-1696.

Resolution: Won't Do

Moved to odpi egeria - see 
https://github.com/odpi/egeria/tree/master/open-metadata-implementation/access-services/governance-engine

> Governance Engine OMAS
> --
>
> Key: ATLAS-1696
> URL: https://issues.apache.org/jira/browse/ATLAS-1696
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>  Labels: VirtualDataConnector
>
> Governance Engine OMAS is one of multiple consumer-centric based interfaces 
> that will be added to Apache Atlas, & provides the API (REST and messaging) 
> to support policy enforcement frameworks such as Apache Ranger. Detailed 
> knowledge of the Atlas data models and structure can then be hidden from 
> these consumers.
> The functionality of gaf includes
>  - ability to retrieve classifications associated to assets
>   - restricted to "interesting" classifications 
>   - restricted to interesting assets being managed by the requesting endpoint
>  - to retrieve a list of interesting roles that relate to enforcement
>  - to retrieve any template rule definitions/lookup tables that might be used 
> to construct executable rules
> The scoping constructs supported in the API will include
>  - Only get classifications that are relevant for security enforcement (ie: 
> only those inheriting from a specified supertype? Verify in ATLAS-1839)
>  - only get information about assets (resources) in a certain part of the 
> datalake (Q: HOW. By zone? How to specify? by asset type? By associated 
> endpoint?)
>  - pagination
>  
> See ATLAS-1839 for more information on the model and classifications
> In the Atlas data model classifications propagate - for example
>  * An database column DOB has no explicit classification
>  * It's containing table CDB  is classified as "customer personal details"
>  * The "SPI" classification is attached to this table with the value 
> "sensitive"
> At enforcement time all that an engine such as ranger cares about is that the 
> column "DOB" is sensitive, how we got there isn't important.  In the example 
> above the propogation occurs
>  * Along the assigned term relationship 
>  * along the structural containment relationship (table->column)
> Therefore gaf omas will "flatten" the structure - so in this case we'll see
>  table/CDB - SPI:sensitive
>  column/DOB - SPI:sensitive
> There will be cases where multiple classifications (of the same type) can be 
> navigated to from an asset like DOB. This may not make logical sense, 
> however, Until precedence is resolved in ATLAS-1839 & related Jiras, OMAS 
> will pass through multiple classifications
> This interface will also support message notifications of changes to managed 
> resources such as a new role, classification. A single kafka topic will be 
> used. 
>  
> A first pass swagger can be found at 
> https://app.swaggerhub.com/apis/planetf1/GovernanceActionOMAS/0.1
> NOTE: Updated 23 Aug with new name of GOVERNANCE ENGINE OMAS



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-1694) Sample assets to support Virtual Connector Project

[Nigel Jones (JIRA)]

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

Nigel Jones resolved ATLAS-1694.

Resolution: Won't Do

This work has now moved to https://github.com/odpi/egeria

> Sample assets to support Virtual Connector Project
> --
>
> Key: ATLAS-1694
> URL: https://issues.apache.org/jira/browse/ATLAS-1694
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>  Labels: VirtualDataConnector
>
> Assets to support the virtual data connector project as samples
> for example
>  - sample data
>  - sample rules/policies/classifications
>  - tools
>  - integration for GaianDB (open source virtualization engine)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-2593) Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework

[Nigel Jones (JIRA)]

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

Nigel Jones resolved ATLAS-2593.

Resolution: Won't Do

This work has now moved to the odpi egeria project at 
[https://github.com/odpi/egeria]  & in particular 
https://github.com/odpi/egeria/tree/master/open-metadata-implementation/access-services/governance-engine

> Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework
> --
>
> Key: ATLAS-2593
> URL: https://issues.apache.org/jira/browse/ATLAS-2593
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2593.patch, ATLAS-2593b.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2464) Information View OMAS Listener

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2464:


I wasn't able to apply the 2464_24_05 patch on top of current master using git 
am:

 

09:57 $ git am < ~/src/patches/omasMay29/ATLAS-2464_24_05.patch
Applying: ATLAS-2464 - omas information view and small omrs changes
error: patch failed: 
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java:32
error: 
omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java:
 patch does not apply
.git/rebase-apply/patch:1116: new blank line at EOF.
+
.git/rebase-apply/patch:2860: new blank line at EOF.
+
Patch failed at 0001 ATLAS-2464 - omas information view and small omrs changes
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

 

However, the patch did apply using the native intellij patcher

> Information View OMAS Listener
> --
>
> Key: ATLAS-2464
> URL: https://issues.apache.org/jira/browse/ATLAS-2464
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Maryna Strelchuk
>Assignee: Ruxandra Rosu
>Priority: Major
> Attachments: 0001-IV-OMAS-initial-patch-08.05.patch, 
> ATLAS-2464_24_05.patch, initial_patch_iv.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2665) Add OMAG API and OMAS APIs in Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2665:


Patch does not apply on top of master+2523+1773

 

8:36 $ git am < ~/src/patches/ATLAS-2665-Add-OMAG-API-in-Atlas-v7.patch
Applying: ATLAS-2665 Add OMAG-API in Atlas
error: patch failed: omrs/pom.xml:39
error: omrs/pom.xml: patch does not apply
Patch failed at 0001 ATLAS-2665 Add OMAG-API in Atlas
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

 

Applying with intellij just shows the errant patch hunk is


 org.springframework
 spring-web
 


 com.fasterxml.jackson.core
 jackson-databind
 ${jackson.version}
 

It just looks as if the patch can't find the right place to slot it in, 
probably due to other pom changes. Easy to merge manually, so could be useful 
to rebase the patch in the context of 2523+1773 (as base before applying any 
other patches?)

> Add OMAG API and OMAS APIs in Atlas
> ---
>
> Key: ATLAS-2665
> URL: https://issues.apache.org/jira/browse/ATLAS-2665
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Bogdan Sava
>Assignee: Bogdan Sava
>Priority: Major
> Attachments: 0001-ATLAS-2665-Add-OMAG-API-in-Atlas.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v3.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v4.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v5.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v6.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v7.patch
>
>
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> Change base URL for the API to "/open-metadata" 
>  
> Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
> resources annotated with.
> Spring mvc has contextConfigLocation init param pointing to 
> /WEB-INF/openMetadataContext.xml which scans the packages:
> {code:java}
> 
> {code}
>  The base URIs will be:
>  - for OMAS: /open-metadata/access-services/
>  - for OMAG: /open-metadata/admin/
>  The omag server spring boot application will have /open-metadata as context 
> path also
>  
> As result:
> /api/* paths will be handled bu jersey-servlet ( 
> com.sun.jersey.spi.spring.container.servlet.SpringServlet )
> /openmetadata/* will be handled by openmetadata-servlet ( 
> org.springframework.web.servlet.DispatcherServlet )
>  
> {code:java}
> 
>  jersey-servlet
>  
>  com.sun.jersey.spi.spring.container.servlet.SpringServlet
>  
>  
>  com.sun.jersey.api.json.POJOMappingFeature
>  true
>  
>  1
> 
> 
>  jersey-servlet
>  /api/atlas/*
> 
> 
>  open-metadata
>  
>  org.springframework.web.servlet.DispatcherServlet
>  
>  
>  contextConfigLocation
>  /WEB-INF/openMetadataContext.xml
>  
>  2
> 
> 
>  open-metadata
>  /open-metadata/*
> 
> {code}
>  
> The review board is: [https://reviews.apache.org/r/67083/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-1773:


Patch applied ok on master+2523, but has some whitespace errors that could be 
cleaned up for final patch

 

08:35 $ git am < ~/src/patches/ATLAS-1773-2018-05-25\ \(1\).patch
Applying: ATLAS-1773: Atlas connector
.git/rebase-apply/patch:2087: new blank line at EOF.
+
.git/rebase-apply/patch:2461: new blank line at EOF.
+
.git/rebase-apply/patch:16630: new blank line at EOF.
+
.git/rebase-apply/patch:17018: new blank line at EOF.
+
warning: 4 lines add whitespace errors.

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-05-25.patch, Notes on running the OMRS 
> stack including the Atlas OMRS connector.txt
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2593) Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2593:


Added current patch. Intermediate WIP. Based on older-style OMRS/omas 
templates, needs refactoring to accomodate recent changes in rest etc.

> Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework
> --
>
> Key: ATLAS-2593
> URL: https://issues.apache.org/jira/browse/ATLAS-2593
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2593.patch, ATLAS-2593b.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2593) Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2593:
---
Attachment: ATLAS-2593b.patch

> Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework
> --
>
> Key: ATLAS-2593
> URL: https://issues.apache.org/jira/browse/ATLAS-2593
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2593.patch, ATLAS-2593b.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2693) Revert ATLAS-2668 for 1.0 branch

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2693:


NOTE: Apply patch ONLY to 1.0 branch.

(not master)

> Revert ATLAS-2668 for 1.0 branch
> 
>
> Key: ATLAS-2693
> URL: https://issues.apache.org/jira/browse/ATLAS-2693
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2693.patch
>
>
> Revert ATLAS-2668 for the 1.0 branch as per review 
> [https://reviews.apache.org/r/67060/#comment285318]
>  
> We could revert the entire fix, however the simplest minimum change is to 
> remove the reference to the assembly from the distro pom. This means that the 
> binary is not placed into the distro directory, though the jar with 
> dependencies is still built in the component directory, and the assembly xml 
> file will still exist in distro.
> If we need to revert the entire fix please comment here and I'll update with 
> a new patch :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2693) Revert ATLAS-2668 for 1.0 branch

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2693:
---
Attachment: (was: ATLAS-2699.patch)

> Revert ATLAS-2668 for 1.0 branch
> 
>
> Key: ATLAS-2693
> URL: https://issues.apache.org/jira/browse/ATLAS-2693
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2693.patch
>
>
> Revert ATLAS-2668 for the 1.0 branch as per review 
> [https://reviews.apache.org/r/67060/#comment285318]
>  
> We could revert the entire fix, however the simplest minimum change is to 
> remove the reference to the assembly from the distro pom. This means that the 
> binary is not placed into the distro directory, though the jar with 
> dependencies is still built in the component directory, and the assembly xml 
> file will still exist in distro.
> If we need to revert the entire fix please comment here and I'll update with 
> a new patch :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2693) Revert ATLAS-2668 for 1.0 branch

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2693:
---
Attachment: ATLAS-2693.patch

> Revert ATLAS-2668 for 1.0 branch
> 
>
> Key: ATLAS-2693
> URL: https://issues.apache.org/jira/browse/ATLAS-2693
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2693.patch
>
>
> Revert ATLAS-2668 for the 1.0 branch as per review 
> [https://reviews.apache.org/r/67060/#comment285318]
>  
> We could revert the entire fix, however the simplest minimum change is to 
> remove the reference to the assembly from the distro pom. This means that the 
> binary is not placed into the distro directory, though the jar with 
> dependencies is still built in the component directory, and the assembly xml 
> file will still exist in distro.
> If we need to revert the entire fix please comment here and I'll update with 
> a new patch :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2693) Revert ATLAS-2668 for 1.0 branch

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2693:
---
Summary: Revert ATLAS-2668 for 1.0 branch  (was: Revert ATLAS-2699 for 1.0 
branch)

> Revert ATLAS-2668 for 1.0 branch
> 
>
> Key: ATLAS-2693
> URL: https://issues.apache.org/jira/browse/ATLAS-2693
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2699.patch
>
>
> Revert ATLAS-2668 for the 1.0 branch as per review 
> [https://reviews.apache.org/r/67060/#comment285318]
>  
> We could revert the entire fix, however the simplest minimum change is to 
> remove the reference to the assembly from the distro pom. This means that the 
> binary is not placed into the distro directory, though the jar with 
> dependencies is still built in the component directory, and the assembly xml 
> file will still exist in distro.
> If we need to revert the entire fix please comment here and I'll update with 
> a new patch :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2693) Revert ATLAS-2699 for 1.0 branch

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2693:
---
Attachment: ATLAS-2699.patch

> Revert ATLAS-2699 for 1.0 branch
> 
>
> Key: ATLAS-2693
> URL: https://issues.apache.org/jira/browse/ATLAS-2693
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2699.patch
>
>
> Revert ATLAS-2668 for the 1.0 branch as per review 
> [https://reviews.apache.org/r/67060/#comment285318]
>  
> We could revert the entire fix, however the simplest minimum change is to 
> remove the reference to the assembly from the distro pom. This means that the 
> binary is not placed into the distro directory, though the jar with 
> dependencies is still built in the component directory, and the assembly xml 
> file will still exist in distro.
> If we need to revert the entire fix please comment here and I'll update with 
> a new patch :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2693) Revert ATLAS-2699 for 1.0 branch

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2693:


added patch. testing build.

> Revert ATLAS-2699 for 1.0 branch
> 
>
> Key: ATLAS-2693
> URL: https://issues.apache.org/jira/browse/ATLAS-2693
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2699.patch
>
>
> Revert ATLAS-2668 for the 1.0 branch as per review 
> [https://reviews.apache.org/r/67060/#comment285318]
>  
> We could revert the entire fix, however the simplest minimum change is to 
> remove the reference to the assembly from the distro pom. This means that the 
> binary is not placed into the distro directory, though the jar with 
> dependencies is still built in the component directory, and the assembly xml 
> file will still exist in distro.
> If we need to revert the entire fix please comment here and I'll update with 
> a new patch :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2693) Revert ATLAS-2699 for 1.0 branch

[Nigel Jones (JIRA)]

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

Nigel Jones reassigned ATLAS-2693:
--

Assignee: Nigel Jones

> Revert ATLAS-2699 for 1.0 branch
> 
>
> Key: ATLAS-2693
> URL: https://issues.apache.org/jira/browse/ATLAS-2693
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> Revert ATLAS-2668 for the 1.0 branch as per review 
> [https://reviews.apache.org/r/67060/#comment285318]
>  
> We could revert the entire fix, however the simplest minimum change is to 
> remove the reference to the assembly from the distro pom. This means that the 
> binary is not placed into the distro directory, though the jar with 
> dependencies is still built in the component directory, and the assembly xml 
> file will still exist in distro.
> If we need to revert the entire fix please comment here and I'll update with 
> a new patch :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2693) Revert ATLAS-2699 for 1.0 branch

[Nigel Jones (JIRA)]

Nigel Jones created ATLAS-2693:
--

 Summary: Revert ATLAS-2699 for 1.0 branch
 Key: ATLAS-2693
 URL: https://issues.apache.org/jira/browse/ATLAS-2693
 Project: Atlas
  Issue Type: Improvement
Reporter: Nigel Jones


Revert ATLAS-2668 for the 1.0 branch as per review 
[https://reviews.apache.org/r/67060/#comment285318]

 

We could revert the entire fix, however the simplest minimum change is to 
remove the reference to the assembly from the distro pom. This means that the 
binary is not placed into the distro directory, though the jar with 
dependencies is still built in the component directory, and the assembly xml 
file will still exist in distro.

If we need to revert the entire fix please comment here and I'll update with a 
new patch :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2668) Add OMAG Server to distribution

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2668:
---
Attachment: (was: ATLAS-2668.patch)

> Add OMAG Server to distribution
> ---
>
> Key: ATLAS-2668
> URL: https://issues.apache.org/jira/browse/ATLAS-2668
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2668e.patch
>
>
> The standalone Open Metadata server is built under omag-server.
> However it is not incorporated into the distribution files (*.gz), and needs 
> careful attention to the classpath to work (ie launch from within IntelliJ)
> The intent of this Jira is
>  * have OMAG server available 'out of the box' in a binary distribution so 
> that users can easily launch it without having to check classpaths or run in 
> an odd environment
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2668) Add OMAG Server to distribution

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2668:


Updated patch to match review board

> Add OMAG Server to distribution
> ---
>
> Key: ATLAS-2668
> URL: https://issues.apache.org/jira/browse/ATLAS-2668
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2668e.patch
>
>
> The standalone Open Metadata server is built under omag-server.
> However it is not incorporated into the distribution files (*.gz), and needs 
> careful attention to the classpath to work (ie launch from within IntelliJ)
> The intent of this Jira is
>  * have OMAG server available 'out of the box' in a binary distribution so 
> that users can easily launch it without having to check classpaths or run in 
> an odd environment
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2668) Add OMAG Server to distribution

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2668:
---
Attachment: ATLAS-2668e.patch

> Add OMAG Server to distribution
> ---
>
> Key: ATLAS-2668
> URL: https://issues.apache.org/jira/browse/ATLAS-2668
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2668e.patch
>
>
> The standalone Open Metadata server is built under omag-server.
> However it is not incorporated into the distribution files (*.gz), and needs 
> careful attention to the classpath to work (ie launch from within IntelliJ)
> The intent of this Jira is
>  * have OMAG server available 'out of the box' in a binary distribution so 
> that users can easily launch it without having to check classpaths or run in 
> an odd environment
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2668) Add OMAG Server to distribution

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2668:


Now added to distribution assemblies.

Assembly includes main jar file & a new README.md which just documents how to 
launch OMAG Server

After patch installed new files are created: ie

17:18 $ ls
README.md omag-server-1.0.0-SNAPSHOT.jar
✔ 
~/src/atlas/distro/target/apache-atlas-1.0.0-SNAPSHOT-omag-server/omag-server-1.0.0-SNAPSHOT
 [master ↑·1|…1⚑ 3]

This mirrors the scheme used for other packages

 

A subsequent Jira could consider adding specific launch/terminate scripts for 
the omag server. Looking at the atlas scripts these make use of some common 
python libs which manages atlas config - in python (easier for platform 
independence) so suggest defer for now to consider what the requirements are. 
This Jira does make it easier to launch OMAG server with default settings.

> Add OMAG Server to distribution
> ---
>
> Key: ATLAS-2668
> URL: https://issues.apache.org/jira/browse/ATLAS-2668
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2668.patch
>
>
> The standalone Open Metadata server is built under omag-server.
> However it is not incorporated into the distribution files (*.gz), and needs 
> careful attention to the classpath to work (ie launch from within IntelliJ)
> The intent of this Jira is
>  * have OMAG server available 'out of the box' in a binary distribution so 
> that users can easily launch it without having to check classpaths or run in 
> an odd environment
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2668) Add OMAG Server to distribution

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2668:


Originally used the following pom.xml fragment which has worked before... but 
for other standalone apps. It doesn't work for spring, so I will use the spring 
framework version, but adding here as a useful note on making a standalone app 
with dependencies and main class identified




 
 org.apache.maven.plugins
 maven-shade-plugin
 3.1.1
 
 false
 
 
 
 package
 
 shade
 
 
 
 
 org.apache.atlas.omag.application.OMAGApplication
 
 
 
 
 
 


In this case I'll use 


 
 
 org.springframework.boot
 spring-boot-maven-plugin
 1.5.10.RELEASE
 
 
 
 repackage
 
 
 
 
 


This fragment will build a standalone jar, so we can now do:

✔ ~/src/atlas/omag-server/target [master|✚ 1⚑ 3]
14:07 $ ls
classes maven-shared-archive-resources original-omag-server-1.0.0-SNAPSHOT.jar
generated-sources maven-status rat.txt
maven-archiver omag-server-1.0.0-SNAPSHOT.jar test-classes
✔ ~/src/atlas/omag-server/target [master|✚ 1⚑ 3]
14:07 $ java -jar ./omag-server-1.0.0-SNAPSHOT.jar

.  _ __ _ _
 /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/ ___)| |_)| | | | | || (_| | ) ) ) )
 ' || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot :: (v1.0.0-SNAPSHOT)

2018-05-10 14:07:12.047 INFO 36215 --- [ main] 
o.a.a.omag.application.OMAGApplication : Starting OMAGApplication 
v1.0.0-SNAPSHOT on nigels-mbp.hursley.uk.ibm.com with PID 36215 
(/Users/jonesn/IdeaProjects/atlas/omag-server/target/omag-server-1.0.0-SNAPSHOT.jar
 started by jonesn in /Users/jonesn/IdeaProjects/atlas/omag-server/target)
2018-05-10 14:07:12.050 INFO 36215 --- [ main] 
o.a.a.omag.application.OMAGApplication : No active profile set, falling back to 
default profiles: default

 

etc ...

That's build done.
Next part - place somewhere in distribution...

> Add OMAG Server to distribution
> ---
>
> Key: ATLAS-2668
> URL: https://issues.apache.org/jira/browse/ATLAS-2668
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> The standalone Open Metadata server is built under omag-server.
> However it is not incorporated into the distribution files (*.gz), and needs 
> careful attention to the classpath to work (ie launch from within IntelliJ)
> The intent of this Jira is
>  * have OMAG server available 'out of the box' in a binary distribution so 
> that users can easily launch it without having to check classpaths or run in 
> an odd environment
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2668) Add OMAG Server to distribution

[Nigel Jones (JIRA)]

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

Nigel Jones reassigned ATLAS-2668:
--

Assignee: Nigel Jones

> Add OMAG Server to distribution
> ---
>
> Key: ATLAS-2668
> URL: https://issues.apache.org/jira/browse/ATLAS-2668
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> The standalone Open Metadata server is built under omag-server.
> However it is not incorporated into the distribution files (*.gz), and needs 
> careful attention to the classpath to work (ie launch from within IntelliJ)
> The intent of this Jira is
>  * have OMAG server available 'out of the box' in a binary distribution so 
> that users can easily launch it without having to check classpaths or run in 
> an odd environment
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2668) Add OMAG Server to distribution

[Nigel Jones (JIRA)]

Nigel Jones created ATLAS-2668:
--

 Summary: Add OMAG Server to distribution
 Key: ATLAS-2668
 URL: https://issues.apache.org/jira/browse/ATLAS-2668
 Project: Atlas
  Issue Type: Improvement
Reporter: Nigel Jones


The standalone Open Metadata server is built under omag-server.

However it is not incorporated into the distribution files (*.gz), and needs 
careful attention to the classpath to work (ie launch from within IntelliJ)



The intent of this Jira is
 * have OMAG server available 'out of the box' in a binary distribution so that 
users can easily launch it without having to check classpaths or run in an odd 
environment

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2569) maven dependency plugin back level - issues with dependency tree check

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2569.
--

> maven dependency plugin back level - issues with dependency tree check
> --
>
> Key: ATLAS-2569
> URL: https://issues.apache.org/jira/browse/ATLAS-2569
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2569.patch
>
>
> The maven dependency plugin is at v2, yet we are using maven v3. This can 
> lead to incorrect results when checking the dependency tree. 
> The error producted from 'mvn dependency:tree' includes:
> [INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ atlas-client-v1 
> ---
> [WARNING] Using Maven 2 dependency tree to get verbose output, which may be 
> inconsistent with actual Maven 3 resolution
> The fix is to update the plugin to a later version. Patch to be added. No 
> warnings are then produced, and we should be more sure of getting proper 
> dependency tree reporting



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2571) Maven: duplicate declarations

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2571.
--

> Maven: duplicate declarations
> -
>
> Key: ATLAS-2571
> URL: https://issues.apache.org/jira/browse/ATLAS-2571
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: ATLAS-2571.patch, ATLAS-2571.patch
>
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:atlas-graphdb-titan0:jar:1.0.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-solrj:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 194, column 21
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-core:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 200, column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hive-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hive-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hive-bridge/pom.xml, line 484, column 
> 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:falcon-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:falcon-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/falcon-bridge/pom.xml, line 370, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:sqoop-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:sqoop-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/sqoop-bridge/pom.xml, line 433, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:storm-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:storm-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/storm-bridge/pom.xml, line 536, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hbase-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hbase-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hbase-bridge/pom.xml, line 508, 
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> [https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html]
> [INFO] 
> 
>  
>  
> These are generally caused by duplicates - for example taking the first:
>  
> 
>  org.apache.solr
>  solr-solrj
> 
> 
>  org.apache.solr
>  solr-solrj
>  ${solr.version}
> 
>  
> So we have it declared twice, once pulling in solr.version - defined in the 
> top level pom, and the other blank. In the case of this plugin, the version 
> is not declared in any DependencyManagement section (the common way of 
> defining default plugin versions which can then be overriden in child poms)
> Cleaning this up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2593) Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2593:


Added first patch. 



- Based on outline provided in omas-connectedasset & omas-assetconsumer
 - Provides framework for two initial API calls
 - Not executed/tested/no unit tests so far
 - No implementation to retrieve actual tags/classifications from metadata store
 - lots of todos/further reading through/checks

will post on review board once API calls work (even returning dummys)

> Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework
> --
>
> Key: ATLAS-2593
> URL: https://issues.apache.org/jira/browse/ATLAS-2593
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2593.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2593) Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2593:
---
Attachment: ATLAS-2593.patch

> Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework
> --
>
> Key: ATLAS-2593
> URL: https://issues.apache.org/jira/browse/ATLAS-2593
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2593.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2601) OMAG server Swagger

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2601:


It does seem as if enunciate and swagger are broadly comparable. In terms of 
build there are some advantages I think to the current enunciate approach if 
[https://stackoverflow.com/questions/43249895/generating-swagger-json-for-spring-mvc-springfox-or-enunciate]
 is correct, especially as it seems less annotations are needed?

Overall  I agree it's better to have one mechanism unless there are very clear 
advantages in having two - or moving to springfox for the base atlas code.

> OMAG server Swagger 
> 
>
> Key: ATLAS-2601
> URL: https://issues.apache.org/jira/browse/ATLAS-2601
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Maryna Strelchuk
>Assignee: Maryna Strelchuk
>Priority: Major
> Attachments: 0001-Atlas-2601-OMAG-server-Swagger.patch
>
>
> This Jira addresses the addition of the Swagger for the OMAG server. 
> Currently Swagger was added as a dependency for
>  * omag-server
>  * omag-api
>  * omas-connectedasset



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2595) Improve version consistency in POMs (omas, omrs...)

[Nigel Jones (JIRA)]

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

Nigel Jones reassigned ATLAS-2595:
--

Assignee: Nigel Jones

> Improve version consistency in POMs (omas, omrs...)
> ---
>
> Key: ATLAS-2595
> URL: https://issues.apache.org/jira/browse/ATLAS-2595
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> In maven projects generally, the  or  
> tags can be used to provide some generic attributes for plugins, versions of 
> dependencies etc in a top level pom, and then child poms no longer need to 
> specify, unless they wish to override.
> Some components in atlas take a different approach, by setting an explicit 
> version in a property in the top level pom, and then using this variable in 
> the child pom.
> The current omrs, omas poms tend to explicitly refer to version, which can 
> lead to more inconsistency by mistake (they can override if essential for 
> function), so this Jira is being opened to consolidate



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2595) Improve version consistency in POMs (omas, omrs...)

[Nigel Jones (JIRA)]

Nigel Jones created ATLAS-2595:
--

 Summary: Improve version consistency in POMs (omas, omrs...)
 Key: ATLAS-2595
 URL: https://issues.apache.org/jira/browse/ATLAS-2595
 Project: Atlas
  Issue Type: Improvement
Reporter: Nigel Jones


In maven projects generally, the  or  
tags can be used to provide some generic attributes for plugins, versions of 
dependencies etc in a top level pom, and then child poms no longer need to 
specify, unless they wish to override.

Some components in atlas take a different approach, by setting an explicit 
version in a property in the top level pom, and then using this variable in the 
child pom.

The current omrs, omas poms tend to explicitly refer to version, which can lead 
to more inconsistency by mistake (they can override if essential for function), 
so this Jira is being opened to consolidate



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-1973) gaf omas : high level swagger API + supporting doc

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-1973.
--

> gaf omas : high level swagger API + supporting doc
> --
>
> Key: ATLAS-1973
> URL: https://issues.apache.org/jira/browse/ATLAS-1973
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Priority: Major
>
> Complete/update swagger.io high level definition of api (yaml)
> Add supporting notes as documentation 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-1974) goveng omas : create skeleton implementation + generated swagger

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-1974.
--

> goveng omas : create skeleton implementation + generated swagger
> 
>
> Key: ATLAS-1974
> URL: https://issues.apache.org/jira/browse/ATLAS-1974
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> In this task I'll take the previously generated definition in yaml & take the 
> first step to making it closer to implementation by creating the appropriate 
> directory structure, maven projects & java classes which would generate the 
> interface & generate swagger output



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2234) Unit test failures in NotificationHookConsumerTest.java

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2234.
--

> Unit test failures in NotificationHookConsumerTest.java
> ---
>
> Key: ATLAS-2234
> URL: https://issues.apache.org/jira/browse/ATLAS-2234
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nigel Jones
>Priority: Major
>
> Have been seeing this unit test failure for a while on my local MacOS builds 
> off master.
> Running org.apache.atlas.notification.NotificationHookConsumerTest
> Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.46 sec <<< 
> FAILURE! - in org.apache.atlas.notification.NotificationHookConsumerTest
> consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted(org.apache.atlas.notification.NotificationHookConsumerTest)
>   Time elapsed: 2.52 sec  <<< FAILURE!
> java.lang.AssertionError: expected [false] but found [true]
>   at org.testng.Assert.fail(Assert.java:94)
>   at org.testng.Assert.failNotEquals(Assert.java:496)
>   at org.testng.Assert.assertFalse(Assert.java:63)
>   at org.testng.Assert.assertFalse(Assert.java:73)
>   at 
> org.apache.atlas.notification.NotificationHookConsumerTest.consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted(NotificationHookConsumerTest.java:290)
> 
> Results :
> Failed tests: 
>   
> NotificationHookConsumerTest.consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted:290
>  expected [false] but found [true]
> Tests run: 79, Failures: 1, Errors: 0, Skipped: 0
> 
> [INFO] Apache Atlas UI  SUCCESS [ 57.722 
> s]
> [INFO] Apache Atlas Web Application ... FAILURE [ 51.658 
> s]
> [INFO] Apache Atlas Documentation . SKIPPED
> this came up again whilst verifying another fix. Opening, will return after 
> completing the other changes.
> It appears this is likely a timing issue probably due to 2500ms vs 500ms.. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-637) Build fails (jenkins, local)

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-637.
-

> Build fails (jenkins, local)
> 
>
> Key: ATLAS-637
> URL: https://issues.apache.org/jira/browse/ATLAS-637
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Nigel Jones
>Priority: Blocker
>
> I am seeing the Atlas build fail when building the Web UI on 2 local (linux) 
> systems of mine. Whilst about to debug I noticed that Apache jenkins is also 
> reporting a build failure on the mailing list as reported at 
> news://news.gmane.org:119/579606293.2657.1459820983173.JavaMail.jenkins@crius
> The jenkins report seems very similar to mine, so I paste that below, and 
> will add further info from my local install attempt:
> See 
> Changes:
> [sumasai.shivaprasad] ATLAS-571 Modify Atlas client for necessary changes in 
> context of HA
> [sumasai.shivaprasad] ATLAS-607 Add Support for delete entity through a 
> qualifiedName (sumasai
> --
> [...truncated 5060 lines...]
> [ERROR] npm http 200 https://registry.npmjs.org/serve-static
> [ERROR] npm http 200 
> https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-1.0.0.tgz
> [ERROR] npm http 200 https://registry.npmjs.org/finalhandler/0.3.6
> [ERROR] npm http 304 https://registry.npmjs.org/escape-html/1.0.1
> [ERROR] npm http 304 https://registry.npmjs.org/etag
> [ERROR] npm http 200 https://registry.npmjs.org/content-disposition/0.5.0
> [ERROR] npm http GET https://registry.npmjs.org/ansi-regex
> [ERROR] npm http GET https://registry.npmjs.org/ansi-regex
> [ERROR] npm http GET https://registry.npmjs.org/get-stdin
> [ERROR] npm http 304 https://registry.npmjs.org/on-finished
> [ERROR] npm http GET 
> https://registry.npmjs.org/finalhandler/-/finalhandler-0.3.6.tgz
> [ERROR] npm http GET 
> https://registry.npmjs.org/serve-static/-/serve-static-1.9.3.tgz
> [ERROR] npm http GET 
> https://registry.npmjs.org/content-disposition/-/content-disposition-0.5.0.tgz
> [ERROR] npm http 304 https://registry.npmjs.org/parseurl
> [ERROR] npm http GET https://registry.npmjs.org/etag/-/etag-1.6.0.tgz
> [ERROR] npm http 200 https://registry.npmjs.org/qs/-/qs-2.4.2.tgz
> [ERROR] npm http 304 https://registry.npmjs.org/type-is
> [ERROR] npm http 304 https://registry.npmjs.org/vary
> [ERROR] npm http GET 
> https://registry.npmjs.org/on-finished/-/on-finished-2.2.1.tgz
> [ERROR] npm http 200 https://registry.npmjs.org/send/0.12.3
> [ERROR] npm http 304 https://registry.npmjs.org/utils-merge/1.0.0
> [ERROR] npm http 200 
> https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-0.1.3.tgz
> [ERROR] npm http 304 https://registry.npmjs.org/accepts
> [ERROR] npm http 200 https://registry.npmjs.org/depd/-/depd-1.0.1.tgz
> [ERROR] npm http GET https://registry.npmjs.org/send/-/send-0.12.3.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/content-disposition/-/content-disposition-0.5.0.tgz
> [ERROR] npm http 304 https://registry.npmjs.org/ansi-regex
> [ERROR] npm http 304 https://registry.npmjs.org/ansi-regex
> [ERROR] npm http 304 https://registry.npmjs.org/get-stdin
> [ERROR] npm http 200 https://registry.npmjs.org/etag/-/etag-1.6.0.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/on-finished/-/on-finished-2.2.1.tgz
> [ERROR] npm http 200 https://registry.npmjs.org/send/-/send-0.12.3.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/finalhandler/-/finalhandler-0.3.6.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/serve-static/-/serve-static-1.9.3.tgz
> [ERROR] npm http GET https://registry.npmjs.org/crc32-stream
> [ERROR] npm http GET https://registry.npmjs.org/node-int64
> [ERROR] npm http 200 https://registry.npmjs.org/node-int64
> [ERROR] npm http 200 https://registry.npmjs.org/crc32-stream
> [ERROR] npm http GET 
> https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz
> [ERROR] npm http GET 
> https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz
> [ERROR] npm http GET https://registry.npmjs.org/crc/3.2.1
> [ERROR] npm http GET https://registry.npmjs.org/ee-first/1.1.0
> [ERROR] npm http GET https://registry.npmjs.org/forwarded
> [ERROR] npm http GET https://registry.npmjs.org/ipaddr.js/1.0.5
> [ERROR] npm http GET https://registry.npmjs.org/negotiator/0.5.3
> [ERROR] npm http GET https://registry.npmjs.org/media-typer/0.3.0
> [ERROR] npm http GET https://registry.npmjs.org/mime-types
> [ERROR] npm http GET https://registry.npmjs.org/mime-types
> [ERROR] npm http GET https://registry.npmjs.org/destroy/1.0.3
> [ERROR] npm http GET 

[jira] [Closed] (ATLAS-1356) ATLAS4091E in webapp Unit Tests

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-1356.
--

> ATLAS4091E in webapp Unit Tests 
> 
>
> Key: ATLAS-1356
> URL: https://issues.apache.org/jira/browse/ATLAS-1356
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: Ubuntu 16.10, Open JDK  1.8.0_111
>Reporter: Nigel Jones
>Priority: Major
> Attachments: atlas20161207e.log
>
>
> Tests run: 6, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 2.74 sec <<< 
> FAI LURE! - in 
> org.apache.atlas.web.resources.TypedefsJerseyResourceIT
> testCreate(org.apache.atlas.web.resources.TypedefsJerseyResourceIT)  Time 
> elapse d: 0.262 sec  <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API 
> org.apache.atlas.At 
> lasBaseClient$APIInfo@2474f125 failed with status 409 (Conflict) Response 
> Body ( 
> {"errorCode":"ATLAS4091E","errorMessage":"Given type fetl already exists"})
> at 
> org.apache.atlas.web.resources.TypedefsJerseyResourceIT.testCreate(Ty 
> pedefsJerseyResourceIT.java:87)
> This happens with a clean clone. Full log to be attached



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-1356) ATLAS4091E in webapp Unit Tests

[Nigel Jones (JIRA)]

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

Nigel Jones resolved ATLAS-1356.

Resolution: Cannot Reproduce

> ATLAS4091E in webapp Unit Tests 
> 
>
> Key: ATLAS-1356
> URL: https://issues.apache.org/jira/browse/ATLAS-1356
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: Ubuntu 16.10, Open JDK  1.8.0_111
>Reporter: Nigel Jones
>Priority: Major
> Attachments: atlas20161207e.log
>
>
> Tests run: 6, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 2.74 sec <<< 
> FAI LURE! - in 
> org.apache.atlas.web.resources.TypedefsJerseyResourceIT
> testCreate(org.apache.atlas.web.resources.TypedefsJerseyResourceIT)  Time 
> elapse d: 0.262 sec  <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API 
> org.apache.atlas.At 
> lasBaseClient$APIInfo@2474f125 failed with status 409 (Conflict) Response 
> Body ( 
> {"errorCode":"ATLAS4091E","errorMessage":"Given type fetl already exists"})
> at 
> org.apache.atlas.web.resources.TypedefsJerseyResourceIT.testCreate(Ty 
> pedefsJerseyResourceIT.java:87)
> This happens with a clean clone. Full log to be attached



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-1158) Build ATLAS using Docker

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-1158.
--

> Build ATLAS using Docker
> 
>
> Key: ATLAS-1158
> URL: https://issues.apache.org/jira/browse/ATLAS-1158
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.8-incubating
>Reporter: Nigel Jones
>Assignee: Qiang Zhang
>Priority: Major
>  Labels: VirtualDataConnector
> Attachments: build_atlas_using_docker.sh
>
>
> In RANGER-1137 ( https://issues.apache.org/jira/browse/RANGER-1137 ) there is 
> a proposal to build ranger using docker in order to avoid environment issues. 
> (though note it's a unix based shell script)
> Some new users to Atlas have had difficulties building the code, so it could 
> be a cool idea to do something similar for Atlas?
> Happy to give it a go though I suspect some of the unit test issues with 
> timeouts may still be hit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-1849) Atlas should prereq Java 8

[Nigel Jones (JIRA)]

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

Nigel Jones resolved ATLAS-1849.

Resolution: Fixed

> Atlas should prereq Java 8
> --
>
> Key: ATLAS-1849
> URL: https://issues.apache.org/jira/browse/ATLAS-1849
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Priority: Major
>
> Atlas should move to assume Java 8 in order to remain current
> Java 7's last official release was in April 2015
> Java 8 was released in March 2014 and is the current release
> Java 9 is currently targetted for release in July 2017
> Various new components we wish to integrate, such as Janus Graph now quite 
> sensibly depend on, and can take advantage of, Java 8. Whilst Atlas does 
> build cleanly under java 8, the new capabilities cannot be used and more 
> crucially any components requiring it can't be so easily integrated into the 
> source. With Java 7 way out of focus there are more likely to be security 
> exposures too.
> One of the current main environments Atlas is supported in is Hadoop. Hadoop 
> 2.x is build with Java 7, though the very latest releases do at least support 
> build with Java 8. Hadoop 3 which prereqs java 8 is due for release in August 
> 2017
> However other environments in the enterprise need not be constrained by this 
> dependency
> We need to decide how we will tackle this dependency change & mitigate the 
> impacts - for example
>  * we stay as-is until hadoop 3 is current/into 2018 (in my view too long)
>  * we go all out on java 8 in the current trunk, and branches are cut for 
> java 7 approach (I worry this is too much work to dual-fix)
>  * we create multiple build profiles and carefully allow java8 code in as 
> needed, but in such a way as a java7 version can still be built, albeit 
> missing out on selective functionality - this could still be tricky, and has 
> run-time dependency differences
>  * if profiles we decide on default (once working I'd suggest 8...)
> Thoughts welcome :-)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-1849) Atlas should prereq Java 8

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-1849.
--

> Atlas should prereq Java 8
> --
>
> Key: ATLAS-1849
> URL: https://issues.apache.org/jira/browse/ATLAS-1849
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Priority: Major
>
> Atlas should move to assume Java 8 in order to remain current
> Java 7's last official release was in April 2015
> Java 8 was released in March 2014 and is the current release
> Java 9 is currently targetted for release in July 2017
> Various new components we wish to integrate, such as Janus Graph now quite 
> sensibly depend on, and can take advantage of, Java 8. Whilst Atlas does 
> build cleanly under java 8, the new capabilities cannot be used and more 
> crucially any components requiring it can't be so easily integrated into the 
> source. With Java 7 way out of focus there are more likely to be security 
> exposures too.
> One of the current main environments Atlas is supported in is Hadoop. Hadoop 
> 2.x is build with Java 7, though the very latest releases do at least support 
> build with Java 8. Hadoop 3 which prereqs java 8 is due for release in August 
> 2017
> However other environments in the enterprise need not be constrained by this 
> dependency
> We need to decide how we will tackle this dependency change & mitigate the 
> impacts - for example
>  * we stay as-is until hadoop 3 is current/into 2018 (in my view too long)
>  * we go all out on java 8 in the current trunk, and branches are cut for 
> java 7 approach (I worry this is too much work to dual-fix)
>  * we create multiple build profiles and carefully allow java8 code in as 
> needed, but in such a way as a java7 version can still be built, albeit 
> missing out on selective functionality - this could still be tricky, and has 
> run-time dependency differences
>  * if profiles we decide on default (once working I'd suggest 8...)
> Thoughts welcome :-)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2084) Make berkeley DB backed Atlas available without external download

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2084.
--

> Make berkeley DB backed Atlas available without external download
> -
>
> Key: ATLAS-2084
> URL: https://issues.apache.org/jira/browse/ATLAS-2084
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS_2084_Add_BerkeleyDB_libraries.patch
>
>
> In https://issues.apache.org/jira/browse/ATLAS-2012 I proposed providing a 
> dockerized version of Atlas to aid people getting up to speed with the 
> technology. During the review it was noted that we had used Hbase for storage 
> rather than the more lightweight, simpler, BerkeleyDB. My concern had been 
> around licensing.
> Today when we build Atlas following the instructions at 
> http://atlas.apache.org/InstallationSteps.html the user is directed to 
> download the berkeleyDB jar from oracle. In ATLAS-2012 David/Graham pointed 
> out that this DB appears to be Apache 2.0 licensed, which means we could 
> incorporate it into our build legitimately.
> Given the necessity to get licensing correct I've opened up this new JIRA to 
> focus on that change. We would need to
>  * Validate we are indeed correct about the license
>  * Add the DB file into the build
>  * Update the web instructions
>  * And optionally as per the original JIRA, consider making B-DB the default 
> for our docker image (most lightweight).
> Please add your thoughts. I'm happy to get and do this change .



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2049) Document common standards for OMAS interfaces

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2049.
--

> Document common standards for OMAS interfaces
> -
>
> Key: ATLAS-2049
> URL: https://issues.apache.org/jira/browse/ATLAS-2049
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2049.patch
>
>
> Document (and review) common standards for OMAS interfaces, so as to ensure 
> some consistency between the multiple OMASs being developed.
> As per phone discussion with some of team on 15 Aug will create this list in 
> a text-like format (perhaps twiki) and review using review board tool.
> Since this will then form documentation for ATlas (internal) developers it 
> may make sense to create as a permanent part of the twiki docs, though if so 
> we may wish to consider adding other related information there such as 
> architectural explanations of omrs, omas etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2226) ATLAS build fails (20171025) - macos

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2226.
--

> ATLAS build fails (20171025) - macos
> 
>
> Key: ATLAS-2226
> URL: https://issues.apache.org/jira/browse/ATLAS-2226
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nigel Jones
>Priority: Major
>
> I refreshed my build environment today, and noted that atlas fails to build 
> (for embedded hbase/solr). I took a fresh git clone to confirm. JDK was 
> updated to the 152 fix level (java 8) a few days ago. Maven is at 3.5 for me 
> and may need to be updated.
> 11:51 $ git clone git://git.apache.org/atlas.git atlas2
> Cloning into 'atlas2'...
> remote: Counting objects: 55084, done.
> remote: Compressing objects: 100% (18742/18742), done.
> remote: Total 55084 (delta 24065), reused 49458 (delta 21532)
> Receiving objects: 100% (55084/55084), 33.37 MiB | 7.29 MiB/s, done.
> Resolving deltas: 100% (24065/24065), done.
> ✔ ~/src 
> 11:51 $ cd atlas2
> ✔ ~/src/atlas2 [master|✔] 
> 11:51 $ mvn clean package -Pdist,external-hbase-solr 2>&1 ~ tee 
> ../20171025a.log
> [INFO] Scanning for projects...
> [WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache Atlas Server Build Tools
> [INFO] apache-atlas
> [INFO] Apache Atlas Integration
> [INFO] Apache Atlas Common
> [INFO] Apache Atlas Typesystem
> [INFO] Apache Atlas Client
> [INFO] atlas-client-common
> [INFO] atlas-client-v1
> [INFO] Apache Atlas Server API
> [INFO] Apache Atlas Notification
> [INFO] atlas-client-v2
> [INFO] Apache Atlas Graph Database Projects
> [INFO] Apache Atlas Graph Database API
> [INFO] Graph Database Common Code
> [INFO] Apache Atlas Titan 1.0.0 GraphDB Impl
> [INFO] Shaded version of Apache hbase client
> [INFO] Apache Atlas Titan 0.5.4 Graph DB Impl
> [INFO] Apache Atlas Graph Database Implementation Dependencies
> [INFO] Shaded version of Apache hbase server
> [INFO] Apache Atlas Repository
> [INFO] Apache Atlas Authorization
> [INFO] Apache Atlas UI
> [INFO] Apache Atlas Web Application
> [INFO] Apache Atlas Documentation
> [INFO] Apache Atlas FileSystem Model
> [INFO] Apache Atlas Plugin Classloader
> [INFO] Apache Atlas Hive Bridge Shim
> [INFO] Apache Atlas Hive Bridge
> [INFO] Apache Atlas Falcon Bridge Shim
> [INFO] Apache Atlas Falcon Bridge
> [INFO] Apache Atlas Sqoop Bridge Shim
> [INFO] Apache Atlas Sqoop Bridge
> [INFO] Apache Atlas Storm Bridge Shim
> [INFO] Apache Atlas Storm Bridge
> [INFO] Apache Atlas Hbase Bridge Shim
> [INFO] Apache Atlas Hbase Bridge
> [INFO] Apache Atlas Distribution
> [INFO] 
> [INFO] 
> 
> [INFO] Building Apache Atlas Server Build Tools 1.0
> [INFO] 
> 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Atlas Server Build Tools  FAILURE [  0.002 
> s]
> [INFO] apache-atlas ... SKIPPED
> [INFO] Apache Atlas Integration ... SKIPPED
> [INFO] Apache Atlas Common  SKIPPED
> [INFO] Apache Atlas Typesystem  SKIPPED
> [INFO] Apache Atlas Client  SKIPPED
> [INFO] atlas-client-common  SKIPPED
> [INFO] atlas-client-v1  SKIPPED
> [INFO] Apache Atlas Server API  SKIPPED
> [INFO] Apache Atlas Notification .. SKIPPED
> [INFO] atlas-client-v2  SKIPPED
> [INFO] Apache Atlas Graph Database Projects ... SKIPPED
> [INFO] Apache Atlas Graph Database API  SKIPPED
> [INFO] Graph Database Common Code . SKIPPED
> [INFO] Apache Atlas Titan 1.0.0 GraphDB Impl .. SKIPPED
> [INFO] Shaded version of Apache hbase client .. SKIPPED
> [INFO] Apache Atlas Titan 0.5.4 Graph DB Impl . SKIPPED
> [INFO] Apache Atlas Graph Database Implementation Dependencies SKIPPED
> [INFO] Shaded version of Apache hbase server .. SKIPPED
> [INFO] Apache Atlas Repository  SKIPPED
> [INFO] Apache Atlas Authorization . SKIPPED
> [INFO] Apache Atlas 

[jira] [Resolved] (ATLAS-2096) Integration Test fails: Given Type Dimension already exists

[Nigel Jones (JIRA)]

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

Nigel Jones resolved ATLAS-2096.

Resolution: Cannot Reproduce

> Integration Test fails: Given Type Dimension already exists
> ---
>
> Key: ATLAS-2096
> URL: https://issues.apache.org/jira/browse/ATLAS-2096
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nigel Jones
>Priority: Major
>
> When building Atlas for hbase/embedded solo I hit a UT failure during the web 
> app tests:
> 127.0.0.1 - - [29/Aug/2017:17:33:22 +] "GET 
> /api/atlas/entities/6cb20ab1-00c2-4e80-a2dc-dfb7a20c90e3 HTTP/1.1" 200 - "-" 
> "Java/1.8.0_144"
> 127.0.0.1 - - [29/Aug/2017:17:33:22 +] "POST 
> /api/atlas/entities/6cb20ab1-00c2-4e80-a2dc-dfb7a20c90e3?property=invalid_property
>  HTTP/1.1" 400 - "-" "Java/1.8.0_144"
> 127.0.0.1 - - [29/Aug/2017:17:33:22 +] "GET 
> /api/atlas/entities/6cb20ab1-00c2-4e80-a2dc-dfb7a20c90e3 HTTP/1.1" 200 - "-" 
> "Java/1.8.0_144"
> 127.0.0.1 - - [29/Aug/2017:17:33:23 +] "POST 
> /api/atlas/v2/types/typedefs/ HTTP/1.1" 409 - "-" "Java/1.8.0_144"
> Tests run: 134, Failures: 1, Errors: 0, Skipped: 5, Time elapsed: 80.922 sec 
> <<< FAILURE! - in TestSuite
> runQuickStart(org.apache.atlas.examples.QuickStartV2IT)  Time elapsed: 0.387 
> sec  <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API 
> org.apache.atlas.AtlasBaseClient$APIInfo@1bd893c7 failed with status 409 
> (Conflict) Response Body 
> ({"errorCode":"ATLAS-409-00-001","errorMessage":"Given type Dimension already 
> exists"})
>   at 
> org.apache.atlas.examples.QuickStartV2IT.runQuickStart(QuickStartV2IT.java:49)
> Results :
> Failed tests: 
>   QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API 
> org.apache...
> Tests run: 134, Failures: 1, Errors: 0, Skipped: 5
> [INFO] 
> [INFO] --- jetty-maven-plugin:9.2.12.v20150709:stop (stop-jetty) @ 
> atlas-webapp --- 
> This was reported in the mailing list at 
> https://lists.apache.org/thread.html/9db9d8668f22a2cdd58dd42fb582e026e07703c7ec6e9ae0e7d53f69@%3Cdev.atlas.apache.org%3E
> Subsequently noticed this is failing (intermittently) on the Jenkins build 
> too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2096) Integration Test fails: Given Type Dimension already exists

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2096.
--

> Integration Test fails: Given Type Dimension already exists
> ---
>
> Key: ATLAS-2096
> URL: https://issues.apache.org/jira/browse/ATLAS-2096
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nigel Jones
>Priority: Major
>
> When building Atlas for hbase/embedded solo I hit a UT failure during the web 
> app tests:
> 127.0.0.1 - - [29/Aug/2017:17:33:22 +] "GET 
> /api/atlas/entities/6cb20ab1-00c2-4e80-a2dc-dfb7a20c90e3 HTTP/1.1" 200 - "-" 
> "Java/1.8.0_144"
> 127.0.0.1 - - [29/Aug/2017:17:33:22 +] "POST 
> /api/atlas/entities/6cb20ab1-00c2-4e80-a2dc-dfb7a20c90e3?property=invalid_property
>  HTTP/1.1" 400 - "-" "Java/1.8.0_144"
> 127.0.0.1 - - [29/Aug/2017:17:33:22 +] "GET 
> /api/atlas/entities/6cb20ab1-00c2-4e80-a2dc-dfb7a20c90e3 HTTP/1.1" 200 - "-" 
> "Java/1.8.0_144"
> 127.0.0.1 - - [29/Aug/2017:17:33:23 +] "POST 
> /api/atlas/v2/types/typedefs/ HTTP/1.1" 409 - "-" "Java/1.8.0_144"
> Tests run: 134, Failures: 1, Errors: 0, Skipped: 5, Time elapsed: 80.922 sec 
> <<< FAILURE! - in TestSuite
> runQuickStart(org.apache.atlas.examples.QuickStartV2IT)  Time elapsed: 0.387 
> sec  <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API 
> org.apache.atlas.AtlasBaseClient$APIInfo@1bd893c7 failed with status 409 
> (Conflict) Response Body 
> ({"errorCode":"ATLAS-409-00-001","errorMessage":"Given type Dimension already 
> exists"})
>   at 
> org.apache.atlas.examples.QuickStartV2IT.runQuickStart(QuickStartV2IT.java:49)
> Results :
> Failed tests: 
>   QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API 
> org.apache...
> Tests run: 134, Failures: 1, Errors: 0, Skipped: 5
> [INFO] 
> [INFO] --- jetty-maven-plugin:9.2.12.v20150709:stop (stop-jetty) @ 
> atlas-webapp --- 
> This was reported in the mailing list at 
> https://lists.apache.org/thread.html/9db9d8668f22a2cdd58dd42fb582e026e07703c7ec6e9ae0e7d53f69@%3Cdev.atlas.apache.org%3E
> Subsequently noticed this is failing (intermittently) on the Jenkins build 
> too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2233) Java 8 no longer supports MaxPermSize -- noise in logs

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2233.
--

> Java 8 no longer supports MaxPermSize -- noise in logs
> --
>
> Key: ATLAS-2233
> URL: https://issues.apache.org/jira/browse/ATLAS-2233
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2233.patch, Screen Shot 2017-10-26 at 12.56.54.png
>
>
> Now that we only support Java 8 we should remove references to 
> -XX:MaxPermSize in the poms, scripts, documents, wiki.
> The build log is littered with
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
> support was removed in 8.0
> The included image gives the results of a quick search



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-2234) Unit test failures in NotificationHookConsumerTest.java

[Nigel Jones (JIRA)]

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

Nigel Jones resolved ATLAS-2234.

Resolution: Cannot Reproduce

> Unit test failures in NotificationHookConsumerTest.java
> ---
>
> Key: ATLAS-2234
> URL: https://issues.apache.org/jira/browse/ATLAS-2234
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nigel Jones
>Priority: Major
>
> Have been seeing this unit test failure for a while on my local MacOS builds 
> off master.
> Running org.apache.atlas.notification.NotificationHookConsumerTest
> Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.46 sec <<< 
> FAILURE! - in org.apache.atlas.notification.NotificationHookConsumerTest
> consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted(org.apache.atlas.notification.NotificationHookConsumerTest)
>   Time elapsed: 2.52 sec  <<< FAILURE!
> java.lang.AssertionError: expected [false] but found [true]
>   at org.testng.Assert.fail(Assert.java:94)
>   at org.testng.Assert.failNotEquals(Assert.java:496)
>   at org.testng.Assert.assertFalse(Assert.java:63)
>   at org.testng.Assert.assertFalse(Assert.java:73)
>   at 
> org.apache.atlas.notification.NotificationHookConsumerTest.consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted(NotificationHookConsumerTest.java:290)
> 
> Results :
> Failed tests: 
>   
> NotificationHookConsumerTest.consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted:290
>  expected [false] but found [true]
> Tests run: 79, Failures: 1, Errors: 0, Skipped: 0
> 
> [INFO] Apache Atlas UI  SUCCESS [ 57.722 
> s]
> [INFO] Apache Atlas Web Application ... FAILURE [ 51.658 
> s]
> [INFO] Apache Atlas Documentation . SKIPPED
> this came up again whilst verifying another fix. Opening, will return after 
> completing the other changes.
> It appears this is likely a timing issue probably due to 2500ms vs 500ms.. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2570) OMRSRepositoryValidator refers to sun.* class

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2570.
--

> OMRSRepositoryValidator refers to sun.* class
> -
>
> Key: ATLAS-2570
> URL: https://issues.apache.org/jira/browse/ATLAS-2570
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
> Attachments: ATLAS-2570.patch
>
>
> I noticed that this class was referring to old deprecated sun packages.
> import sun.misc.Regexp;
> Fortunately this package was not used, so it is a very minor fixup, but good 
> not to accidentally start using any private/deprecated packages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2488.
--

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2488-1.patch, ATLAS-2488-2.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ATLAS-2245) Update Maven dependency in build to 3.5.0

[Nigel Jones (JIRA)]

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

Nigel Jones closed ATLAS-2245.
--

> Update Maven dependency in build to 3.5.0
> -
>
> Key: ATLAS-2245
> URL: https://issues.apache.org/jira/browse/ATLAS-2245
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
> Attachments: ATLAS-2245-4.patch
>
>
> The version of maven on the jenkins build was recently updated to address 
> some build issues.
> It seems a few people have hit maven issues so I now propose we update the 
> main build dependency to 3.5.0 as this is currently in the top level pom as
> 
> 3.0.4
> 
> and change to 3.5.0
> The very latest is 3.5.2, but since jenkins is now at 3.5.0 and is known 
> working, plus homebrew (mac) at least only goes as far as 3.5.0, I suggest we 
> go with that as a prereq. 3.5.2 will work as well 
> A search through the source tree shows this is the only occurance, so this is 
> a one file change
> NOTE: There is an impact to users, who need to upgrade to maven 3.5. I will 
> shortly check the wiki docs and would propose an email to the mailing list 
> remining developers to pull the latest maven 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2593) Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework

[Nigel Jones (JIRA)]

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

Nigel Jones reassigned ATLAS-2593:
--

Assignee: Nigel Jones

> Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework
> --
>
> Key: ATLAS-2593
> URL: https://issues.apache.org/jira/browse/ATLAS-2593
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-1974) goveng omas : create skeleton implementation + generated swagger

[Nigel Jones (JIRA)]

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

Nigel Jones resolved ATLAS-1974.

Resolution: Fixed

closing this - was based on old code patterns 

> goveng omas : create skeleton implementation + generated swagger
> 
>
> Key: ATLAS-1974
> URL: https://issues.apache.org/jira/browse/ATLAS-1974
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> In this task I'll take the previously generated definition in yaml & take the 
> first step to making it closer to implementation by creating the appropriate 
> directory structure, maven projects & java classes which would generate the 
> interface & generate swagger output



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2593) Governance Engine OMAS - skeleton based on new omrs/omas patterns/ & framework

[Nigel Jones (JIRA)]

Nigel Jones created ATLAS-2593:
--

 Summary: Governance Engine OMAS - skeleton based on new omrs/omas 
patterns/ & framework
 Key: ATLAS-2593
 URL: https://issues.apache.org/jira/browse/ATLAS-2593
 Project: Atlas
  Issue Type: Sub-task
Reporter: Nigel Jones






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-1694) Sample assets to support Virtual Connector Project

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-1694:


Some sample data has been posted into

[https://github.com/GaianRangerPlugin/ranger-gaian-plugin/tree/master/SampleData]

as part of supporting the vdc work. This includes spreadsheets, csv files for 
data, and scripts to create for db2 & mariadb/mysql.

If anyone is interested in this I could add to atlas, but not sure if it's 
useful at this point. For now the update/link may help anyone looking for vdc 
info/data/examples

> Sample assets to support Virtual Connector Project
> --
>
> Key: ATLAS-1694
> URL: https://issues.apache.org/jira/browse/ATLAS-1694
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>  Labels: VirtualDataConnector
>
> Assets to support the virtual data connector project as samples
> for example
>  - sample data
>  - sample rules/policies/classifications
>  - tools
>  - integration for GaianDB (open source virtualization engine)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-2570) OMRSRepositoryValidator refers to sun.* class

[Nigel Jones (JIRA)]

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

Nigel Jones resolved ATLAS-2570.

Resolution: Fixed

> OMRSRepositoryValidator refers to sun.* class
> -
>
> Key: ATLAS-2570
> URL: https://issues.apache.org/jira/browse/ATLAS-2570
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
> Attachments: ATLAS-2570.patch
>
>
> I noticed that this class was referring to old deprecated sun packages.
> import sun.misc.Regexp;
> Fortunately this package was not used, so it is a very minor fixup, but good 
> not to accidentally start using any private/deprecated packages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2570) OMRSRepositoryValidator refers to sun.* class

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2570:


Patch for ATLAS-1775 also contains this change, so closing

> OMRSRepositoryValidator refers to sun.* class
> -
>
> Key: ATLAS-2570
> URL: https://issues.apache.org/jira/browse/ATLAS-2570
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
> Attachments: ATLAS-2570.patch
>
>
> I noticed that this class was referring to old deprecated sun packages.
> import sun.misc.Regexp;
> Fortunately this package was not used, so it is a very minor fixup, but good 
> not to accidentally start using any private/deprecated packages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2571) Maven: duplicate declarations

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2571:
---
Attachment: ATLAS-2571.patch

> Maven: duplicate declarations
> -
>
> Key: ATLAS-2571
> URL: https://issues.apache.org/jira/browse/ATLAS-2571
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Minor
> Attachments: ATLAS-2571.patch
>
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:atlas-graphdb-titan0:jar:1.0.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-solrj:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 194, column 21
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-core:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 200, column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hive-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hive-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hive-bridge/pom.xml, line 484, column 
> 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:falcon-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:falcon-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/falcon-bridge/pom.xml, line 370, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:sqoop-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:sqoop-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/sqoop-bridge/pom.xml, line 433, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:storm-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:storm-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/storm-bridge/pom.xml, line 536, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hbase-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hbase-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hbase-bridge/pom.xml, line 508, 
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> [https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html]
> [INFO] 
> 
>  
>  
> These are generally caused by duplicates - for example taking the first:
>  
> 
>  org.apache.solr
>  solr-solrj
> 
> 
>  org.apache.solr
>  solr-solrj
>  ${solr.version}
> 
>  
> So we have it declared twice, once pulling in solr.version - defined in the 
> top level pom, and the other blank. In the case of this plugin, the version 
> is not declared in any DependencyManagement section (the common way of 
> defining default plugin versions which can then be overriden in child poms)
> Cleaning this up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2571) Maven: duplicate declarations

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2571:
---
Attachment: ATLAS-2571.patch

> Maven: duplicate declarations
> -
>
> Key: ATLAS-2571
> URL: https://issues.apache.org/jira/browse/ATLAS-2571
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Minor
> Attachments: ATLAS-2571.patch, ATLAS-2571.patch
>
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:atlas-graphdb-titan0:jar:1.0.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-solrj:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 194, column 21
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-core:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 200, column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hive-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hive-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hive-bridge/pom.xml, line 484, column 
> 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:falcon-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:falcon-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/falcon-bridge/pom.xml, line 370, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:sqoop-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:sqoop-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/sqoop-bridge/pom.xml, line 433, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:storm-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:storm-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/storm-bridge/pom.xml, line 536, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hbase-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hbase-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hbase-bridge/pom.xml, line 508, 
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> [https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html]
> [INFO] 
> 
>  
>  
> These are generally caused by duplicates - for example taking the first:
>  
> 
>  org.apache.solr
>  solr-solrj
> 
> 
>  org.apache.solr
>  solr-solrj
>  ${solr.version}
> 
>  
> So we have it declared twice, once pulling in solr.version - defined in the 
> top level pom, and the other blank. In the case of this plugin, the version 
> is not declared in any DependencyManagement section (the common way of 
> defining default plugin versions which can then be overriden in child poms)
> Cleaning this up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2571) Maven: duplicate declarations

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2571:


updated patch as review tool had issues. 

> Maven: duplicate declarations
> -
>
> Key: ATLAS-2571
> URL: https://issues.apache.org/jira/browse/ATLAS-2571
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Minor
> Attachments: ATLAS-2571.patch, ATLAS-2571.patch
>
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:atlas-graphdb-titan0:jar:1.0.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-solrj:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 194, column 21
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-core:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 200, column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hive-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hive-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hive-bridge/pom.xml, line 484, column 
> 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:falcon-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:falcon-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/falcon-bridge/pom.xml, line 370, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:sqoop-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:sqoop-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/sqoop-bridge/pom.xml, line 433, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:storm-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:storm-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/storm-bridge/pom.xml, line 536, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hbase-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hbase-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hbase-bridge/pom.xml, line 508, 
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> [https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html]
> [INFO] 
> 
>  
>  
> These are generally caused by duplicates - for example taking the first:
>  
> 
>  org.apache.solr
>  solr-solrj
> 
> 
>  org.apache.solr
>  solr-solrj
>  ${solr.version}
> 
>  
> So we have it declared twice, once pulling in solr.version - defined in the 
> top level pom, and the other blank. In the case of this plugin, the version 
> is not declared in any DependencyManagement section (the common way of 
> defining default plugin versions which can then be overriden in child poms)
> Cleaning this up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2571) Maven: duplicate declarations

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2571:


Other duplicates were caused by 2 declarations of a plugin in the pom - each 
with one execution. I have corrected these to a single declaration with two 
executions. Mostly this affected the bridges.

Whilst checking the errors I also noticed

 

[WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
prerequisites which is only intended for maven-plugin projects but not for non 
maven-plugin projects. For such purposes you should use the 
maven-enforcer-plugin. See 
[https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html]

 

I made a change to support maven-enforcer last year, so these prerequisites are 
not longer needed. I have therefore deleted.

> Maven: duplicate declarations
> -
>
> Key: ATLAS-2571
> URL: https://issues.apache.org/jira/browse/ATLAS-2571
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Minor
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:atlas-graphdb-titan0:jar:1.0.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-solrj:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 194, column 21
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-core:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 200, column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hive-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hive-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hive-bridge/pom.xml, line 484, column 
> 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:falcon-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:falcon-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/falcon-bridge/pom.xml, line 370, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:sqoop-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:sqoop-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/sqoop-bridge/pom.xml, line 433, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:storm-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:storm-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/storm-bridge/pom.xml, line 536, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hbase-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hbase-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hbase-bridge/pom.xml, line 508, 
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> [https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html]
> [INFO] 
> 

[jira] [Assigned] (ATLAS-2571) Maven: duplicate declarations

[Nigel Jones (JIRA)]

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

Nigel Jones reassigned ATLAS-2571:
--

Assignee: Nigel Jones

> Maven: duplicate declarations
> -
>
> Key: ATLAS-2571
> URL: https://issues.apache.org/jira/browse/ATLAS-2571
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:atlas-graphdb-titan0:jar:1.0.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-solrj:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 194, column 21
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-core:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 200, column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hive-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hive-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hive-bridge/pom.xml, line 484, column 
> 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:falcon-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:falcon-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/falcon-bridge/pom.xml, line 370, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:sqoop-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:sqoop-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/sqoop-bridge/pom.xml, line 433, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:storm-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:storm-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/storm-bridge/pom.xml, line 536, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hbase-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hbase-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hbase-bridge/pom.xml, line 508, 
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> [https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html]
> [INFO] 
> 
>  
>  
> These are generally caused by duplicates - for example taking the first:
>  
> 
>  org.apache.solr
>  solr-solrj
> 
> 
>  org.apache.solr
>  solr-solrj
>  ${solr.version}
> 
>  
> So we have it declared twice, once pulling in solr.version - defined in the 
> top level pom, and the other blank. In the case of this plugin, the version 
> is not declared in any DependencyManagement section (the common way of 
> defining default plugin versions which can then be overriden in child poms)
> Cleaning this up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2571) Maven: duplicate declarations

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2571:
---
Priority: Minor  (was: Major)

> Maven: duplicate declarations
> -
>
> Key: ATLAS-2571
> URL: https://issues.apache.org/jira/browse/ATLAS-2571
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Minor
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:atlas-graphdb-titan0:jar:1.0.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-solrj:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 194, column 21
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: org.apache.solr:solr-core:jar -> version (?) vs ${solr.version} @ 
> org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 200, column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hive-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hive-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hive-bridge/pom.xml, line 484, column 
> 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:falcon-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:falcon-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/falcon-bridge/pom.xml, line 370, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:sqoop-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:sqoop-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/sqoop-bridge/pom.xml, line 433, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:storm-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:storm-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/storm-bridge/pom.xml, line 536, 
> column 21
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:hbase-bridge:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ 
> org.apache.atlas:hbase-bridge:[unknown-version], 
> /Users/jonesn/IdeaProjects/atlas/addons/hbase-bridge/pom.xml, line 508, 
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> [https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html]
> [INFO] 
> 
>  
>  
> These are generally caused by duplicates - for example taking the first:
>  
> 
>  org.apache.solr
>  solr-solrj
> 
> 
>  org.apache.solr
>  solr-solrj
>  ${solr.version}
> 
>  
> So we have it declared twice, once pulling in solr.version - defined in the 
> top level pom, and the other blank. In the case of this plugin, the version 
> is not declared in any DependencyManagement section (the common way of 
> defining default plugin versions which can then be overriden in child poms)
> Cleaning this up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2571) Maven: duplicate declarations

[Nigel Jones (JIRA)]

Nigel Jones created ATLAS-2571:
--

 Summary: Maven: duplicate declarations
 Key: ATLAS-2571
 URL: https://issues.apache.org/jira/browse/ATLAS-2571
 Project: Atlas
  Issue Type: Improvement
Reporter: Nigel Jones


[INFO] Scanning for projects...

[WARNING]

[WARNING] Some problems were encountered while building the effective model for 
org.apache.atlas:atlas-graphdb-titan0:jar:1.0.0-SNAPSHOT

[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
be unique: org.apache.solr:solr-solrj:jar -> version (?) vs ${solr.version} @ 
org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
/Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 194, column 21

[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
be unique: org.apache.solr:solr-core:jar -> version (?) vs ${solr.version} @ 
org.apache.atlas:atlas-graphdb-titan0:[unknown-version], 
/Users/jonesn/IdeaProjects/atlas/graphdb/titan0/pom.xml, line 200, column 21

[WARNING]

[WARNING] Some problems were encountered while building the effective model for 
org.apache.atlas:hive-bridge:jar:1.0.0-SNAPSHOT

[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found 
duplicate declaration of plugin org.apache.maven.plugins:maven-resources-plugin 
@ org.apache.atlas:hive-bridge:[unknown-version], 
/Users/jonesn/IdeaProjects/atlas/addons/hive-bridge/pom.xml, line 484, column 21

[WARNING]

[WARNING] Some problems were encountered while building the effective model for 
org.apache.atlas:falcon-bridge:jar:1.0.0-SNAPSHOT

[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found 
duplicate declaration of plugin org.apache.maven.plugins:maven-resources-plugin 
@ org.apache.atlas:falcon-bridge:[unknown-version], 
/Users/jonesn/IdeaProjects/atlas/addons/falcon-bridge/pom.xml, line 370, column 
21

[WARNING]

[WARNING] Some problems were encountered while building the effective model for 
org.apache.atlas:sqoop-bridge:jar:1.0.0-SNAPSHOT

[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found 
duplicate declaration of plugin org.apache.maven.plugins:maven-resources-plugin 
@ org.apache.atlas:sqoop-bridge:[unknown-version], 
/Users/jonesn/IdeaProjects/atlas/addons/sqoop-bridge/pom.xml, line 433, column 
21

[WARNING]

[WARNING] Some problems were encountered while building the effective model for 
org.apache.atlas:storm-bridge:jar:1.0.0-SNAPSHOT

[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found 
duplicate declaration of plugin org.apache.maven.plugins:maven-resources-plugin 
@ org.apache.atlas:storm-bridge:[unknown-version], 
/Users/jonesn/IdeaProjects/atlas/addons/storm-bridge/pom.xml, line 536, column 
21

[WARNING]

[WARNING] Some problems were encountered while building the effective model for 
org.apache.atlas:hbase-bridge:jar:1.0.0-SNAPSHOT

[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found 
duplicate declaration of plugin org.apache.maven.plugins:maven-resources-plugin 
@ org.apache.atlas:hbase-bridge:[unknown-version], 
/Users/jonesn/IdeaProjects/atlas/addons/hbase-bridge/pom.xml, line 508, column 
21

[WARNING]

[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.

[WARNING]

[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.

[WARNING]

[WARNING] The project org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT uses 
prerequisites which is only intended for maven-plugin projects but not for non 
maven-plugin projects. For such purposes you should use the 
maven-enforcer-plugin. See 
[https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html]

[INFO] 

 

 

These are generally caused by duplicates - for example taking the first:

 


 org.apache.solr
 solr-solrj



 org.apache.solr
 solr-solrj
 ${solr.version}


 

So we have it declared twice, once pulling in solr.version - defined in the top 
level pom, and the other blank. In the case of this plugin, the version is not 
declared in any DependencyManagement section (the common way of defining 
default plugin versions which can then be overriden in child poms)

Cleaning this up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2570) OMRSRepositoryValidator refers to sun.* class

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2570:
---
Attachment: ATLAS-2570.patch

> OMRSRepositoryValidator refers to sun.* class
> -
>
> Key: ATLAS-2570
> URL: https://issues.apache.org/jira/browse/ATLAS-2570
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
> Attachments: ATLAS-2570.patch
>
>
> I noticed that this class was referring to old deprecated sun packages.
> import sun.misc.Regexp;
> Fortunately this package was not used, so it is a very minor fixup, but good 
> not to accidentally start using any private/deprecated packages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2570) OMRSRepositoryValidator refers to sun.* class

[Nigel Jones (JIRA)]

Nigel Jones created ATLAS-2570:
--

 Summary: OMRSRepositoryValidator refers to sun.* class
 Key: ATLAS-2570
 URL: https://issues.apache.org/jira/browse/ATLAS-2570
 Project: Atlas
  Issue Type: Improvement
Reporter: Nigel Jones


I noticed that this class was referring to old deprecated sun packages.

import sun.misc.Regexp;

Fortunately this package was not used, so it is a very minor fixup, but good 
not to accidentally start using any private/deprecated packages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2570) OMRSRepositoryValidator refers to sun.* class

[Nigel Jones (JIRA)]

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

Nigel Jones reassigned ATLAS-2570:
--

Assignee: Nigel Jones

> OMRSRepositoryValidator refers to sun.* class
> -
>
> Key: ATLAS-2570
> URL: https://issues.apache.org/jira/browse/ATLAS-2570
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
>
> I noticed that this class was referring to old deprecated sun packages.
> import sun.misc.Regexp;
> Fortunately this package was not used, so it is a very minor fixup, but good 
> not to accidentally start using any private/deprecated packages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2569) maven dependency plugin back level - issues with dependency tree check

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2569:
---
Attachment: ATLAS-2569.patch

> maven dependency plugin back level - issues with dependency tree check
> --
>
> Key: ATLAS-2569
> URL: https://issues.apache.org/jira/browse/ATLAS-2569
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Attachments: ATLAS-2569.patch
>
>
> The maven dependency plugin is at v2, yet we are using maven v3. This can 
> lead to incorrect results when checking the dependency tree. 
> The error producted from 'mvn dependency:tree' includes:
> [INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ atlas-client-v1 
> ---
> [WARNING] Using Maven 2 dependency tree to get verbose output, which may be 
> inconsistent with actual Maven 3 resolution
> The fix is to update the plugin to a later version. Patch to be added. No 
> warnings are then produced, and we should be more sure of getting proper 
> dependency tree reporting



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2569) maven dependency plugin back level - issues with dependency tree check

[Nigel Jones (JIRA)]

Nigel Jones created ATLAS-2569:
--

 Summary: maven dependency plugin back level - issues with 
dependency tree check
 Key: ATLAS-2569
 URL: https://issues.apache.org/jira/browse/ATLAS-2569
 Project: Atlas
  Issue Type: Improvement
Reporter: Nigel Jones


The maven dependency plugin is at v2, yet we are using maven v3. This can lead 
to incorrect results when checking the dependency tree. 

The error producted from 'mvn dependency:tree' includes:

[INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ atlas-client-v1 ---

[WARNING] Using Maven 2 dependency tree to get verbose output, which may be 
inconsistent with actual Maven 3 resolution

The fix is to update the plugin to a later version. Patch to be added. No 
warnings are then produced, and we should be more sure of getting proper 
dependency tree reporting



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2569) maven dependency plugin back level - issues with dependency tree check

[Nigel Jones (JIRA)]

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

Nigel Jones reassigned ATLAS-2569:
--

Assignee: Nigel Jones

> maven dependency plugin back level - issues with dependency tree check
> --
>
> Key: ATLAS-2569
> URL: https://issues.apache.org/jira/browse/ATLAS-2569
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> The maven dependency plugin is at v2, yet we are using maven v3. This can 
> lead to incorrect results when checking the dependency tree. 
> The error producted from 'mvn dependency:tree' includes:
> [INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ atlas-client-v1 
> ---
> [WARNING] Using Maven 2 dependency tree to get verbose output, which may be 
> inconsistent with actual Maven 3 resolution
> The fix is to update the plugin to a later version. Patch to be added. No 
> warnings are then produced, and we should be more sure of getting proper 
> dependency tree reporting



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2568) tools.jar is gone after Java 8

[Nigel Jones (JIRA)]

Nigel Jones created ATLAS-2568:
--

 Summary: tools.jar is gone after Java 8
 Key: ATLAS-2568
 URL: https://issues.apache.org/jira/browse/ATLAS-2568
 Project: Atlas
  Issue Type: Improvement
Reporter: Nigel Jones
 Attachments: dependency.out

We currently depend on jdk.tools artifact in the maven build. This is 
'tools.jar' from the JDK.

This has been removed from the JDK as of version 9 - See 'Removed rt.jar and 
tools.jar' at 
[https://docs.oracle.com/javase/9/migrate/toc.htm#JSMIG-GUID-A868D0B9-026F-4D46-B979-901834343F9E]

Running a maven dependency check (output attached) this is getting pulled in 
via our dependencies:

Solr 7.0.0 (recent.- Sep 17, though latest is 7.3.0)

Hadoop 2.7.1 (Jun 2015, latest 2.x is 2.9.0 from nov.17) 

Hbase 1.1.2 (Aug 2015, many versions since)

Hive 1.2.1 (jun 2015)

Or in more detail:

[INFO] \- org.apache.solr:solr-test-framework:jar:7.0.0:compile

[INFO] \- org.apache.hadoop:hadoop-common:jar:2.7.1:compile

[INFO] \- org.apache.hbase:hbase-client:jar:1.1.2:compile

[INFO] \- org.apache.hbase:hbase-server:jar:tests:1.1.2:compile

[INFO] \- org.apache.hive:hive-exec:jar:1.2.1:provided

[INFO] \- org.apache.hadoop:hadoop-annotations:jar:2.7.1:compile

[INFO] \- org.apache.hbase:hbase-server:jar:1.1.2:provided

I not know if these components have fixed the issues yet, and further, Action 
isn't needed on this until we go beyond Java 8 to 9,10,11 etc.. However I 
noticed this issue when looking at a different maven issue so thought it would 
be useful to log here for future action.

Of more relevance perhaps is:
 * Some of our dependencies are very old... Where compatible updates are 
available  we should be looking to bring these a little more up to date – 
obviously not a wholescale hadoop level change yet, but certainly the latest 
fix of each core component that works.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2488:


I've not yet been able to thoroughly test the new functions and won't be able 
to for a few weeks, so I've posted the patch (updated with Madhan's changes) so 
that others can also review/comments/try out.

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2488-1.patch, ATLAS-2488-2.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2488:


Thanks for the comments/update. ... I hadn't posted to review board etc as 
still checking out the client code.

 

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2488-1.patch, ATLAS-2488-2.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2488:
---
Attachment: (was: ATLAS-2488.patch)

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2488-1.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2488:
---
Attachment: ATLAS-2488-1.patch

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2488-1.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2488:


Correctly formatted patch added. Currently testing in ex-atlas client code.

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2488.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2488:
---
Attachment: ATLAS-2488.patch

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2488.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2488:
---
Attachment: (was: 2488.patch)

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2488:


Added temporary patch. Will repost in correct format to review board after more 
testing. 

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 2488.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2488:
---
Attachment: 2488.patch

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 2488.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

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

Nigel Jones reassigned ATLAS-2488:
--

Assignee: Nigel Jones

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Nigel Jones (JIRA)]

Nigel Jones created ATLAS-2488:
--

 Summary: AtlasClientV2 should support create of relationship
 Key: ATLAS-2488
 URL: https://issues.apache.org/jira/browse/ATLAS-2488
 Project: Atlas
  Issue Type: New Feature
Reporter: Nigel Jones
 Fix For: 1.0.0


RelationshipREST allows one to create, delete & get relationships

However the AtlasClientV2 API only has support for get & delete, not create

This is an omission (bug arguably?) , since the client should reflect what is 
available via the rest API in a more java-usable form

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2245) Update Maven dependency in build to 3.5.0

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2245:
---
Attachment: (was: ATLAS-2245-3.patch)

> Update Maven dependency in build to 3.5.0
> -
>
> Key: ATLAS-2245
> URL: https://issues.apache.org/jira/browse/ATLAS-2245
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
> Attachments: ATLAS-2245-4.patch
>
>
> The version of maven on the jenkins build was recently updated to address 
> some build issues.
> It seems a few people have hit maven issues so I now propose we update the 
> main build dependency to 3.5.0 as this is currently in the top level pom as
> 
> 3.0.4
> 
> and change to 3.5.0
> The very latest is 3.5.2, but since jenkins is now at 3.5.0 and is known 
> working, plus homebrew (mac) at least only goes as far as 3.5.0, I suggest we 
> go with that as a prereq. 3.5.2 will work as well 
> A search through the source tree shows this is the only occurance, so this is 
> a one file change
> NOTE: There is an impact to users, who need to upgrade to maven 3.5. I will 
> shortly check the wiki docs and would propose an email to the mailing list 
> remining developers to pull the latest maven 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2245) Update Maven dependency in build to 3.5.0

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2245:
---
Attachment: ATLAS-2245-4.patch

Updated with new error message as per review
** JAVA VERSION ERROR ** Java 8 (Update 151) or above is required.

> Update Maven dependency in build to 3.5.0
> -
>
> Key: ATLAS-2245
> URL: https://issues.apache.org/jira/browse/ATLAS-2245
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
> Attachments: ATLAS-2245-4.patch
>
>
> The version of maven on the jenkins build was recently updated to address 
> some build issues.
> It seems a few people have hit maven issues so I now propose we update the 
> main build dependency to 3.5.0 as this is currently in the top level pom as
> 
> 3.0.4
> 
> and change to 3.5.0
> The very latest is 3.5.2, but since jenkins is now at 3.5.0 and is known 
> working, plus homebrew (mac) at least only goes as far as 3.5.0, I suggest we 
> go with that as a prereq. 3.5.2 will work as well 
> A search through the source tree shows this is the only occurance, so this is 
> a one file change
> NOTE: There is an impact to users, who need to upgrade to maven 3.5. I will 
> shortly check the wiki docs and would propose an email to the mailing list 
> remining developers to pull the latest maven 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2245) Update Maven dependency in build to 3.5.0

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2245:
---
Attachment: ATLAS-2245-3.patch

Removed additional dependency check in graph pom

> Update Maven dependency in build to 3.5.0
> -
>
> Key: ATLAS-2245
> URL: https://issues.apache.org/jira/browse/ATLAS-2245
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
> Attachments: ATLAS-2245-3.patch
>
>
> The version of maven on the jenkins build was recently updated to address 
> some build issues.
> It seems a few people have hit maven issues so I now propose we update the 
> main build dependency to 3.5.0 as this is currently in the top level pom as
> 
> 3.0.4
> 
> and change to 3.5.0
> The very latest is 3.5.2, but since jenkins is now at 3.5.0 and is known 
> working, plus homebrew (mac) at least only goes as far as 3.5.0, I suggest we 
> go with that as a prereq. 3.5.2 will work as well 
> A search through the source tree shows this is the only occurance, so this is 
> a one file change
> NOTE: There is an impact to users, who need to upgrade to maven 3.5. I will 
> shortly check the wiki docs and would propose an email to the mailing list 
> remining developers to pull the latest maven 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2245) Update Maven dependency in build to 3.5.0

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2245:
---
Attachment: (was: ATLAS-2245-1.patch)

> Update Maven dependency in build to 3.5.0
> -
>
> Key: ATLAS-2245
> URL: https://issues.apache.org/jira/browse/ATLAS-2245
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Trivial
> Attachments: ATLAS-2245-3.patch
>
>
> The version of maven on the jenkins build was recently updated to address 
> some build issues.
> It seems a few people have hit maven issues so I now propose we update the 
> main build dependency to 3.5.0 as this is currently in the top level pom as
> 
> 3.0.4
> 
> and change to 3.5.0
> The very latest is 3.5.2, but since jenkins is now at 3.5.0 and is known 
> working, plus homebrew (mac) at least only goes as far as 3.5.0, I suggest we 
> go with that as a prereq. 3.5.2 will work as well 
> A search through the source tree shows this is the only occurance, so this is 
> a one file change
> NOTE: There is an impact to users, who need to upgrade to maven 3.5. I will 
> shortly check the wiki docs and would propose an email to the mailing list 
> remining developers to pull the latest maven 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2260) Ensure BerkeleyDB works with Janus

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2260:


Ok... if and when we get the rest of the build sorted, I still expect the 
proposal in ATLAS-2084 makes sense for incorporation of berkelydb as a local 
repo if a) we're ok with the license (seemed ok to me) and b) we can't find the 
lib elsewhere.. However thanks for the explanation, as you say seems there are 
bigger issues which are being worked first.

> Ensure BerkeleyDB works with Janus 
> ---
>
> Key: ATLAS-2260
> URL: https://issues.apache.org/jira/browse/ATLAS-2260
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>
> currently Atlas defaults to JanusGraph in master. The Atlas build appears to 
> bring in the Apache 2 licensed BerkeleyDB JE 7.3.7. I should be possible for 
> Atlas to be built and run with Janus using this embedded BerkeleyDB. 
> Currently building with 
> mvn clean package -Pdist,berkeley-elasticsearch -DskipTests  
> is clean but Atlas fails to start - as it cannot find a sleepycat DBException 
> class.
> We should consider supporting running Berkeley with solr as well. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2260) Ensure BerkeleyDB works with Janus

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2260:


See my explanation in ATLAS-2084, I think if I do a fix there, it should work 
with Janus. For now copy the library manually.

Suggestion - I can modify a patch to try and do the packaging .. it will still 
need testing (which can continue here)?

> Ensure BerkeleyDB works with Janus 
> ---
>
> Key: ATLAS-2260
> URL: https://issues.apache.org/jira/browse/ATLAS-2260
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>
> currently Atlas defaults to JanusGraph in master. The Atlas build appears to 
> bring in the Apache 2 licensed BerkeleyDB JE 7.3.7. I should be possible for 
> Atlas to be built and run with Janus using this embedded BerkeleyDB. 
> Currently building with 
> mvn clean package -Pdist,berkeley-elasticsearch -DskipTests  
> is clean but Atlas fails to start - as it cannot find a sleepycat DBException 
> class.
> We should consider supporting running Berkeley with solr as well. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (ATLAS-2012) Docker - image & hub - for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2012:
---
Comment: was deleted

(was: Looking at docker hub, for an individual to upload an image is pretty 
simple.
However to allow multiple users (within the atlas community) to update the 
image would require setting up an organization & then adding members

A number of projects though including zookeeper, flink, httpd, solr, storm have 
'official' images, guidelines for this are at 
https://github.com/docker-library/official-images. More review is required, but 
I think in the medium term this is what we should target, this comes with it 
requirements around aspects like issue tracking

In order to get an image uploaded promptly, a pragmatic approach is probably to 
create an organization (adding any individual interested) and upload as a 
contributed image in order to learn/verify the process, and once we have 
something useful that meets the official requirements to work towards migrating 
the image there.
)

> Docker - image & hub - for Atlas
> 
>
> Key: ATLAS-2012
> URL: https://issues.apache.org/jira/browse/ATLAS-2012
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
> Fix For: 1.0.0
>
> Attachments: ATLAS-2012-Build-docker-image.patch, atlas_docker.patch, 
> atlas_docker1.patch, atlas_docker_2.patch
>
>
> Docker is increasingly become a standard way of easily running components in 
> a flexible manner, whether for development, production, or test
> I feel there are a few things we can do with docker that will aid Atlas's 
> appeal
> 1. We could provide a simple example of how to create a docker image from the 
> Atlas build. This could be published on the wiki & it would make it easier 
> for developers to use Atlas within a docker environment - mostly by 
> addressing how to configure & start up
> 2. We could automatically generate a docker image as part of the build 
> process. This builds on #1 by automating the creation of the image & making 
> it "just part of the build"
> 3. We could publish the docker image from #2, for releases, to dockerhub, 
> making it near trivial for any developer to easily pull down and experiment 
> with Atlas. Full source of course would be provided/documented so that a user 
> could customize as needed for their environment plus of course improve what 
> is provided with the core project
> 4. We could work with other teams especially ranger, to allow similar efforts 
> in other teams to easily work together & be orchestrated 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2094) Make Atlas available in docker hub

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2094:


Looking at docker hub, for an individual to upload an image is pretty simple.
However to allow multiple users (within the atlas community) to update the 
image would require setting up an organization & then adding members
A number of projects though including zookeeper, flink, httpd, solr, storm have 
'official' images, guidelines for this are at 
https://github.com/docker-library/official-images. More review is required, but 
I think in the medium term this is what we should target, this comes with it 
requirements around aspects like issue tracking
In order to get an image uploaded promptly, a pragmatic approach is probably to 
create an organization (adding any individual interested) and upload as a 
contributed image in order to learn/verify the process, and once we have 
something useful that meets the official requirements to work towards migrating 
the image there.

> Make Atlas available in docker hub
> --
>
> Key: ATLAS-2094
> URL: https://issues.apache.org/jira/browse/ATLAS-2094
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>
> In ATLAS-2012 we introduced a basic docker image for Atlas which is created 
> in the build.
> In ATLAS-2093 this can be extended with some basic sample data
> This Jira will take things a step further. We can make Atlas available on the 
> docker hub or similar, so that just as with many technologies like Cassandra, 
> mysql, someone interested in taking a peek at what atlas has to offer can 
> quickly obtain and run atlas in little more than a single line.
> We need to check licensing (I imagine it's ok but need to validate), and 
> consider what other documentation might be needed, and any extra sample data, 
> so that someone is given a good impression of what the project offers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2012) Docker - image & hub - for Atlas

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2012:


Looking at docker hub, for an individual to upload an image is pretty simple.
However to allow multiple users (within the atlas community) to update the 
image would require setting up an organization & then adding members

A number of projects though including zookeeper, flink, httpd, solr, storm have 
'official' images, guidelines for this are at 
https://github.com/docker-library/official-images. More review is required, but 
I think in the medium term this is what we should target, this comes with it 
requirements around aspects like issue tracking

In order to get an image uploaded promptly, a pragmatic approach is probably to 
create an organization (adding any individual interested) and upload as a 
contributed image in order to learn/verify the process, and once we have 
something useful that meets the official requirements to work towards migrating 
the image there.


> Docker - image & hub - for Atlas
> 
>
> Key: ATLAS-2012
> URL: https://issues.apache.org/jira/browse/ATLAS-2012
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
> Fix For: 1.0.0
>
> Attachments: ATLAS-2012-Build-docker-image.patch, atlas_docker.patch, 
> atlas_docker1.patch, atlas_docker_2.patch
>
>
> Docker is increasingly become a standard way of easily running components in 
> a flexible manner, whether for development, production, or test
> I feel there are a few things we can do with docker that will aid Atlas's 
> appeal
> 1. We could provide a simple example of how to create a docker image from the 
> Atlas build. This could be published on the wiki & it would make it easier 
> for developers to use Atlas within a docker environment - mostly by 
> addressing how to configure & start up
> 2. We could automatically generate a docker image as part of the build 
> process. This builds on #1 by automating the creation of the image & making 
> it "just part of the build"
> 3. We could publish the docker image from #2, for releases, to dockerhub, 
> making it near trivial for any developer to easily pull down and experiment 
> with Atlas. Full source of course would be provided/documented so that a user 
> could customize as needed for their environment plus of course improve what 
> is provided with the core project
> 4. We could work with other teams especially ranger, to allow similar efforts 
> in other teams to easily work together & be orchestrated 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)