date:20171114

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

2017-11-14 Thread 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

2017-11-14 Thread 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

2017-11-14 Thread 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)

Build failed in Jenkins: Atlas-master-IntegrationTests #184

2017-11-14 Thread Apache Jenkins Server

See 


Changes:

[ssubramanian] ATLAS-2258: Fix new Integration test failures introduced due to

--
[...truncated 646.30 KB...]
at 
org.apache.atlas.hive.HiveITBase.runCommandWithDelay(HiveITBase.java:113)
at org.apache.atlas.hive.HiveITBase.runCommand(HiveITBase.java:105)
at 
org.apache.atlas.hive.hook.HiveHookIT.testLoadLocalPath(HiveHookIT.java:426)

testLoadLocalPathIntoPartition(org.apache.atlas.hive.hook.HiveHookIT)  Time 
elapsed: 0.058 sec  <<< FAILURE!
java.lang.AssertionError: expected [0] but found [4]
at org.testng.Assert.fail(Assert.java:94)
at org.testng.Assert.failNotEquals(Assert.java:496)
at org.testng.Assert.assertEquals(Assert.java:125)
at org.testng.Assert.assertEquals(Assert.java:372)
at org.testng.Assert.assertEquals(Assert.java:382)
at 
org.apache.atlas.hive.HiveITBase.runCommandWithDelay(HiveITBase.java:120)
at 
org.apache.atlas.hive.HiveITBase.runCommandWithDelay(HiveITBase.java:113)
at org.apache.atlas.hive.HiveITBase.runCommand(HiveITBase.java:105)
at 
org.apache.atlas.hive.hook.HiveHookIT.testLoadLocalPathIntoPartition(HiveHookIT.java:437)

testTraitsPreservedOnColumnRename(org.apache.atlas.hive.hook.HiveHookIT)  Time 
elapsed: 95.146 sec  <<< FAILURE!
java.lang.AssertionError: Assertions failed. Failing after waiting for timeout 
8 msecs
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:387)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:320)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithRetries(AtlasBaseClient.java:471)
at org.apache.atlas.AtlasClient.callAPIWithRetries(AtlasClient.java:962)
at org.apache.atlas.AtlasClient.getEntity(AtlasClient.java:646)
at org.apache.atlas.hive.HiveITBase$1.evaluate(HiveITBase.java:161)
at org.apache.atlas.hive.HiveITBase.waitFor(HiveITBase.java:198)
at 
org.apache.atlas.hive.HiveITBase.assertEntityIsRegistered(HiveITBase.java:158)
at 
org.apache.atlas.hive.hook.HiveHookIT.assertColumnIsRegistered(HiveHookIT.java:281)
at 
org.apache.atlas.hive.hook.HiveHookIT.assertColumnIsRegistered(HiveHookIT.java:276)
at 
org.apache.atlas.hive.hook.HiveHookIT.testTraitsPreservedOnColumnRename(HiveHookIT.java:1253)

testTruncateTable(org.apache.atlas.hive.hook.HiveHookIT)  Time elapsed: 95.14 
sec  <<< FAILURE!
java.lang.AssertionError: Assertions failed. Failing after waiting for timeout 
8 msecs
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:387)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:320)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithRetries(AtlasBaseClient.java:471)
at org.apache.atlas.AtlasClient.callAPIWithRetries(AtlasClient.java:962)
at org.apache.atlas.AtlasClient.getEntity(AtlasClient.java:646)
at org.apache.atlas.hive.HiveITBase$1.evaluate(HiveITBase.java:161)
at org.apache.atlas.hive.HiveITBase.waitFor(HiveITBase.java:198)
at 
org.apache.atlas.hive.HiveITBase.assertEntityIsRegistered(HiveITBase.java:158)
at 
org.apache.atlas.hive.HiveITBase.assertTableIsRegistered(HiveITBase.java:152)
at 
org.apache.atlas.hive.HiveITBase.assertTableIsRegistered(HiveITBase.java:146)
at 
org.apache.atlas.hive.hook.HiveHookIT.testTruncateTable(HiveHookIT.java:1195)

testUpdateProcess(org.apache.atlas.hive.hook.HiveHookIT)  Time elapsed: 0.215 
sec  <<< FAILURE!
java.lang.AssertionError: expected [0] but found [1]
at org.testng.Assert.fail(Assert.java:94)
at org.testng.Assert.failNotEquals(Assert.java:496)
at org.testng.Assert.assertEquals(Assert.java:125)
at org.testng.Assert.assertEquals(Assert.java:372)
at org.testng.Assert.assertEquals(Assert.java:382)
at 
org.apache.atlas.hive.HiveITBase.runCommandWithDelay(HiveITBase.java:120)
at 
org.apache.atlas.hive.HiveITBase.runCommandWithDelay(HiveITBase.java:113)
at org.apache.atlas.hive.HiveITBase.runCommand(HiveITBase.java:105)
at 
org.apache.atlas.hive.hook.HiveHookIT.testUpdateProcess(HiveHookIT.java:581)


Results :

Failed tests: 
  
