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

See -- [...truncated 37.03 MB...] 2017-08-26 03:59:38,672 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding primitive {name=owner, dataType={name=string,

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

See -- [...truncated 32.38 MB...] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at

Re: [VOTE] Release Apache Atlas 0.8.1 - release candidate 1

+1 - No binary files, except zip files containing json files - Verified build with -DskipTests=true (my build env as some issues) Thanks Bosco On 8/25/17, 2:13 PM, "Ramesh Mani" wrote: +1 for the rc1 of Apache Atlas 0.8.1 release Verified the build with

Re: Review Request 61561: ATLAS-1218: Atlas says it is started but does not accept REST requests

> On Aug. 25, 2017, 9:55 a.m., Nigel Jones wrote: > > distro/src/bin/atlas_start.py > > Lines 134 (patched) > > > > > > I notice we have a hardcoded max time of 5 minutes. I wonder if there's > > any scenarios

Build failed in Jenkins: Atlas-0.8-IntegrationTests #28

See -- [...truncated 36.43 MB...] 2017-08-25 22:01:08,575 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding primitive {name=qualifiedName, dataType={name=string,

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

See -- [...truncated 489.91 KB...] 127.0.0.1 - - [25/Aug/2017:21:51:17 +] "POST /api/atlas/entities HTTP/1.1" 201 - "-" "Java/1.7.0_80" 127.0.0.1 - -

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

See Changes: [madhan] ATLAS:2012: Dockerfile to build and run Atlas -- [...truncated 497.02 KB...] 127.0.0.1 - - [25/Aug/2017:19:44:33 +] "GET

Re: Review Request 61913: ATLAS-2012: Build docker image

> On Aug. 25, 2017, 6:18 p.m., Apoorv Naik wrote: > > dev-support/atlas-docker/Dockerfile > > Lines 52 (patched) > > > > > > Just curious as to why we're logging into hbase shell I had the same question. I think it

Re: Review Request 61913: ATLAS-2012: Build docker image

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61913/#review183868 --- Ship it! Ship It! - Madhan Neethiraj On Aug. 25, 2017, 1:14

[jira] [Updated] (ATLAS-2083) Refactor AtlasDefStore classes to reduce code duplication

[ https://issues.apache.org/jira/browse/ATLAS-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Ding updated ATLAS-2083: Attachment: ATLAS-2083_1.patch Rebased the patch on the latest master branch. > Refactor

Re: Review Request 61871: ATLAS-2083: Refactor AtlasDefStore classes to reduce code duplication

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61871/ --- (Updated Aug. 25, 2017, 6:44 p.m.) Review request for atlas, Apoorv Naik,

Re: Review Request 61913: ATLAS-2012: Build docker image

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61913/#review183865 --- dev-support/atlas-docker/Dockerfile Lines 52 (patched)

Build failed in Jenkins: Atlas-0.8-IntegrationTests #27

See -- [...truncated 33.17 MB...] 2017-08-25 18:10:08,379 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending message for topic ATLAS_ENTITIES:

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

See -- [...truncated 39.83 MB...] 2017-08-25 18:07:49,472 INFO - [ShutdownMonitor:] ~ ==> stopConsumerThreads() (NotificationHookConsumer:175) 2017-08-25 18:07:49,473 INFO

Re: Emtity Resource v1 test failures

Nigel, I agree we all need to spend some time and clean up these tests. Feel free to open JIRA's for the failing tests. I see the integration tests consistently failing in hive-bridge module due to Lock timeout exception - I suspect this is because of some stale open transaction lingering around

Re: Emtity Resource v1 test failures

I think Sarath already made changes for this one don't know why this failed again. Perhaps we need to revisit the integration tests after all. One jira per test failure should be a great way to split work amongst the community. Sent from Nine

Re: Review Request 61736: ATLAS-2049 Document common standards for OMAS interfaces

Hi all, We now have a number of OMAS APIs being designed and developed. There have been a number of discussions around best practices/standards, and the document below is an initial attempt to get these written down. I'm sure this will be an evolving list, but it would be really useful to get

[jira] [Created] (ATLAS-2086) Docker - reenable unit tests in build once IT stable

Nigel Jones created ATLAS-2086: -- Summary: Docker - reenable unit tests in build once IT stable Key: ATLAS-2086 URL: https://issues.apache.org/jira/browse/ATLAS-2086 Project: Atlas Issue Type:

Review Request 61913: ATLAS-2012: Build docker image

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61913/ --- Review request for atlas, Apoorv Naik, David Radley, Madhan Neethiraj, and

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

[ https://issues.apache.org/jira/browse/ATLAS-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nigel Jones updated ATLAS-2012: --- Attachment: ATLAS-2012-Build-docker-image.patch > Docker - image & hub - for Atlas >

Re: Emtity Resource v1 test failures

On 2017-08-25 12:28, "Nigel Jones" wrote: > I rebased this morning, but am still getting a failure - albeit a different > one - this looks like a timeout issue whilst the previous were seemingly more > functional. Is there a JIRA you are tracking these under? Should

Re: Emtity Resource v1 test failures

On 2017-08-24 18:45, Sarath Subramanian wrote: > Hi Nigel, > > Few Integration Test fixes have gone into master in the last couple of > days, could you rebase master and try the tests again. Hi Sarath, I rebased this morning, but am still getting a failure - albeit a

Re: About the way traits are stored in TitanDB

Hi Benjamin, The way Atlas is architected is that there is one graph for types and a separate graph for the instances. I see a lot of benefits with this design. Having edges between the types allows us to navigate and check types consistency with gremlin queries. It means we can implement

About the way traits are stored in TitanDB

Hi all, Working on Atlas repository in Titan, I am surprised by the way traits are stored : traits type are Vertices, which seems ok, but traits instances are Vertices too. So, when you attach a trait to an entity, Atlas will create a new Vertex (containing the attributes that are set) and

Re: Review Request 61561: ATLAS-1218: Atlas says it is started but does not accept REST requests

> On Aug. 11, 2017, 12:11 p.m., David Radley wrote: > > distro/src/bin/atlas_config.py > > Lines 71 (patched) > > > > > > I am uncomfortable duplicating the default port values here. I suggest > > moving this logic

Re: Review Request 61561: ATLAS-1218: Atlas says it is started but does not accept REST requests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61561/#review183837 --- distro/src/bin/atlas_start.py Lines 134 (patched)

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

See Changes: [madhan] ATLAS-2076: update type-search to support filter by RELATIONSHIP type [madhan] ATLAS-2060: Fix logger class name typos -- [...truncated

[jira] [Resolved] (ATLAS-2060) Fix logger class name typos

[ https://issues.apache.org/jira/browse/ATLAS-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2060. - Resolution: Fixed Committed to master:

[jira] [Resolved] (ATLAS-2076) Add RELATIONSHIP type to search filters

[ https://issues.apache.org/jira/browse/ATLAS-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2076. - Resolution: Fixed Committed to master:

Re: Review Request 61665: ATLAS-2047: Exception Thrown by Kafka Consumer Ends up Filling Logs Due to Incorrect Handling

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