HiveMetastoreBridgeIT.testCreateTableAndImport:41->HiveITBase.assertDatabaseIsRegistered:237->HiveITBase.assertDatabaseIsRegistered:243->HiveITBase.assertEntityIsRegistered:158->HiveITBase.waitFor:202
 Assertions failed. Failing after waiting for timeout 8 msecs
  
HiveMetastoreBridgeIT.testImportCreatedTable:77->HiveITBase.assertDatabaseIsRegistered:237->HiveITBase.assertDatabaseIsRegistered:243->HiveITBase.assertEntityIsRegistered:158->HiveITBase.waitFor:202
 Assertions failed. Failing after waiting for timeout 8 msecs

Re: Unable to start atlas on master

2017-11-14 Thread Sarath Subramanian

David,

For berkeley-elasticsearch distribution.

Could you copy je-5.0.73.jar 
(https://mvnrepository.com/artifact/com.sleepycat/je/5.0.73) to 
${atlas_home}/libext directory and try restarting atlas. 

I’m able to bring up atlas by copying the jar. We do not package BerkeleyDB JE 
jar due to licensing requirements. 

Thanks,

Sarath Subramanian

On 11/14/17, 2:55 AM, "David Radley"  wrote:

>clean package 
>-Pdist,berkeley-elasticsearch -DskipTests

[jira] [Commented] (ATLAS-2251) Remove/replace use of TypeSystem with AtlasTypeRegistry

2017-11-14 Thread Nigel Jones (JIRA)


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

Nigel Jones commented on ATLAS-2251:


The patch may need rebasing - that error I posted now seems fixed. Getting a 
Hive Hook IT error now but I think that is a seperate issue so once rebased I 
think patch is good

> Remove/replace use of TypeSystem with AtlasTypeRegistry
> ---
>
> Key: ATLAS-2251
> URL: https://issues.apache.org/jira/browse/ATLAS-2251
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: ATLAS-2251-1.patch, ATLAS-2251-3.patch, 
> ATLAS-2251-4.patch
>
>
> With introduction of V2 APIs in 0.8 release, Atlas core type-system 
> implementation moved to use AtlasTypeRegistry (which uses data-structures 
> introduced in V2 APIs). However, earlier version equivalent, TypeSystem 
> (which uses V1 data-structures), is still being referenced in few places, 
> like:
>  - V1 REST APIs, to covert between V1 and V2 data-structures
>  - notification processing, which uses V1 data-structures
>  - DSL query implementation
>  - AtlasClient API
>  - unit tests
> Having to support legacy TypeSystem causes run time overhead in duplicate 
> caching of type-information - in AtlasTypeRegistry and TypeSystem. Removing 
> TypeSystem implementation will help eliminate this overhead and also improve 
> maintainability of Atlas sources.
> This JIRA is to track removal of TypeSystem implementation and its 
> references; where necessary, references should be updated to use 
> AtlasTypeRegistry equivalent.
> - it is very critical to continue to support V1 REST APIs and processing of 
> current V1 notifications 
> - existing unit tests that use V1 data-structures will be removed and will be 
> replaced with equivalents that use V2 data-structures
> - AtlasClient in new release will only support V2 data-structures; however, 
> older version AtlasClient will continue to work with new version of Atlas 
> server



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

Build failed in Jenkins: Atlas-master-Titan-IntegrationTests #16

2017-11-14 Thread Apache Jenkins Server

See 


Changes:

[ssubramanian] ATLAS-2258: Fix new Integration test failures introduced due to

--
[...truncated 444.17 KB...]
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities?type=hive_table=qualifiedName=default.table3nohitl8pi@primary
 HTTP/1.1" 200 4147 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities?type=hive_process=qualifiedName=QUERY:default.table3nohitl8pi@primary:1510704302000-%3E:PATH_WRITE
 HTTP/1.1" 200 2169 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities?type=hive_process=qualifiedName=QUERY:default.table3nohitl8pi@primary:1510704302000-%3E:PATH_WRITE
 HTTP/1.1" 200 2169 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities/f376b8e3-84e6-440e-bab5-5e1b86c28e95 HTTP/1.1" 200 2169 "-" 
"Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities/cd0c5cce-8506-4028-b9f6-9a6f3d84a785 HTTP/1.1" 200 4147 "-" 
"Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities/18983b36-a1e7-47ae-b3d1-46a9bd199541 HTTP/1.1" 200 1284 "-" 
"Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities/d23c4073-1db3-4d50-a5b9-a90e7c5dc339 HTTP/1.1" 200 1284 "-" 
"Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities?type=hdfs_path=qualifiedName=pfile:/home/jenkins/jenkins-slave/workspace/atlas-master-titan-integrationtests/addons/hive-bridge/target/somedfspath2-data-pn3ssulxfs
 HTTP/1.1" 200 1284 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities?type=hdfs_path=qualifiedName=pfile:/home/jenkins/jenkins-slave/workspace/atlas-master-titan-integrationtests/addons/hive-bridge/target/somedfspath2-data-pn3ssulxfs
 HTTP/1.1" 200 1284 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:14 +] "GET 
/api/atlas/entities/18983b36-a1e7-47ae-b3d1-46a9bd199541 HTTP/1.1" 200 1284 "-" 
"Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:15 +] "GET 
/api/atlas/entities?type=hive_db=qualifiedName=default@primary 
HTTP/1.1" 200 855 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:15 +] "GET 
/api/atlas/entities?type=hive_db=qualifiedName=default@primary 
HTTP/1.1" 200 855 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:15 +] "GET 
/api/atlas/entities?type=hive_table=qualifiedName=default.tablegaz1patcr5@primary
 HTTP/1.1" 404 116 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities?type=hive_table=qualifiedName=default.tablegaz1patcr5@primary
 HTTP/1.1" 200 4149 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities?type=hive_table=qualifiedName=default.tablegaz1patcr5@primary
 HTTP/1.1" 200 4149 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities?type=hive_process=qualifiedName=default.tablegaz1patcr5@primary:1510704315000
 HTTP/1.1" 200 1988 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities?type=hive_process=qualifiedName=default.tablegaz1patcr5@primary:1510704315000
 HTTP/1.1" 200 1988 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities/a5dc781c-11cd-480d-bc5a-076738de8a65 HTTP/1.1" 200 1988 "-" 
"Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities?type=hdfs_path=qualifiedName=pfile:/home/jenkins/jenkins-slave/workspace/atlas-master-titan-integrationtests/addons/hive-bridge/target/parentpath-data-zavcbzrk3z
 HTTP/1.1" 200 1278 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities?type=hdfs_path=qualifiedName=pfile:/home/jenkins/jenkins-slave/workspace/atlas-master-titan-integrationtests/addons/hive-bridge/target/parentpath-data-zavcbzrk3z
 HTTP/1.1" 200 1278 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities/4e510cd1-996c-4408-afaf-b35d3ebdeecb HTTP/1.1" 200 1278 "-" 
"Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities?type=hive_table HTTP/1.1" 200 2693 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities/026b8efd-f50f-4716-b644-69f00845d883 HTTP/1.1" 200 855 "-" 
"Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "GET 
/api/atlas/entities?type=hive_table=qualifiedName=default.tablegaz1patcr5@primary
 HTTP/1.1" 200 4149 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:20 +] "POST 
/api/atlas/entities/8977c574-d462-4d07-97f8-4b8e605c70da HTTP/1.1" 200 1267 "-" 
"Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:21 +] "GET 
/api/atlas/entities?type=hive_process=qualifiedName=default.tablegaz1patcr5@primary:1510704315000
 HTTP/1.1" 200 1988 "-" "Java/1.8.0_152"
127.0.0.1 - - [15/Nov/2017:00:05:21 +]

[jira] [Updated] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-2258:
--
Attachment: ATLAS-2258.2.patch

> Fix new Integration test failures introduced due to ATLAS-2251
> --
>
> Key: ATLAS-2258
> URL: https://issues.apache.org/jira/browse/ATLAS-2258
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 1.0.0
>
> Attachments: ATLAS-2258.2.patch
>
>
> * Disable DSL search related tests until v2 implementation is ready
> * Fix the following new IT failures:
>   
> EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
>  Â» AtlasService
>   TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
> servi...
>   TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 
> expected [404] but found [503]
>   TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
> ser...
>   TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service 
> API or...



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

[jira] [Updated] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-2258:
--
Attachment: (was: ATLAS-2258.1.patch)

> Fix new Integration test failures introduced due to ATLAS-2251
> --
>
> Key: ATLAS-2258
> URL: https://issues.apache.org/jira/browse/ATLAS-2258
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 1.0.0
>
>
> * Disable DSL search related tests until v2 implementation is ready
> * Fix the following new IT failures:
>   
> EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
>  Â» AtlasService
>   TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
> servi...
>   TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 
> expected [404] but found [503]
>   TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
> ser...
>   TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service 
> API or...



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

[jira] [Commented] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-2258:
---

[~jonesn] I updated the patch, the latest patch should fix the failure above.

> Fix new Integration test failures introduced due to ATLAS-2251
> --
>
> Key: ATLAS-2258
> URL: https://issues.apache.org/jira/browse/ATLAS-2258
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 1.0.0
>
> Attachments: ATLAS-2258.1.patch
>
>
> * Disable DSL search related tests until v2 implementation is ready
> * Fix the following new IT failures:
>   
> EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
>  Â» AtlasService
>   TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
> servi...
>   TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 
> expected [404] but found [503]
>   TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
> ser...
>   TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service 
> API or...



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

Re: Review Request 63792: [ATLAS-2258]: Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Sarath Subramanian


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63792/
---

(Updated Nov. 14, 2017, 3:40 p.m.)


Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.


Changes
---

addressed review comments.


Bugs: ATLAS-2258
https://issues.apache.org/jira/browse/ATLAS-2258


Repository: atlas


Description
---

* Disable DSL search related tests until v2 implementation is ready

* Fix the following new IT failures:
EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
 Â» AtlasService
EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
 Â» AtlasService
TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
servi...
TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 expected 
[404] but found [503]
TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
ser...
TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service API 
or...


Diffs (updated)
-

  addons/falcon-bridge/pom.xml f5b0b452 
  addons/hive-bridge/pom.xml b16d1c3f 
  addons/hive-bridge/src/test/java/org/apache/atlas/hive/HiveITBase.java 
d9fb46ec 
  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
773a1e81 
  addons/sqoop-bridge/pom.xml 5a9305e0 
  addons/storm-bridge/pom.xml e57c021f 
  client/client-v1/src/main/java/org/apache/atlas/AtlasClient.java bcdec712 
  client/client-v1/src/main/java/org/apache/atlas/EntityAuditEvent.java 
567205fb 
  intg/src/main/java/org/apache/atlas/type/AtlasType.java ce0a4755 
  intg/src/main/java/org/apache/atlas/v1/model/instance/Referenceable.java 
f1d28d1a 
  intg/src/main/java/org/apache/atlas/v1/model/instance/Struct.java 5aebd4b2 
  
intg/src/main/java/org/apache/atlas/v1/model/notification/EntityNotificationV1.java
 549dbe36 
  
intg/src/main/java/org/apache/atlas/v1/model/notification/HookNotificationV1.java
 c70e7d0c 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasEntityFormatConverter.java
 2229ecec 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
 89bf7dcd 
  webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
11879e65 
  
webapp/src/test/java/org/apache/atlas/web/integration/DataSetLineageJerseyResourceIT.java
 7e504800 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityDiscoveryJerseyResourceIT.java
 75d3872c 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
 0f585f9a 
  
webapp/src/test/java/org/apache/atlas/web/integration/MetadataDiscoveryJerseyResourceIT.java
 f25fc5f8 
  
webapp/src/test/java/org/apache/atlas/web/integration/TypesJerseyResourceIT.java
 cd876f4f 


Diff: https://reviews.apache.org/r/63792/diff/2/

Changes: https://reviews.apache.org/r/63792/diff/1-2/


Testing
---

mvn clean package Validated the failing ITs succeeds


Thanks,

Sarath Subramanian

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

2017-11-14 Thread Nigel Jones (JIRA)


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

Nigel Jones reassigned ATLAS-2094:
--

Assignee: Nigel Jones

> 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-2258) Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Nigel Jones (JIRA)


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

Nigel Jones commented on ATLAS-2258:


I was getting a whole slew of errors relating to the DSL change.. so I applied 
this patch to master (as of just now) and most of the errors have gone, though 
I now get this new one:

Mentioning it here as this patch isn't in master yet?\
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.277 sec <<< 
FAILURE! - in org.apache.atlas.web.service.SecureEmbeddedServerTest
runOtherSuitesAgainstSecureServer(org.apache.atlas.web.service.SecureEmbeddedServerTest)
  Time elapsed: 1.509 sec  <<< FAILURE!
org.testng.TestNGException: 
org.apache.atlas.web.integration.MetadataDiscoveryJerseyResourceIT.testSearchUsingFullText()
 is depending on method public void 
org.apache.atlas.web.integration.MetadataDiscoveryJerseyResourceIT.testSearchDSLLimits()
 throws java.lang.Exception, which is not annotated with @Test or not included.
at 
org.testng.internal.MethodHelper.findDependedUponMethods(MethodHelper.java:111)
at 
org.testng.internal.MethodHelper.topologicalSort(MethodHelper.java:241)
at org.testng.internal.MethodHelper.sortMethods(MethodHelper.java:317)
at 
org.testng.internal.MethodHelper.collectAndOrderMethods(MethodHelper.java:59)
at org.testng.TestRunner.initMethods(TestRunner.java:485)
at org.testng.TestRunner.init(TestRunner.java:239)
at org.testng.TestRunner.init(TestRunner.java:209)
at org.testng.TestRunner.(TestRunner.java:157)
at 
org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:546)
at org.testng.SuiteRunner.init(SuiteRunner.java:159)
at org.testng.SuiteRunner.(SuiteRunner.java:113)
at org.testng.TestNG.createSuiteRunner(TestNG.java:1274)
at org.testng.TestNG.createSuiteRunners(TestNG.java:1261)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1115)
at org.testng.TestNG.run(TestNG.java:1032)
at 
org.apache.atlas.web.service.SecureEmbeddedServerTestBase.runOtherSuitesAgainstSecureServer(SecureEmbeddedServerTestBase.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:659)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:845)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1153)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
at org.testng.TestRunner.privateRun(TestRunner.java:771)
at org.testng.TestRunner.run(TestRunner.java:621)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
at org.testng.SuiteRunner.run(SuiteRunner.java:259)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1199)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1124)
at org.testng.TestNG.run(TestNG.java:1032)
at 
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:129)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:113)
at 
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

(macOS, jdk 1.8 152b16)

> Fix new Integration test failures introduced due to ATLAS-2251
> --
>
> Key: ATLAS-2258
> URL: https://issues.apache.org/jira/browse/ATLAS-2258
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix

Re: Review Request 63792: [ATLAS-2258]: Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Madhan Neethiraj


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63792/#review191002
---


Fix it, then Ship it!





repository/src/main/java/org/apache/atlas/repository/converters/AtlasEntityFormatConverter.java
Line 129 (original), 129 (patched)


It will be safer to handle 'entity.getStatus() == null' here.


- Madhan Neethiraj


On Nov. 14, 2017, 9:32 a.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63792/
> ---
> 
> (Updated Nov. 14, 2017, 9:32 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2258
> https://issues.apache.org/jira/browse/ATLAS-2258
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> * Disable DSL search related tests until v2 implementation is ready
> 
> * Fix the following new IT failures:
> EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
>  Â» AtlasService
> EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
> EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
> MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
> TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
>  Â» AtlasService
> TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
> servi...
> TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 
> expected [404] but found [503]
> TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
> ser...
> TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service API 
> or...
> 
> 
> Diffs
> -
> 
>   client/client-v1/src/main/java/org/apache/atlas/EntityAuditEvent.java 
> 567205fb 
>   intg/src/main/java/org/apache/atlas/type/AtlasType.java ce0a4755 
>   intg/src/main/java/org/apache/atlas/v1/model/instance/Referenceable.java 
> f1d28d1a 
>   intg/src/main/java/org/apache/atlas/v1/model/instance/Struct.java 5aebd4b2 
>   
> intg/src/main/java/org/apache/atlas/v1/model/notification/EntityNotificationV1.java
>  549dbe36 
>   
> intg/src/main/java/org/apache/atlas/v1/model/notification/HookNotificationV1.java
>  c70e7d0c 
>   
> repository/src/main/java/org/apache/atlas/repository/converters/AtlasEntityFormatConverter.java
>  2229ecec 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
>  89bf7dcd 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 11879e65 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/DataSetLineageJerseyResourceIT.java
>  7e504800 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/EntityDiscoveryJerseyResourceIT.java
>  75d3872c 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
>  0f585f9a 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/MetadataDiscoveryJerseyResourceIT.java
>  f25fc5f8 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/TypesJerseyResourceIT.java
>  cd876f4f 
> 
> 
> Diff: https://reviews.apache.org/r/63792/diff/1/
> 
> 
> Testing
> ---
> 
> mvn clean package Validated the failing ITs succeeds
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 63721: ATLAS-1964 :UI, Support to resize and order columns in Search table

2017-11-14 Thread Ashutosh Mestry


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63721/#review190973
---


Fix it, then Ship it!





dashboardv2/gruntfile.js
Lines 168 (patched)


Where is the file with attributations?


- Ashutosh Mestry


On Nov. 14, 2017, 6:40 a.m., pratik pandey wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63721/
> ---
> 
> (Updated Nov. 14, 2017, 6:40 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, keval bhatt, Madhan Neethiraj, and 
> Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-1964
> https://issues.apache.org/jira/browse/ATLAS-1964
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add support for drag and drop column.
> 
> 
> Diffs
> -
> 
>   dashboardv2/gruntfile.js ba9ea0f 
>   dashboardv2/package.json 957e916 
>   dashboardv2/public/css/scss/search.scss 26f1505 
>   dashboardv2/public/js/main.js f6c0157 
>   dashboardv2/public/js/utils/Utils.js 47e9ac2 
>   dashboardv2/public/js/views/search/SearchResultLayoutView.js 2e8c165 
> 
> 
> Diff: https://reviews.apache.org/r/63721/diff/1/
> 
> 
> Testing
> ---
> 
> Done one round of sanity testing.
> 
> 
> Thanks,
> 
> pratik pandey
> 
>

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

2017-11-14 Thread Nigel Jones (JIRA)


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

Nigel Jones commented on ATLAS-2084:


I noticed when building that the berkeley library is now pulled in by 
Janusgraph:

org.janusgraph.janusgraph-berkeleyje:0.1.1 depends on com.sleepycat.je:7.3.7

If so, a) we need to be comfortable this is ok and b) if so, we can potentally 
abandon this particular change and just update documentation as to how to 
configure janus to use berkeleydb

Comments [~grahamwallis] 



> 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
> 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
(v6.4.14#64029)

Re: Review Request 63503: ATLAS-1095 - Review of OCF - the Open Connector Framework

2017-11-14 Thread Yao Li



> On Nov. 6, 2017, 12:50 p.m., Yao Li wrote:
> > om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/ElementHeader.java
> > Lines 164 (patched)
> > 
> >
> > I'm a little bit confused, when do you use super.getParentAsset() and 
> > this.getParentAsset()
> 
> Mandy Chessell wrote:
> It depends when you are in the class hierarchy.  Am I being inconsistent 
> in the code?

only the EmbeddedConnection class uses this.getParentAsset() in the code and 
other classes all use super.getParentAsset. EmbeddedConnection and 
Classification both extends AssetPropertyBase, but in Classfication you use 
super.getParentAsset() to get additionalProperties, but in EmbeddedConnection 
you use this.getParentAsset().


- Yao


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63503/#review190146
---


On Nov. 10, 2017, 12:48 p.m., Mandy Chessell wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63503/
> ---
> 
> (Updated Nov. 10, 2017, 12:48 p.m.)
> 
> 
> Review request for atlas and Madhan Neethiraj.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch contains the open connector framework code.  This code is located 
> in the om-fwk-ocf component and is described in JIRA 
> https://issues.apache.org/jira/browse/ATLAS-1095
> 
> I have added a new patch to the Jira with fixes from Yao's comments.  
> Upgraded Maven to 352 and rebuilt/rerun tests.
> 
> 
> Diffs
> -
> 
>   om-fwk-ocf/README.md PRE-CREATION 
>   om-fwk-ocf/pom.xml PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/Connector.java PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorBase.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorBroker.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorProvider.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorProviderBase.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/ConnectionCheckedException.java
>  PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/ConnectorCheckedException.java
>  PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/OCFCheckedExceptionBase.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/OCFErrorCode.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/OCFRuntimeException.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/PropertyServerException.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/README.md PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AdditionalProperties.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Analysis.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Annotation.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AnnotationStatus.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Annotations.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetDescriptor.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetDetail.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetPropertyBase.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetSummary.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetUniverse.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Certification.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Certifications.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Classification.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Classifications.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Comment.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/CommentType.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Comments.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/ConnectedAssetProperties.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Connection.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Connections.java 
> PRE-CREATION 
>

[jira] [Commented] (ATLAS-1837) OCF definitions for Area 1 of the open metadata model

2017-11-14 Thread Yao (JIRA)


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

Yao commented on ATLAS-1837:


the docs text 
https://cwiki.apache.org/confluence/display/ATLAS/Area+1+-+Connectors+and+Connector+Directories
 is not available anymore

> OCF definitions for Area 1 of the open metadata model
> -
>
> Key: ATLAS-1837
> URL: https://issues.apache.org/jira/browse/ATLAS-1837
> Project: Atlas
>  Issue Type: Task
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> the open connector framework in Area 1 in the open metadata model.



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

Re: Review Request 63503: ATLAS-1095 - Review of OCF - the Open Connector Framework

2017-11-14 Thread Yao Li


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63503/#review190936
---




om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Connection.java
Lines 27 (patched)


model 0101 does not exist in this 
wiki(https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Open+Metadata+Typesystem)



om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Endpoint.java
Lines 23 (patched)


in the model 
0040(https://cwiki.apache.org/confluence/display/ATLAS/Area+0+-+Extensions+to+the+base+model),
 Endpoint also has description:string. And this property is not in the class. 
Is this necessary for EndPoint?


- Yao Li


On Nov. 10, 2017, 12:48 p.m., Mandy Chessell wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63503/
> ---
> 
> (Updated Nov. 10, 2017, 12:48 p.m.)
> 
> 
> Review request for atlas and Madhan Neethiraj.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch contains the open connector framework code.  This code is located 
> in the om-fwk-ocf component and is described in JIRA 
> https://issues.apache.org/jira/browse/ATLAS-1095
> 
> I have added a new patch to the Jira with fixes from Yao's comments.  
> Upgraded Maven to 352 and rebuilt/rerun tests.
> 
> 
> Diffs
> -
> 
>   om-fwk-ocf/README.md PRE-CREATION 
>   om-fwk-ocf/pom.xml PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/Connector.java PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorBase.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorBroker.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorProvider.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorProviderBase.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/ConnectionCheckedException.java
>  PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/ConnectorCheckedException.java
>  PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/OCFCheckedExceptionBase.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/OCFErrorCode.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/OCFRuntimeException.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/PropertyServerException.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/README.md PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AdditionalProperties.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Analysis.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Annotation.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AnnotationStatus.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Annotations.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetDescriptor.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetDetail.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetPropertyBase.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetSummary.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetUniverse.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Certification.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Certifications.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Classification.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Classifications.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Comment.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/CommentType.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Comments.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/ConnectedAssetProperties.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Connection.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Connections.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/ConnectorType.java 
> PRE-CREATION 
>   
>

Unable to start atlas on master

2017-11-14 Thread David Radley

Hi all,
I have tried a few ways to build the latest atlas code from master;  all 
successfully build, but Atlas will not start. I wonder if anyone else is 
seeing this behavior. 

1) Prior to the recent changes, I was successfully running clean package 
-Pdist,berkeley-elasticsearch -DskipTests
This no longer works now the default has changed to Janus I get an error 
in the log com.sleepycat.je.DatabaseException not found

2) I have tried: 
clean package -Pdist,berkeley-elasticsearch -DskipTests 
-DGRAPH-PROVIDER=titan0
this also does not work - this looks like a regression - as the old titan0 
builds should continue to work the same as they did. 

3) I have followed the readme instructions and run 
$ export MAVEN_OPTS="-Xms2g -Xmx2g"
$ mvn clean install

# currently few tests might fail in some environments
# (timing issue?), the community is reviewing and updating
# such tests.
#
# if you see test failures, please run the following command:
   $ mvn clean -DskipTests install

$ mvn clean package -Pdist

This fails to start atlas

4) I run with HBase internal Solr errors - this fails with  errors in the 
log like this::

2017-11-13 16:51:36,612 ERROR - [pool-1-thread-3 - 
8eaf67c4-ba4b-4276-8ba9-7818ded1f9cf:] ~ Request to collection 
fulltext_index failed due to (400) 
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: 
Error from server at 
http://9.20.103.142:9838/solr/fulltext_index_shard1_replica1: Exception 
writing document id 3a0 to the index; possible analysis error., retry? 0 
(CloudSolrClient:889)
2017-11-13 16:51:36,645 ERROR - [pool-1-thread-3 - 
8eaf67c4-ba4b-4276-8ba9-7818ded1f9cf:] ~ Request to collection 
fulltext_index failed due to (400) 
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: 
Error from server at 
http://9.20.103.142:9838/solr/fulltext_index_shard1_replica1: Exception 
writing document id 3a0 to the index; possible analysis error., retry? 0 
(CloudSolrClient:889)
2017-11-13 16

This is issue is a blocker for me. I would which build options are 
expected to work and and which ones have been tested to work on master, 
  all the best, David. 






 
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: Review Request 63503: ATLAS-1095 - Review of OCF - the Open Connector Framework

2017-11-14 Thread Yao Li


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63503/#review190924
---




om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorBroker.java
Lines 134 (patched)


Do you mean in the ConnectorProvider class, it doesn't  
setConnectorClassName



om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorBroker.java
Lines 164 (patched)


I didn't find this class's definiation in the patch


- Yao Li


On Nov. 10, 2017, 12:48 p.m., Mandy Chessell wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63503/
> ---
> 
> (Updated Nov. 10, 2017, 12:48 p.m.)
> 
> 
> Review request for atlas and Madhan Neethiraj.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch contains the open connector framework code.  This code is located 
> in the om-fwk-ocf component and is described in JIRA 
> https://issues.apache.org/jira/browse/ATLAS-1095
> 
> I have added a new patch to the Jira with fixes from Yao's comments.  
> Upgraded Maven to 352 and rebuilt/rerun tests.
> 
> 
> Diffs
> -
> 
>   om-fwk-ocf/README.md PRE-CREATION 
>   om-fwk-ocf/pom.xml PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/Connector.java PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorBase.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorBroker.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorProvider.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ConnectorProviderBase.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/ConnectionCheckedException.java
>  PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/ConnectorCheckedException.java
>  PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/OCFCheckedExceptionBase.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/OCFErrorCode.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/OCFRuntimeException.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/PropertyServerException.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/ffdc/README.md PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AdditionalProperties.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Analysis.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Annotation.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AnnotationStatus.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Annotations.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetDescriptor.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetDetail.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetPropertyBase.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetSummary.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/AssetUniverse.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Certification.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Certifications.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Classification.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Classifications.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Comment.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/CommentType.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Comments.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/ConnectedAssetProperties.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Connection.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/Connections.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/ConnectorType.java 
> PRE-CREATION 
>   
> om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/DerivedSchemaElement.java
>  PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/ElementHeader.java 
> PRE-CREATION 
>   om-fwk-ocf/src/main/java/org/apache/atlas/ocf/properties/ElementType.java 
> PRE-CREATION

[jira] [Commented] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-2258:
---

Code Review: https://reviews.apache.org/r/63792/

> Fix new Integration test failures introduced due to ATLAS-2251
> --
>
> Key: ATLAS-2258
> URL: https://issues.apache.org/jira/browse/ATLAS-2258
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 1.0.0
>
> Attachments: ATLAS-2258.1.patch
>
>
> * Disable DSL search related tests until v2 implementation is ready
> * Fix the following new IT failures:
>   
> EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
>  Â» AtlasService
>   TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
> servi...
>   TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 
> expected [404] but found [503]
>   TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
> ser...
>   TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service 
> API or...



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

Review Request 63792: [ATLAS-2258]: Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Sarath Subramanian


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63792/
---

Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.


Bugs: ATLAS-2258
https://issues.apache.org/jira/browse/ATLAS-2258


Repository: atlas


Description
---

* Disable DSL search related tests until v2 implementation is ready

* Fix the following new IT failures:
EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
 Â» AtlasService
EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
 Â» AtlasService
TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
servi...
TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 expected 
[404] but found [503]
TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
ser...
TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service API 
or...


Diffs
-

  client/client-v1/src/main/java/org/apache/atlas/EntityAuditEvent.java 
567205fb 
  intg/src/main/java/org/apache/atlas/type/AtlasType.java ce0a4755 
  intg/src/main/java/org/apache/atlas/v1/model/instance/Referenceable.java 
f1d28d1a 
  intg/src/main/java/org/apache/atlas/v1/model/instance/Struct.java 5aebd4b2 
  
intg/src/main/java/org/apache/atlas/v1/model/notification/EntityNotificationV1.java
 549dbe36 
  
intg/src/main/java/org/apache/atlas/v1/model/notification/HookNotificationV1.java
 c70e7d0c 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasEntityFormatConverter.java
 2229ecec 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
 89bf7dcd 
  webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
11879e65 
  
webapp/src/test/java/org/apache/atlas/web/integration/DataSetLineageJerseyResourceIT.java
 7e504800 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityDiscoveryJerseyResourceIT.java
 75d3872c 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
 0f585f9a 
  
webapp/src/test/java/org/apache/atlas/web/integration/MetadataDiscoveryJerseyResourceIT.java
 f25fc5f8 
  
webapp/src/test/java/org/apache/atlas/web/integration/TypesJerseyResourceIT.java
 cd876f4f 


Diff: https://reviews.apache.org/r/63792/diff/1/


Testing
---

mvn clean package Validated the failing ITs succeeds


Thanks,

Sarath Subramanian

[jira] [Updated] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-2258:
--
Attachment: ATLAS-2258.1.patch

> Fix new Integration test failures introduced due to ATLAS-2251
> --
>
> Key: ATLAS-2258
> URL: https://issues.apache.org/jira/browse/ATLAS-2258
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 1.0.0
>
> Attachments: ATLAS-2258.1.patch
>
>
> * Disable DSL search related tests until v2 implementation is ready
> * Fix the following new IT failures:
>   
> EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
>  Â» AtlasService
>   TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
> servi...
>   TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 
> expected [404] but found [503]
>   TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
> ser...
>   TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service 
> API or...



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

[jira] [Updated] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

2017-11-14 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-2258:
--
Description: 
* Disable DSL search related tests until v2 implementation is ready
* Fix the following new IT failures:
  
EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
 Â» AtlasService
  
EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
  
EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
  
MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
  
TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
 Â» AtlasService
  TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
servi...
  TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 
expected [404] but found [503]
  TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
ser...
  TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service API 
or...

  was:
Fix the following new IT failures:
  
EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
 Â» AtlasService
  
EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
  
EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
  
MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
 Â» AtlasService
  
TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
 Â» AtlasService
  TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
servi...
  TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 
expected [404] but found [503]
  TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
ser...
  TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service API 
or...


> Fix new Integration test failures introduced due to ATLAS-2251
> --
>
> Key: ATLAS-2258
> URL: https://issues.apache.org/jira/browse/ATLAS-2258
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 1.0.0
>
>
> * Disable DSL search related tests until v2 implementation is ready
> * Fix the following new IT failures:
>   
> EntityDiscoveryJerseyResourceIT.setUp:52->createTypes:203->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityJerseyResourceIT.setUp:72->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> EntityLineageJerseyResourceIT.setUp:56->DataSetLineageJerseyResourceIT.setUp:60->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> MetadataDiscoveryJerseyResourceIT.setUp:57->createTypes:231->BaseResourceIT.createTypeDefinitionsV1:353->BaseResourceIT.createType:206
>  Â» AtlasService
>   
> TypedefsJerseyResourceIT.testCreate:84->BaseResourceIT.createType:163->BaseResourceIT.batchCreateTypes:158
>  Â» AtlasService
>   TypedefsJerseyResourceIT.testDuplicateCreate:112 Â» AtlasService Metadata 
> servi...
>   TypedefsJerseyResourceIT.testInvalidGets:200 Should've returned a 404 
> expected [404] but found [503]
>   TypedefsJerseyResourceIT.testListTypesByFilter:277 Â» AtlasService Metadata 
> ser...
>   TypedefsJerseyResourceIT.testUpdate:133 Â» AtlasService Metadata service 
> API or...



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

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

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

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

Build failed in Jenkins: Atlas-master-IntegrationTests #184

Re: Unable to start atlas on master

[jira] [Commented] (ATLAS-2251) Remove/replace use of TypeSystem with AtlasTypeRegistry

Build failed in Jenkins: Atlas-master-Titan-IntegrationTests #16

[jira] [Updated] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

[jira] [Updated] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

[jira] [Commented] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

Re: Review Request 63792: [ATLAS-2258]: Fix new Integration test failures introduced due to ATLAS-2251

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

[jira] [Commented] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

Re: Review Request 63792: [ATLAS-2258]: Fix new Integration test failures introduced due to ATLAS-2251

Re: Review Request 63721: ATLAS-1964 :UI, Support to resize and order columns in Search table

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

Re: Review Request 63503: ATLAS-1095 - Review of OCF - the Open Connector Framework

[jira] [Commented] (ATLAS-1837) OCF definitions for Area 1 of the open metadata model

Re: Review Request 63503: ATLAS-1095 - Review of OCF - the Open Connector Framework

Unable to start atlas on master

Re: Review Request 63503: ATLAS-1095 - Review of OCF - the Open Connector Framework

[jira] [Commented] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

Review Request 63792: [ATLAS-2258]: Fix new Integration test failures introduced due to ATLAS-2251

[jira] [Updated] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

[jira] [Updated] (ATLAS-2258) Fix new Integration test failures introduced due to ATLAS-2251

25 matches

Site Navigation

Mail list logo

Footer information