Build failed in Jenkins: Atlas-master-UnitTests #46

2017-08-29 Thread Apache Jenkins Server
See 

--
[...truncated 463.05 KB...]
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
at 
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
at 
org.apache.atlas.web.service.SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider(SecureEmbeddedServerTest.java:74)

testMissingEntriesInCredentialProvider(org.apache.atlas.web.service.SecureEmbeddedServerTest)
  Time elapsed: 0.002 sec  <<< FAILURE!
java.lang.AssertionError: No entries should generate an exception
at org.testng.Assert.fail(Assert.java:89)
at 
org.apache.atlas.web.service.SecureEmbeddedServerTestBase.testMissingEntriesInCredentialProvider(SecureEmbeddedServerTestBase.java:143)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
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)

testNoConfiguredCredentialProvider(org.apache.atlas.web.service.SecureEmbeddedServerTest)
  Time elapsed: 12.402 sec  <<< FAILURE!
java.lang.AssertionError: Should have thrown an exception
at org.testng.Assert.fail(Assert.java:89)
at 
org.apache.atlas.web.service.SecureEmbeddedServerTestBase.testNoConfiguredCredentialProvider(SecureEmbeddedServerTestBase.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
   

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

2017-08-29 Thread Apache Jenkins Server
See 


--
[...truncated 25.25 MB...]
2017-08-30 05:22:23,191 INFO  - [ShutdownMonitor:] ~ Stopping service 
org.apache.atlas.notification.NotificationHookConsumer (Services:65)
2017-08-30 05:22:23,191 INFO  - [ShutdownMonitor:] ~ ==> stopConsumerThreads() 
(NotificationHookConsumer:173)
2017-08-30 05:22:23,192 INFO  - [ShutdownMonitor:] ~ ==> HookConsumer 
shutdown() (NotificationHookConsumer$HookConsumer:421)
2017-08-30 05:22:23,192 INFO  - [ShutdownMonitor:] ~ 
[atlas-hook-consumer-thread], Shutting down (Logging$class:68)
2017-08-30 05:22:23,658 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 05:22:23,659 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 05:22:23,659 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e319258240002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-30 05:22:23,660 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 05:22:23,660 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 05:22:24,973 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 05:22:24,973 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 05:22:24,974 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e319258240002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-30 05:22:25,108 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 05:22:25,108 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 05:22:25,109 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e319258240002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-30 05:22:25,686 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 05:22:25,687 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 05:22:26,078 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 05:22:26,079 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 05:22:26,559 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 05:22:26,559 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 05:22:26,560 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e319258240002 for server null, unexpected error, 

[jira] [Comment Edited] (ATLAS-2087) Allow Atlas server to bind on a specific address

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian edited comment on ATLAS-2087 at 8/30/17 5:22 AM:


The following unit tests failed after the commit

Failed tests:
  NegativeSSLAndKerberosTest.testUnsecuredClient:139 expected: but 
was:
  SSLAndKerberosTest.testService:185 » ClientHandler java.io.IOException: 
javax
  SSLTest.testService:147 » ClientHandler javax.net.ssl.SSLException: 
Unrecogniz...
  
SecureEmbeddedServerTest>SecureEmbeddedServerTestBase.testMissingEntriesInCredentialProvider:143
 No entries should generate an exception
  
SecureEmbeddedServerTest>SecureEmbeddedServerTestBase.testNoConfiguredCredentialProvider:112
 Should have thrown an exception
  SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider:79 War 
deploy failed

https://builds.apache.org/view/A/view/Atlas/job/Atlas-master-UnitTests/46/console


was (Author: sarath.ku...@gmail.com):
The following unit tests failed after the commit

Failed tests:
  NegativeSSLAndKerberosTest.testUnsecuredClient:139 expected: but 
was:
  SSLAndKerberosTest.testService:185 » ClientHandler java.io.IOException: 
javax
  SSLTest.testService:147 » ClientHandler javax.net.ssl.SSLException: 
Unrecogniz...
  
SecureEmbeddedServerTest>SecureEmbeddedServerTestBase.testMissingEntriesInCredentialProvider:143
 No entries should generate an exception
  
SecureEmbeddedServerTest>SecureEmbeddedServerTestBase.testNoConfiguredCredentialProvider:112
 Should have thrown an exception
  SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider:79 War 
deploy failed



> Allow Atlas server to bind on a specific address
> 
>
> Key: ATLAS-2087
> URL: https://issues.apache.org/jira/browse/ATLAS-2087
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2087.2.patch, ATLAS-2087.patch
>
>
> Atlas server always bind to address "0.0.0.0":
> {code}
> connector.setHost("0.0.0.0");
> {code}
> But in many cases, user want to only run Atlas on a specified IP address 
> (e.g. private network).
> The existing property "_atlas.server.bind.address_" should be used:
> {code}
> final String addr = conf.get("atlas.server.bind.address", "0.0.0.0");
> connector.setHost(addr);
> {code}



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


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

2017-08-29 Thread Apache Jenkins Server
See 


--
[...truncated 39.82 MB...]
2017-08-30 05:13:09,385 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=owner, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2635008] (GraphToTypedInstanceMapper:387)
2017-08-30 05:13:09,386 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2635008 type=hdfs_path 
guid=36eee2d3-097a-47d2-8dd5-dec64731f44f] (GraphHelper:505)
2017-08-30 05:13:09,396 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"4dc69870-4ec2-4394-bdda-8b9a3d59ee49","version":0,"typeName":"hive_process","state":"ACTIVE"},"typeName":"hive_process","values":{"queryId":"jenkins_20170830051120_a3fb25bf-ba41-40c6-9ee1-061d84bc8bda","name":"create
  external table table1hdl8k1ahu(id int, name string) comment \u0027table 
comment\u0027  partitioned by(dt string) location 
\u0027pfile:///home/jenkins/jenkins-slave/workspace/atlas-master-integrationtests/addons/hive-bridge/./target/sometestpath-data-ffyctjleg1\u0027","startTime":"2017-08-30T05:11:20.932Z","queryPlan":"Not
 
Supported","operationType":"CREATETABLE","outputs":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"fc9f5976-f3af-4aae-bee3-784fa4280e2f","version":0,"typeName":"DataSet","state":"ACTIVE"}],"endTime":"2017-08-30T05:11:21.073Z","recentQueries":["create
  external table table1hdl8k1ahu(id int, name string) comment \u0027table 
comment\u0027  partitioned by(dt string) location 
\u0027pfile:///home/jenkins/jenkins-slave/workspace/atlas-master-integrationtests/addons/hive-bridge/./target/sometestpath-data-ffyctjleg1\u0027"],"inputs":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"36eee2d3-097a-47d2-8dd5-dec64731f44f","version":0,"typeName":"DataSet","state":"ACTIVE"}],"qualifiedName":"default.table1hdl8k1ahu@primary:150406988","queryText":"create
  external table table1hdl8k1ahu(id int, name string) comment \u0027table 
comment\u0027  partitioned by(dt string) location 
\u0027pfile:///home/jenkins/jenkins-slave/workspace/atlas-master-integrationtests/addons/hive-bridge/./target/sometestpath-data-ffyctjleg1\u0027","clusterName":"primary","userName":"jenkins"},"traitNames":[],"traits":{},"systemAttributes":{}},"operationType":"ENTITY_CREATE","traits":[]}}
 (KafkaNotification:218)
2017-08-30 05:13:09,397 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"36eee2d3-097a-47d2-8dd5-dec64731f44f","version":0,"typeName":"hdfs_path","state":"ACTIVE"},"typeName":"hdfs_path","values":{"name":"/home/jenkins/jenkins-slave/workspace/atlas-master-integrationtests/addons/hive-bridge/target/sometestpath-data-ffyctjleg1","path":"pfile:/home/jenkins/jenkins-slave/workspace/atlas-master-integrationtests/addons/hive-bridge/target/sometestpath-data-ffyctjleg1","createTime":"1970-01-01T00:00:00.000Z","isSymlink":false,"numberOfReplicas":0,"qualifiedName":"pfile:/home/jenkins/jenkins-slave/workspace/atlas-master-integrationtests/addons/hive-bridge/target/sometestpath-data-ffyctjleg1","isFile":false,"fileSize":0,"modifiedTime":"1970-01-01T00:00:00.000Z","clusterName":"primary"},"traitNames":[],"traits":{},"systemAttributes":{}},"operationType":"ENTITY_CREATE","traits":[]}}
 (KafkaNotification:218)
2017-08-30 05:13:09,504 INFO  - [ShutdownMonitor:] ~ Stopping service 
org.apache.atlas.notification.NotificationHookConsumer (Services:65)
2017-08-30 05:13:09,505 INFO  - [ShutdownMonitor:] ~ ==> stopConsumerThreads() 
(NotificationHookConsumer:175)
2017-08-30 05:13:09,505 INFO  - [ShutdownMonitor:] ~ ==> HookConsumer 
shutdown() (NotificationHookConsumer$HookConsumer:423)
2017-08-30 05:13:09,505 INFO  - [ShutdownMonitor:] ~ 
[atlas-hook-consumer-thread], Shutting down (Logging$class:68)
2017-08-30 05:13:09,824 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 05:13:09,824 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 05:13:09,825 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e3189d6ad0002 for server null, unexpected error, closing socket 

[jira] [Reopened] (ATLAS-2087) Allow Atlas server to bind on a specific address

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian reopened ATLAS-2087:
---

The following unit tests failed after the commit

Failed tests:
  NegativeSSLAndKerberosTest.testUnsecuredClient:139 expected: but 
was:
  SSLAndKerberosTest.testService:185 » ClientHandler java.io.IOException: 
javax
  SSLTest.testService:147 » ClientHandler javax.net.ssl.SSLException: 
Unrecogniz...
  
SecureEmbeddedServerTest>SecureEmbeddedServerTestBase.testMissingEntriesInCredentialProvider:143
 No entries should generate an exception
  
SecureEmbeddedServerTest>SecureEmbeddedServerTestBase.testNoConfiguredCredentialProvider:112
 Should have thrown an exception
  SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider:79 War 
deploy failed



> Allow Atlas server to bind on a specific address
> 
>
> Key: ATLAS-2087
> URL: https://issues.apache.org/jira/browse/ATLAS-2087
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2087.2.patch, ATLAS-2087.patch
>
>
> Atlas server always bind to address "0.0.0.0":
> {code}
> connector.setHost("0.0.0.0");
> {code}
> But in many cases, user want to only run Atlas on a specified IP address 
> (e.g. private network).
> The existing property "_atlas.server.bind.address_" should be used:
> {code}
> final String addr = conf.get("atlas.server.bind.address", "0.0.0.0");
> connector.setHost(addr);
> {code}



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


Build failed in Jenkins: Atlas-master-UnitTests #45

2017-08-29 Thread Apache Jenkins Server
See 

--
[...truncated 463.06 KB...]
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
at 
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
at 
org.apache.atlas.web.service.SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider(SecureEmbeddedServerTest.java:74)

testMissingEntriesInCredentialProvider(org.apache.atlas.web.service.SecureEmbeddedServerTest)
  Time elapsed: 0.001 sec  <<< FAILURE!
java.lang.AssertionError: No entries should generate an exception
at org.testng.Assert.fail(Assert.java:89)
at 
org.apache.atlas.web.service.SecureEmbeddedServerTestBase.testMissingEntriesInCredentialProvider(SecureEmbeddedServerTestBase.java:143)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
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)

testNoConfiguredCredentialProvider(org.apache.atlas.web.service.SecureEmbeddedServerTest)
  Time elapsed: 12.18 sec  <<< FAILURE!
java.lang.AssertionError: Should have thrown an exception
at org.testng.Assert.fail(Assert.java:89)
at 
org.apache.atlas.web.service.SecureEmbeddedServerTestBase.testNoConfiguredCredentialProvider(SecureEmbeddedServerTestBase.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)

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

2017-08-29 Thread Apache Jenkins Server
See 


--
[...truncated 30.40 MB...]
2017-08-30 04:23:32,686 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Referenceable.qualifiedName from vertex[id=2647552 type=hive_process 
guid=bb3fd027-a4cf-49a7-ab9f-e775d3f4023a] (GraphHelper:433)
2017-08-30 04:23:32,688 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo name (GraphToTypedInstanceMapper:144)
2017-08-30 04:23:32,688 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=name, dataType={name=string, description=null}, 
multiplicity={lower=1, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2647552] (GraphToTypedInstanceMapper:387)
2017-08-30 04:23:32,690 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.name from vertex[id=2647552 type=hive_process 
guid=bb3fd027-a4cf-49a7-ab9f-e775d3f4023a] (GraphHelper:433)
2017-08-30 04:23:32,691 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.name from vertex[id=2647552 type=hive_process 
guid=bb3fd027-a4cf-49a7-ab9f-e775d3f4023a] (GraphHelper:433)
2017-08-30 04:23:32,692 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo description (GraphToTypedInstanceMapper:144)
2017-08-30 04:23:32,692 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=description, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=false, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2647552] (GraphToTypedInstanceMapper:387)
2017-08-30 04:23:32,693 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.description from vertex[id=2647552 type=hive_process 
guid=bb3fd027-a4cf-49a7-ab9f-e775d3f4023a] (GraphHelper:433)
2017-08-30 04:23:32,694 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo owner (GraphToTypedInstanceMapper:144)
2017-08-30 04:23:32,694 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=owner, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2647552] (GraphToTypedInstanceMapper:387)
2017-08-30 04:23:32,696 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2647552 type=hive_process 
guid=bb3fd027-a4cf-49a7-ab9f-e775d3f4023a] (GraphHelper:433)
2017-08-30 04:23:32,714 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"bb3fd027-a4cf-49a7-ab9f-e775d3f4023a","version":0,"typeName":"hive_process","state":"ACTIVE"},"typeName":"hive_process","values":{"queryId":"jenkins_20170830042136_69408de6-0ceb-4f10-b1b6-8f95edc6bfe0","name":"create
  external table tablerxu5fudshx(id int, name string) comment \u0027table 
comment\u0027  partitioned by(dt string) location 
\u0027pfile:///home/jenkins/jenkins-slave/workspace/atlas-0.8-integrationtests/addons/hive-bridge/./target/sometestpath-data-qfvvrik20c\u0027","startTime":"2017-08-30T04:21:36.351Z","queryPlan":"Not
 
Supported","operationType":"CREATETABLE","outputs":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"5d5ed887-b4b5-41c2-ad22-c640e0c14559","version":0,"typeName":"DataSet","state":"DELETED"}],"endTime":"2017-08-30T04:21:36.580Z","recentQueries":["create
  external table tablerxu5fudshx(id int, name string) comment \u0027table 
comment\u0027  partitioned by(dt string) location 
\u0027pfile:///home/jenkins/jenkins-slave/workspace/atlas-0.8-integrationtests/addons/hive-bridge/./target/sometestpath-data-qfvvrik20c\u0027"],"inputs":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"5f9bf05b-261e-4471-b52f-51b5ee27ac90","version":0,"typeName":"DataSet","state":"ACTIVE"}],"qualifiedName":"default.tablerxu5fudshx@primary:1504066896000","queryText":"create
  external table tablerxu5fudshx(id int, name string) comment \u0027table 
comment\u0027  partitioned by(dt string) location 
\u0027pfile:///home/jenkins/jenkins-slave/workspace/atlas-0.8-integrationtests/addons/hive-bridge/./target/sometestpath-data-qfvvrik20c\u0027","clusterName":"primary","userName":"jenkins"},"traitNames":[],"traits":{},"systemAttributes":{}},"operationType":"ENTITY_UPDATE","traits":[]}}
 (KafkaNotification:218)
2017-08-30 04:23:32,841 INFO  - [ShutdownMonitor:] ~ Stopping service 
org.apache.atlas.notification.NotificationHookConsumer (Services:65)
2017-08-30 04:23:32,841 INFO  - [ShutdownMonitor:] ~ ==> stopConsumerThreads() 

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

2017-08-29 Thread Apache Jenkins Server
See 


--
[...truncated 33.68 MB...]

testLoadDFSPathPartitioned(org.apache.atlas.hive.hook.HiveHookIT)  Time 
elapsed: 5.528 sec  <<< FAILURE!
java.lang.AssertionError: Assertions failed. Failing after waiting for timeout 
1000 msecs
at 
org.apache.atlas.hive.hook.HiveHookIT.testLoadDFSPathPartitioned(HiveHookIT.java:448)
Caused by: org.apache.atlas.AtlasServiceException: Metadata service API 
org.apache.atlas.AtlasBaseClient$APIInfo@44b9cdf5 failed with status 404 (Not 
Found) Response Body ({"error":"Instance hive_table with unique attribute 
{qualifiedName=default.tablep682fubr6x@primary} does not exist"})
at 
org.apache.atlas.hive.hook.HiveHookIT.testLoadDFSPathPartitioned(HiveHookIT.java:448)

testLoadLocalPath(org.apache.atlas.hive.hook.HiveHookIT)  Time elapsed: 0.158 
sec  <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<4>
at 
org.apache.atlas.hive.hook.HiveHookIT.testLoadLocalPath(HiveHookIT.java:428)

testLoadLocalPathIntoPartition(org.apache.atlas.hive.hook.HiveHookIT)  Time 
elapsed: 0.219 sec  <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<4>
at 
org.apache.atlas.hive.hook.HiveHookIT.testLoadLocalPathIntoPartition(HiveHookIT.java:439)

testTraitsPreservedOnColumnRename(org.apache.atlas.hive.hook.HiveHookIT)  Time 
elapsed: 5.582 sec  <<< FAILURE!
java.lang.AssertionError: Assertions failed. Failing after waiting for timeout 
1000 msecs
at 
org.apache.atlas.hive.hook.HiveHookIT.assertColumnIsRegistered(HiveHookIT.java:283)
at 
org.apache.atlas.hive.hook.HiveHookIT.assertColumnIsRegistered(HiveHookIT.java:278)
at 
org.apache.atlas.hive.hook.HiveHookIT.testTraitsPreservedOnColumnRename(HiveHookIT.java:1255)
Caused by: org.apache.atlas.AtlasServiceException: Metadata service API 
org.apache.atlas.AtlasBaseClient$APIInfo@34086c5b failed with status 404 (Not 
Found) Response Body ({"error":"Instance hive_column with unique attribute 
{qualifiedName=dbcxr9pdahu9.tableyiqijdut0b.id@primary} does not exist"})
at 
org.apache.atlas.hive.hook.HiveHookIT.assertColumnIsRegistered(HiveHookIT.java:283)
at 
org.apache.atlas.hive.hook.HiveHookIT.assertColumnIsRegistered(HiveHookIT.java:278)
at 
org.apache.atlas.hive.hook.HiveHookIT.testTraitsPreservedOnColumnRename(HiveHookIT.java:1255)

testTruncateTable(org.apache.atlas.hive.hook.HiveHookIT)  Time elapsed: 5.582 
sec  <<< FAILURE!
java.lang.AssertionError: Assertions failed. Failing after waiting for timeout 
1000 msecs
at 
org.apache.atlas.hive.hook.HiveHookIT.testTruncateTable(HiveHookIT.java:1197)
Caused by: org.apache.atlas.AtlasServiceException: Metadata service API 
org.apache.atlas.AtlasBaseClient$APIInfo@1342e8af failed with status 404 (Not 
Found) Response Body ({"error":"Instance hive_table with unique attribute 
{qualifiedName=default.tablelkwrrrctbs@primary} does not exist"})
at 
org.apache.atlas.hive.hook.HiveHookIT.testTruncateTable(HiveHookIT.java:1197)

testUpdateProcess(org.apache.atlas.hive.hook.HiveHookIT)  Time elapsed: 10.582 
sec  <<< FAILURE!
java.lang.AssertionError: Assertions failed. Failing after waiting for timeout 
1000 msecs
at 
org.apache.atlas.hive.hook.HiveHookIT.assertProcessIsRegistered(HiveHookIT.java:1735)
at 
org.apache.atlas.hive.hook.HiveHookIT.validateProcess(HiveHookIT.java:487)
at 
org.apache.atlas.hive.hook.HiveHookIT.validateProcess(HiveHookIT.java:507)
at 
org.apache.atlas.hive.hook.HiveHookIT.testUpdateProcess(HiveHookIT.java:590)
Caused by: org.apache.atlas.AtlasServiceException: Metadata service API 
org.apache.atlas.AtlasBaseClient$APIInfo@114d02fc failed with status 404 (Not 
Found) Response Body ({"error":"Instance hive_process with unique attribute 
{qualifiedName=QUERY:default.tablecsyotanhkp@primary:1504066935000->:PATH_WRITE}
 does not exist"})
at 
org.apache.atlas.hive.hook.HiveHookIT.assertProcessIsRegistered(HiveHookIT.java:1735)
at 
org.apache.atlas.hive.hook.HiveHookIT.validateProcess(HiveHookIT.java:487)
at 
org.apache.atlas.hive.hook.HiveHookIT.validateProcess(HiveHookIT.java:507)
at 
org.apache.atlas.hive.hook.HiveHookIT.testUpdateProcess(HiveHookIT.java:590)


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 1000 msecs
  
HiveMetastoreBridgeIT.testImportCreatedTable:77->HiveITBase.assertDatabaseIsRegistered:237->HiveITBase.assertDatabaseIsRegistered:243->HiveITBase.assertEntityIsRegistered:158->HiveITBase.waitFor:202
 Assertions failed. Failing after waiting for timeout 1000 msecs
  

Jenkins build is back to normal : Atlas-master-NoTests #47

2017-08-29 Thread Apache Jenkins Server
See 




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

2017-08-29 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2087: fix for build failure in earlier commit

--
[...truncated 34.80 MB...]
EndOfStreamException: Unable to read additional data from client sessionid 
0x15e310c7719, likely client has closed socket
at 
org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
at 
org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
at java.lang.Thread.run(Thread.java:745)
2017-08-30 02:56:53,158 INFO  - [ShutdownMonitor:] ~ Stopping service 
org.apache.atlas.notification.NotificationHookConsumer (Services:65)
2017-08-30 02:56:53,158 INFO  - [ShutdownMonitor:] ~ ==> stopConsumerThreads() 
(NotificationHookConsumer:175)
2017-08-30 02:56:53,159 INFO  - [ShutdownMonitor:] ~ ==> HookConsumer 
shutdown() (NotificationHookConsumer$HookConsumer:423)
2017-08-30 02:56:53,159 INFO  - [ShutdownMonitor:] ~ 
[atlas-hook-consumer-thread], Shutting down (Logging$class:68)
2017-08-30 02:56:53,543 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 02:56:53,544 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 02:56:54,245 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 02:56:54,245 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 02:56:54,246 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e310c77190002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-30 02:56:54,649 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 02:56:54,650 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 02:56:55,053 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 02:56:55,054 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 02:56:55,534 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 02:56:55,534 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 02:56:55,535 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e310c77190002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-30 02:56:56,236 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 02:56:56,237 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 02:56:56,304 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-30 02:56:56,305 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-30 02:56:56,305 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e310c77190002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: 

Build failed in Jenkins: Atlas-master-UnitTests #43

2017-08-29 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2087: Allow Atlas server to bind on a specific address

--
[...truncated 444.75 KB...]
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (findbugs-check) @ 
atlas-dashboardv2 ---
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
atlas-dashboardv2 ---
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/atlas/atlas-dashboardv2/0.9-SNAPSHOT/atlas-dashboardv2-0.9-SNAPSHOT.war
[INFO] Installing 
 
to 
/home/jenkins/.m2/repository/org/apache/atlas/atlas-dashboardv2/0.9-SNAPSHOT/atlas-dashboardv2-0.9-SNAPSHOT.pom
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/atlas/atlas-dashboardv2/0.9-SNAPSHOT/atlas-dashboardv2-0.9-SNAPSHOT-sources.jar
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/atlas/atlas-dashboardv2/0.9-SNAPSHOT/atlas-dashboardv2-0.9-SNAPSHOT-test-sources.jar
[INFO] 
[INFO] 
[INFO] Building Apache Atlas Web Application 0.9-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ atlas-webapp ---
[INFO] Deleting 
 (includes = 
[**/*.pyc], excludes = [])
[INFO] 
[INFO] --- buildnumber-maven-plugin:1.4:create (default) @ atlas-webapp ---
[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildNumber: 42ccc44a9289274133528324eab02cff15ffb955 at 
timestamp: 1504058701659
[WARNING] Cannot get the branch information from the git repository: 
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- apache-rat-plugin:0.7:check (rat-check) @ atlas-webapp ---
[INFO] Exclude: **/dependency-reduced-pom.xml
[INFO] Exclude: **/javax.script.ScriptEngineFactory
[INFO] Exclude: .reviewboardrc
[INFO] Exclude: 3party-licenses/**
[INFO] Exclude: **/.cache
[INFO] Exclude: **/.cache-main
[INFO] Exclude: **/.cache-tests
[INFO] Exclude: **/.checkstyle
[INFO] Exclude: *.txt
[INFO] Exclude: **/*.json
[INFO] Exclude: .pc/**
[INFO] Exclude: debian/**
[INFO] Exclude: .svn/**
[INFO] Exclude: .git/**
[INFO] Exclude: .gitignore
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.twiki
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.json
[INFO] Exclude: **/*.log
[INFO] Exclude: **/target/**
[INFO] Exclude: **/target*/**
[INFO] Exclude: **/build/**
[INFO] Exclude: **/*.patch
[INFO] Exclude: derby.log
[INFO] Exclude: **/logs/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.project
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/mock/**
[INFO] Exclude: **/data/**
[INFO] Exclude: **/maven-eclipse.xml
[INFO] Exclude: **/.externalToolBuilders/**
[INFO] Exclude: **/build.log
[INFO] Exclude: **/.bowerrc
[INFO] Exclude: *.json
[INFO] Exclude: **/overlays/**
[INFO] Exclude: dev-support/**
[INFO] Exclude: **/users-credentials.properties
[INFO] Exclude: **/public/css/animate.min.css
[INFO] Exclude: **/public/css/bootstrap-sidebar.css
[INFO] Exclude: **/public/js/external_lib/**
[INFO] Exclude: **/node_modules/**
[INFO] Exclude: **/public/js/libs/**
[INFO] Exclude: **/atlas.data/**
[INFO] Exclude: **/${sys:atlas.data}/**
[INFO] Exclude: **/policy-store.txt
[INFO] Exclude: **/*rebel*.xml
[INFO] Exclude: **/*rebel*.xml.bak
[INFO] 
[INFO] --- maven-resources-plugin:2.7:copy-resources (copy-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 11 resources
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- 

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

2017-08-29 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2087: Allow Atlas server to bind on a specific address

--
[...truncated 412.11 KB...]
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ atlas-dashboardv2 ---
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.9.1:check (checkstyle-check) @ 
atlas-dashboardv2 ---
[INFO] 
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.1:check (findbugs-check) > :findbugs @ 
atlas-dashboardv2 >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ atlas-dashboardv2 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (findbugs-check) < :findbugs @ 
atlas-dashboardv2 <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (findbugs-check) @ 
atlas-dashboardv2 ---
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
atlas-dashboardv2 ---
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/atlas/atlas-dashboardv2/0.9-SNAPSHOT/atlas-dashboardv2-0.9-SNAPSHOT.war
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/atlas/atlas-dashboardv2/0.9-SNAPSHOT/atlas-dashboardv2-0.9-SNAPSHOT.pom
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/atlas/atlas-dashboardv2/0.9-SNAPSHOT/atlas-dashboardv2-0.9-SNAPSHOT-sources.jar
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/atlas/atlas-dashboardv2/0.9-SNAPSHOT/atlas-dashboardv2-0.9-SNAPSHOT-test-sources.jar
[INFO] 
[INFO] 
[INFO] Building Apache Atlas Web Application 0.9-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ atlas-webapp ---
[INFO] Deleting 
 
(includes = [**/*.pyc], excludes = [])
[INFO] 
[INFO] --- buildnumber-maven-plugin:1.4:create (default) @ atlas-webapp ---
[INFO] Executing: /bin/sh -c cd 
' && 
'git' 'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildNumber: 42ccc44a9289274133528324eab02cff15ffb955 at 
timestamp: 1504057295277
[WARNING] Cannot get the branch information from the git repository: 
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 
'git' 'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- apache-rat-plugin:0.7:check (rat-check) @ atlas-webapp ---
[INFO] Exclude: **/dependency-reduced-pom.xml
[INFO] Exclude: **/javax.script.ScriptEngineFactory
[INFO] Exclude: .reviewboardrc
[INFO] Exclude: 3party-licenses/**
[INFO] Exclude: **/.cache
[INFO] Exclude: **/.cache-main
[INFO] Exclude: **/.cache-tests
[INFO] Exclude: **/.checkstyle
[INFO] Exclude: *.txt
[INFO] Exclude: **/*.json
[INFO] Exclude: .pc/**
[INFO] Exclude: debian/**
[INFO] Exclude: .svn/**
[INFO] Exclude: .git/**
[INFO] Exclude: .gitignore
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.twiki
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.json
[INFO] Exclude: **/*.log
[INFO] Exclude: **/target/**
[INFO] Exclude: **/target*/**
[INFO] Exclude: **/build/**
[INFO] Exclude: **/*.patch
[INFO] Exclude: derby.log
[INFO] Exclude: **/logs/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.project
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/mock/**
[INFO] Exclude: **/data/**
[INFO] Exclude: **/maven-eclipse.xml
[INFO] Exclude: **/.externalToolBuilders/**
[INFO] Exclude: **/build.log
[INFO] Exclude: **/.bowerrc
[INFO] Exclude: *.json
[INFO] Exclude: **/overlays/**
[INFO] Exclude: dev-support/**
[INFO] Exclude: **/users-credentials.properties
[INFO] Exclude: **/public/css/animate.min.css
[INFO] Exclude: **/public/css/bootstrap-sidebar.css
[INFO] Exclude: **/public/js/external_lib/**
[INFO] Exclude: **/node_modules/**
[INFO] Exclude: **/public/js/libs/**
[INFO] Exclude: **/atlas.data/**
[INFO] Exclude: 

[jira] [Resolved] (ATLAS-2087) Allow Atlas server to bind on a specific address

2017-08-29 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj resolved ATLAS-2087.
-
Resolution: Fixed

Patch committed to master: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/42ccc44a

> Allow Atlas server to bind on a specific address
> 
>
> Key: ATLAS-2087
> URL: https://issues.apache.org/jira/browse/ATLAS-2087
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2087.2.patch, ATLAS-2087.patch
>
>
> Atlas server always bind to address "0.0.0.0":
> {code}
> connector.setHost("0.0.0.0");
> {code}
> But in many cases, user want to only run Atlas on a specified IP address 
> (e.g. private network).
> The existing property "_atlas.server.bind.address_" should be used:
> {code}
> final String addr = conf.get("atlas.server.bind.address", "0.0.0.0");
> connector.setHost(addr);
> {code}



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


[jira] [Updated] (ATLAS-2087) Allow Atlas server to bind on a specific address

2017-08-29 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj updated ATLAS-2087:

Attachment: ATLAS-2087.2.patch

[~rding] - that patch looks good. Thanks!

I committed the patch with one change - following move/rename:
  BaseSecurityTest.ATLAS_DEFAULT_HOST_ADDRESS ==> 
EmbeddedServer.ATLAS_DEFAULT_BIND_ADDRESS.



> Allow Atlas server to bind on a specific address
> 
>
> Key: ATLAS-2087
> URL: https://issues.apache.org/jira/browse/ATLAS-2087
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2087.2.patch, ATLAS-2087.patch
>
>
> Atlas server always bind to address "0.0.0.0":
> {code}
> connector.setHost("0.0.0.0");
> {code}
> But in many cases, user want to only run Atlas on a specified IP address 
> (e.g. private network).
> The existing property "_atlas.server.bind.address_" should be used:
> {code}
> final String addr = conf.get("atlas.server.bind.address", "0.0.0.0");
> connector.setHost(addr);
> {code}



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


Re: Review Request 61980: ATLAS-2087: Allow Atlas server to bind on a specific address

2017-08-29 Thread Sarath Subramanian

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


Ship it!




Ship It!

- Sarath Subramanian


On Aug. 29, 2017, 4:22 p.m., Richard Ding wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61980/
> ---
> 
> (Updated Aug. 29, 2017, 4:22 p.m.)
> 
> 
> Review request for atlas, David Radley, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2087
> https://issues.apache.org/jira/browse/ATLAS-2087
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Allow users to use existing property "atlas.server.bind.address" to specify 
> an address Atlas server binds to. If not specified, the default address 
> "0.0.0.0" is used.
> 
> 
> Diffs
> -
> 
>   webapp/src/main/java/org/apache/atlas/Atlas.java e29254b0 
>   webapp/src/main/java/org/apache/atlas/web/service/EmbeddedServer.java 
> 467571e8 
>   webapp/src/main/java/org/apache/atlas/web/service/SecureEmbeddedServer.java 
> fa02e9b9 
>   
> webapp/src/test/java/org/apache/atlas/web/filters/AtlasAuthenticationKerberosFilterTest.java
>  02a6fe40 
>   
> webapp/src/test/java/org/apache/atlas/web/security/BaseSSLAndKerberosTest.java
>  d46aa2f9 
>   webapp/src/test/java/org/apache/atlas/web/security/BaseSecurityTest.java 
> ad87025d 
>   webapp/src/test/java/org/apache/atlas/web/security/SSLTest.java 95720fdf 
>   
> webapp/src/test/java/org/apache/atlas/web/service/SecureEmbeddedServerTest.java
>  dc3b936b 
>   
> webapp/src/test/java/org/apache/atlas/web/service/SecureEmbeddedServerTestBase.java
>  41c3cb1b 
> 
> 
> Diff: https://reviews.apache.org/r/61980/diff/1/
> 
> 
> Testing
> ---
> 
> All unit tests pass.
> 
> Tested with following configurations:
> ```
> atlas.server.bind.address=0.0.0.0
> 
> atlas.server.bind.address=127.0.0.1
> 
> atlas.server.bind.address=123.45.67.89
> 
> ```
> The last is an invalid address and the server will shutdown with an error 
> message.
> 
> 
> Thanks,
> 
> Richard Ding
> 
>



Review Request 61980: ATLAS-2087: Allow Atlas server to bind on a specific address

2017-08-29 Thread Richard Ding via Review Board

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

Review request for atlas, David Radley, Madhan Neethiraj, and Sarath 
Subramanian.


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


Repository: atlas


Description
---

Allow users to use existing property "atlas.server.bind.address" to specify an 
address Atlas server binds to. If not specified, the default address "0.0.0.0" 
is used.


Diffs
-

  webapp/src/main/java/org/apache/atlas/Atlas.java e29254b0 
  webapp/src/main/java/org/apache/atlas/web/service/EmbeddedServer.java 
467571e8 
  webapp/src/main/java/org/apache/atlas/web/service/SecureEmbeddedServer.java 
fa02e9b9 
  
webapp/src/test/java/org/apache/atlas/web/filters/AtlasAuthenticationKerberosFilterTest.java
 02a6fe40 
  
webapp/src/test/java/org/apache/atlas/web/security/BaseSSLAndKerberosTest.java 
d46aa2f9 
  webapp/src/test/java/org/apache/atlas/web/security/BaseSecurityTest.java 
ad87025d 
  webapp/src/test/java/org/apache/atlas/web/security/SSLTest.java 95720fdf 
  
webapp/src/test/java/org/apache/atlas/web/service/SecureEmbeddedServerTest.java 
dc3b936b 
  
webapp/src/test/java/org/apache/atlas/web/service/SecureEmbeddedServerTestBase.java
 41c3cb1b 


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


Testing
---

All unit tests pass.

Tested with following configurations:
```
atlas.server.bind.address=0.0.0.0

atlas.server.bind.address=127.0.0.1

atlas.server.bind.address=123.45.67.89

```
The last is an invalid address and the server will shutdown with an error 
message.


Thanks,

Richard Ding



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

2017-08-29 Thread Apache Jenkins Server
See 


Changes:

[ssubramanian] ATLAS-2097: Update docs site.xml about 0.8.1 documentation and 
release

--
[...truncated 36.66 MB...]
2017-08-29 22:58:28,560 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo name (GraphToTypedInstanceMapper:144)
2017-08-29 22:58:28,560 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=name, dataType={name=string, description=null}, 
multiplicity={lower=1, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2626560] (GraphToTypedInstanceMapper:387)
2017-08-29 22:58:28,561 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.name from vertex[id=2626560 type=hive_table 
guid=d7080cf8-aad1-44b3-84dc-001711f1e204] (GraphHelper:495)
2017-08-29 22:58:28,563 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.name from vertex[id=2626560 type=hive_table 
guid=d7080cf8-aad1-44b3-84dc-001711f1e204] (GraphHelper:495)
2017-08-29 22:58:28,564 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo description (GraphToTypedInstanceMapper:144)
2017-08-29 22:58:28,564 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=description, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=false, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2626560] (GraphToTypedInstanceMapper:387)
2017-08-29 22:58:28,566 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.description from vertex[id=2626560 type=hive_table 
guid=d7080cf8-aad1-44b3-84dc-001711f1e204] (GraphHelper:495)
2017-08-29 22:58:28,567 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo owner (GraphToTypedInstanceMapper:144)
2017-08-29 22:58:28,567 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=owner, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2626560] (GraphToTypedInstanceMapper:387)
2017-08-29 22:58:28,568 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2626560 type=hive_table 
guid=d7080cf8-aad1-44b3-84dc-001711f1e204] (GraphHelper:495)
2017-08-29 22:58:28,570 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2626560 type=hive_table 
guid=d7080cf8-aad1-44b3-84dc-001711f1e204] (GraphHelper:495)
2017-08-29 22:58:28,571 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[e5e7b3b9-af44-4717-b0be-a7abcdfda205] 
(GraphBackedMetadataRepository:179)
2017-08-29 22:58:28,571 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[d3b7a02c-0bd2-40fc-a8fa-377c0db0c090] 
(GraphBackedMetadataRepository:179)
2017-08-29 22:58:28,572 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[4d99163b-353d-4010-bf30-fbc79f7b312f] 
(GraphBackedMetadataRepository:179)
2017-08-29 22:58:28,572 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[7541c541-c407-4fd0-ac6e-79d6e4ad08c9] 
(GraphBackedMetadataRepository:179)
2017-08-29 22:58:28,637 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 

[jira] [Updated] (ATLAS-2087) Allow Atlas server to bind on a specific address

2017-08-29 Thread Richard Ding (JIRA)

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

Richard Ding updated ATLAS-2087:

Attachment: ATLAS-2087.patch

> Allow Atlas server to bind on a specific address
> 
>
> Key: ATLAS-2087
> URL: https://issues.apache.org/jira/browse/ATLAS-2087
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2087.patch
>
>
> Atlas server always bind to address "0.0.0.0":
> {code}
> connector.setHost("0.0.0.0");
> {code}
> But in many cases, user want to only run Atlas on a specified IP address 
> (e.g. private network).
> The existing property "_atlas.server.bind.address_" should be used:
> {code}
> final String addr = conf.get("atlas.server.bind.address", "0.0.0.0");
> connector.setHost(addr);
> {code}



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


[jira] [Resolved] (ATLAS-2065) Release Atlas 0.8.1

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian resolved ATLAS-2065.
---
Resolution: Fixed

Apache Atlas 0.8.1 released on Aug 29, 2017.

> Release Atlas 0.8.1
> ---
>
> Key: ATLAS-2065
> URL: https://issues.apache.org/jira/browse/ATLAS-2065
> Project: Atlas
>  Issue Type: Task
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.8.1-incubating
>
>




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


[jira] [Updated] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian updated ATLAS-2097:
--
Description: 
* Update atlas docs site.xml about 0.8.1 documentation and release information
* Change pom.xml version to 0.8.2-SNAPSHOT  for branch-0.8

  was:Atlas


> Update atlas docs site.xml about 0.8.1 documentation and release information
> 
>
> Key: ATLAS-2097
> URL: https://issues.apache.org/jira/browse/ATLAS-2097
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2097.1.patch
>
>
> * Update atlas docs site.xml about 0.8.1 documentation and release information
> * Change pom.xml version to 0.8.2-SNAPSHOT  for branch-0.8



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


[jira] [Commented] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information

2017-08-29 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj commented on ATLAS-2097:
-

[~sarath.ku...@gmail.com] - the changes look good. +1 for the patch.

> Update atlas docs site.xml about 0.8.1 documentation and release information
> 
>
> Key: ATLAS-2097
> URL: https://issues.apache.org/jira/browse/ATLAS-2097
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2097.1.patch
>
>
> * Update atlas docs site.xml about 0.8.1 documentation and release information
> * Change pom.xml version to 0.8.2-SNAPSHOT  for branch-0.8



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


[jira] [Updated] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian updated ATLAS-2097:
--
Description: * Update atlas docs site.xml about 0.8.1 documentation and 
release information  (was: * Update atlas docs site.xml about 0.8.1 
documentation and release information
* Change pom.xml version to 0.8.2-SNAPSHOT  for branch-0.8)

> Update atlas docs site.xml about 0.8.1 documentation and release information
> 
>
> Key: ATLAS-2097
> URL: https://issues.apache.org/jira/browse/ATLAS-2097
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2097.1.patch
>
>
> * Update atlas docs site.xml about 0.8.1 documentation and release information



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


[jira] [Updated] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian updated ATLAS-2097:
--
Description: Atlas

> Update atlas docs site.xml about 0.8.1 documentation and release information
> 
>
> Key: ATLAS-2097
> URL: https://issues.apache.org/jira/browse/ATLAS-2097
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2097.1.patch
>
>
> Atlas



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


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

2017-08-29 Thread Madhan Neethiraj

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




webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
Lines 227 (patched)


Consider marking 'resetInterval' as final.



webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
Lines 257 (patched)


Consider renaming updateDurations() to setWaitDuration() and call from line 
#240.

void setWaitDuration() {
  long now   = System.currentTimeMillis();
  long timeSinceLastWait = now - lastWaitAt;

  if (timeSinceLastWait > resetInterval) {
waitDuration = minDuration; // reset
  } else if (waitDuration != maxDuration) {
waitDuration += increment;

if (waitDuration > maxDuration) {
  waitDuration = maxDuration;
}
  }
  
  lastWaitAt = now;
}



webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
Lines 264 (patched)


Shouldn't waitDuration be set to 'maxDuration' here? Else, the next wait 
will start from minDuration - causing more frequent retries.



webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
Lines 275 (patched)


Consider reading minWaitDuration, maxWaitDuration from configuration, right 
next to where consumerRetryInterval is read currently (line #120).

consumerRetryInterval = 
applicationProperties.getInt(CONSUMER_RETRY_INTERVAL, 500);
minWaitDuration   = applicationProperties.getInt(MIN_RETRY_INTERVAL, 
consumerRetryInterval); // 500 ms  by default
maxWaitDuration   = applicationProperties.getInt(MAX_RETRY_INTERVAL, 
minWaitDuration * 60);  //  30 sec by default



webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
Lines 279 (patched)


'pauseDuration' seems to be used only in tests; considering removing this 
member and update tests to use minWaitDuration.



webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
Line 246 (original), 306 (patched)


Why not call 'adaptiveWaiter.pause()' here as well?


- Madhan Neethiraj


On Aug. 29, 2017, 9:01 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61665/
> ---
> 
> (Updated Aug. 29, 2017, 9:01 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-2047
> https://issues.apache.org/jira/browse/ATLAS-2047
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Please refer to 
> [ATLAS-2047](https://issues.apache.org/jira/browse/ATLAS-2047) for background 
> and analysis.
> 
> **Background**
> 
> The _IllegalStateException_ is thrown by _KafkaConsumer.aquire_. This method 
> is called at the beginning of almost every method in this class. The method 
> checks if the consumer is closed, if it is then it throws 
> IllegalStateException.
> 
> Scenario may come about in this way:
> - Shutdown has been initiated. Close on consumer is called.
> - However, the consumer thread is just about to enter another poll cycle.
> - Thus acquire sees that consumer is closed and throws the exception (2nd 
> bullet above).
> 
> Please take a look at this scala code. This is _ShutdownableThread_. The 
> thread does the job of handling all exceptions. Upon exception, it manages 
> the _shutdownLatch_ (from yesterday’s bug fix) and gets out of the 
> _isRunning_ loop.
> ```scala
>   override def run(): Unit = {
> info("Starting ")
> try{
>   while(isRunning.get()){
> doWork()
>   }
> } catch{
>   case e: Throwable =>
> if(isRunning.get())
>   error("Error due to ", e)
> }
> shutdownLatch.countDown()
> info("Stopped ")
>   }
> ```
> 
> **Implementation**
> 
> Special treatment is given to _IllegalStateException_ by implementing pause & 
> retry logic:
> - Modified _LOG_ to _debug_. That way logs are not filled during retry.
> - _HookConsumer_ is more resilient. It handles exceptions resulting from 
> _Kafka_ and entity APIs.
> 
> 
> Diffs
> -
> 
>   
> webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
>  ef64c3b 
>   webapp/src/test/java/org/apache/atlas/notification/AdaptiveWaiterTest.java 
> PRE-CREATION 
>   
> webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
>  

[jira] [Updated] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian updated ATLAS-2097:
--
Fix Version/s: 0.8.1-incubating

> Update atlas docs site.xml about 0.8.1 documentation and release information
> 
>
> Key: ATLAS-2097
> URL: https://issues.apache.org/jira/browse/ATLAS-2097
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2097.1.patch
>
>




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


[jira] [Updated] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian updated ATLAS-2097:
--
Issue Type: Bug  (was: Sub-task)
Parent: (was: ATLAS-2065)

> Update atlas docs site.xml about 0.8.1 documentation and release information
> 
>
> Key: ATLAS-2097
> URL: https://issues.apache.org/jira/browse/ATLAS-2097
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2097.1.patch
>
>




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


[jira] [Updated] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian updated ATLAS-2097:
--
Affects Version/s: 0.8.1-incubating

> Update atlas docs site.xml about 0.8.1 documentation and release information
> 
>
> Key: ATLAS-2097
> URL: https://issues.apache.org/jira/browse/ATLAS-2097
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2097.1.patch
>
>




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


[ANNOUNCE] Apache Atlas 0.8.1 released

2017-08-29 Thread Sarath Subramanian
Hi All,

The Apache Atlas team is happy to announce the release of Apache Atlas -
version 0.8.1.

Atlas is a scalable and extensible set of core foundational governance
services – enabling enterprises to effectively and efficiently meet their
compliance requirements within Hadoop and allows integration with the whole
enterprise data ecosystem.


The release artifacts are available at:
http://www.apache.org/dyn/closer.cgi/atlas/0.8.1/

The binary artifacts are available from Maven central and its mirrors.


Release notes available at:
https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=blob;f=release-log.txt;hb=refs/tags/release-0.8.1-rc1

To use these artifacts, please use the following documentation:
http://atlas.apache.org/0.8.1

For more details on Apache Atlas, please visit the project website:
http://atlas.apache.org


We thank everyone who made this release possible.


Thanks,
The Apache Atlas team


[jira] [Updated] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian updated ATLAS-2097:
--
Attachment: ATLAS-2097.1.patch

> Update atlas docs site.xml about 0.8.1 documentation and release information
> 
>
> Key: ATLAS-2097
> URL: https://issues.apache.org/jira/browse/ATLAS-2097
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2097.1.patch
>
>




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


[jira] [Resolved] (ATLAS-2068) Update atlas website about 0.8.1 release

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian resolved ATLAS-2068.
---
Resolution: Fixed

> Update atlas website about 0.8.1 release
> 
>
> Key: ATLAS-2068
> URL: https://issues.apache.org/jira/browse/ATLAS-2068
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.8.1-incubating
>
>




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


[jira] [Created] (ATLAS-2097) Update atlas docs site.xml about 0.8.1 documentation and release information

2017-08-29 Thread Sarath Subramanian (JIRA)
Sarath Subramanian created ATLAS-2097:
-

 Summary: Update atlas docs site.xml about 0.8.1 documentation and 
release information
 Key: ATLAS-2097
 URL: https://issues.apache.org/jira/browse/ATLAS-2097
 Project: Atlas
  Issue Type: Sub-task
  Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
Priority: Minor
 Fix For: 0.9-incubating






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


[jira] [Commented] (ATLAS-2068) Update atlas website about 0.8.1 release

2017-08-29 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian commented on ATLAS-2068:
---

Committed to atlas-website:
https://git-wip-us.apache.org/repos/asf?p=atlas-website.git;a=commit;h=c5b7bdb3319200eb7097bbe60fd4d3e55533e5fe

> Update atlas website about 0.8.1 release
> 
>
> Key: ATLAS-2068
> URL: https://issues.apache.org/jira/browse/ATLAS-2068
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.8.1-incubating
>
>




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


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

2017-08-29 Thread Ashutosh Mestry

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

(Updated Aug. 29, 2017, 9:01 p.m.)


Review request for atlas, Madhan Neethiraj and Nixon Rodrigues.


Changes
---

Updates include:
- _AdaptiveWaiter_ implementation.
- Added unit tests for new implementation.


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


Repository: atlas


Description
---

Please refer to [ATLAS-2047](https://issues.apache.org/jira/browse/ATLAS-2047) 
for background and analysis.

**Background**

The _IllegalStateException_ is thrown by _KafkaConsumer.aquire_. This method is 
called at the beginning of almost every method in this class. The method checks 
if the consumer is closed, if it is then it throws IllegalStateException.

Scenario may come about in this way:
- Shutdown has been initiated. Close on consumer is called.
- However, the consumer thread is just about to enter another poll cycle.
- Thus acquire sees that consumer is closed and throws the exception (2nd 
bullet above).

Please take a look at this scala code. This is _ShutdownableThread_. The thread 
does the job of handling all exceptions. Upon exception, it manages the 
_shutdownLatch_ (from yesterday’s bug fix) and gets out of the _isRunning_ loop.
```scala
  override def run(): Unit = {
info("Starting ")
try{
  while(isRunning.get()){
doWork()
  }
} catch{
  case e: Throwable =>
if(isRunning.get())
  error("Error due to ", e)
}
shutdownLatch.countDown()
info("Stopped ")
  }
```

**Implementation**

Special treatment is given to _IllegalStateException_ by implementing pause & 
retry logic:
- Modified _LOG_ to _debug_. That way logs are not filled during retry.
- _HookConsumer_ is more resilient. It handles exceptions resulting from 
_Kafka_ and entity APIs.


Diffs (updated)
-

  
webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
 ef64c3b 
  webapp/src/test/java/org/apache/atlas/notification/AdaptiveWaiterTest.java 
PRE-CREATION 
  
webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
 a6f58e8 


Diff: https://reviews.apache.org/r/61665/diff/3/

Changes: https://reviews.apache.org/r/61665/diff/2-3/


Testing
---

**Unit tests**
Updated unit tests to reproduce the scenarios and verify the fix.

**Functional tests**
Verified regular notification scenarios.


Thanks,

Ashutosh Mestry



Re: Emtity Resource v1 test failures

2017-08-29 Thread Nigel Jones
I opened up ATLAS-2096 on the Dimension already exists error which I continue 
to hit today after pulling the latest master, and I also see intermittently in 
the Jenkins build.

On 2017-08-25 19:10, Sarath Subramanian  wrote: 
> 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 which also modified/read the same property,
> since Berkley DB is ACID compliant subsequent transactions times out since
> the previous transaction is not closed properly. We don't see this in HBase
> since its not an ACID compliant.
> 
> 
> Thanks,
> Sarath Subramanian
> 
> On Fri, Aug 25, 2017 at 7:10 AM, Apoorv Naik  wrote:
> 
> > 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
> > 
> > From: Nigel Jones 
> > Sent: Aug 25, 2017 5:06 AM
> > To: dev@atlas.apache.org
> > Subject: 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 I create one per failure?
> > >
> > > I'll retry
> > >
> > > Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> > 109.969 sec <<< FAILURE! - in TestSuite
> > > testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT)  Time
> > elapsed: 1.537 sec  <<< FAILURE!
> >
> > Another build, another random error - timing could be a factor (certainly
> > in the earlier test). This however is one of the build failures I had
> > yesterday. It's also been seen in the Jenkins build
> >
> >  FAILURE! - in TestSuite
> > runQuickStart(org.apache.atlas.examples.QuickStartV2IT)  Time elapsed:
> > 0.344 sec  <<< FAILURE!
> > org.apache.atlas.AtlasServiceException: Metadata service API
> > org.apache.atlas.AtlasBaseClient$APIInfo@1a990d3 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
> >
> >
> > I feel we do need to between us all try and get these tests running
> > cleanly, as it's otherwise very tempting to run skip-tests and risk
> > suggesting a change/patch that causes a failure. (I was trying to get a
> > solid baseline before trying to start on a new API)
> >
> > We could even consider a short term change to the build to not stop if any
> > known, problematic tests fail - still run, but continue. may help?
> >
> >
> 


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

2017-08-29 Thread Nigel Jones (JIRA)
Nigel Jones created ATLAS-2096:
--

 Summary: 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


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


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

2017-08-29 Thread Nigel Jones


> On Aug. 25, 2017, 7: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
> 
> Madhan Neethiraj wrote:
> I had the same question.
> 
> I think it will be better to tail Atlas log file with: 'tail -fF 
> /root/atlas-bin/logs/application.log'.
> 
> Rest of the patch is good. Thanks Nigel.
> 
> Nigel Jones wrote:
> purely a left over/oversight from hbase. I'll make that update and repost

Madhan made this change when committing it, so closing this review


- Nigel


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


On Aug. 25, 2017, 2:14 p.m., Nigel Jones wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61913/
> ---
> 
> (Updated Aug. 25, 2017, 2:14 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, David Radley, Madhan Neethiraj, and 
> Richard Ding.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2012: Build docker image
> 
> Note: Unit tests are currently not run within the docker image build process. 
> As per the JIRA it would be nice to include these but currently the tests 
> fail in many ways. This is an independent issue to the docker image work, and 
> so I propose opening a new JIRA to re-enable UT once build is stable, but 
> meanwhile we can get the docker support in
> 
> 
> Diffs
> -
> 
>   dev-support/atlas-docker/Dockerfile PRE-CREATION 
>   dev-support/atlas-docker/README.md PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/61913/diff/1/
> 
> 
> Testing
> ---
> 
> * check image can be rebuilt repeatedly
> * checker Atlas image starts up correctly
> * Run some unit tests in built image (note: see mailing list for discussion 
> about current IT test failures in builds)
> * Verified Atlas Web UI is accessible
> 
> 
> Thanks,
> 
> Nigel Jones
> 
>



[jira] [Created] (ATLAS-2095) Docker - add other interesting pieces like hive, ranger

2017-08-29 Thread Nigel Jones (JIRA)
Nigel Jones created ATLAS-2095:
--

 Summary: Docker - add other interesting pieces like hive, ranger
 Key: ATLAS-2095
 URL: https://issues.apache.org/jira/browse/ATLAS-2095
 Project: Atlas
  Issue Type: New Feature
Reporter: Nigel Jones


In ATLAS-2012, ATLAS-2093 & ATLAS-2094 we have created docker images for Atlas.

However this is 'just' Atlas. It would be interesting to have a proper data 
engine like hive contributing metadata, maybe even perhaps an enforcement 
engine like Ranger, enforcing access to the data based on business terms, 
classifications & real data. This makes it much easier to understand the scope 
of how Atlas can help.

Since this is cross component we should consider if Atlas is the right home, or 
if there are other external projects which might handle this. Also whilst we 
could build a single monolithic image, I think it would be preferable instead 
to orchestrate a number of docker containers. docker-compose is rather 
primitive, but is simple & could possibly suffice, whilst a kubernetes approach 
is more real, but requires more setup work to run 



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


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

2017-08-29 Thread Nigel Jones (JIRA)

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

Nigel Jones commented on ATLAS-2086:


In the review comments of ATLAS-2012 it was pointed out the UTs take rather a 
long time to run, so in consideration I will close this JIRA for now. We'll go 
without UTs.

> 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: Bug
>Reporter: Nigel Jones
>
> A build of a docker image for atlas was created under ATLAS-2012.
> An initial comment from David was that it would be better to build with tests 
> enabled. I agree - this makes sense in case there's something different about 
> the docker (ubuntu) environment from the host, and would be good to spot even 
> though the build takes longer
> However with Jenkins build failing regularly, and with some other 
> intermittent tests failing as per a recent mailing list discussion I am 
> instead leaving 2012 without UT, and raising this issue to re-introduce it 
> when things are stable. That way we get the docker support in, but also don't 
> forget to read testing as soon as we can.



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


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

2017-08-29 Thread Nigel Jones (JIRA)

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

Nigel Jones resolved ATLAS-2086.

Resolution: Won't Do

> 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: Bug
>Reporter: Nigel Jones
>
> A build of a docker image for atlas was created under ATLAS-2012.
> An initial comment from David was that it would be better to build with tests 
> enabled. I agree - this makes sense in case there's something different about 
> the docker (ubuntu) environment from the host, and would be good to spot even 
> though the build takes longer
> However with Jenkins build failing regularly, and with some other 
> intermittent tests failing as per a recent mailing list discussion I am 
> instead leaving 2012 without UT, and raising this issue to re-introduce it 
> when things are stable. That way we get the docker support in, but also don't 
> forget to read testing as soon as we can.



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


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

2017-08-29 Thread Nigel Jones (JIRA)

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

Nigel Jones commented on ATLAS-2012:


thanks. will raise new jira to add sample data, to make available via docker 
hub, and for thinking about combining atlas with other components (be it hive, 
ranger) for a more complete experience

> 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: 0.9-incubating
>
> Attachments: ATLAS-2012-Build-docker-image.patch, 
> atlas_docker1.patch, atlas_docker_2.patch, atlas_docker.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] [Updated] (ATLAS-2092) Failures following concurrent updates

2017-08-29 Thread Graham Wallis (JIRA)

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

Graham Wallis updated ATLAS-2092:
-
Description: There is a race condition that causes duplication of schema 
vertices as a result of concurrent graph updates. This in turn leads to failure 
of queries that specify a type such as an edge label used in an attribute that 
references another entity. This problem is known to affect Atlas entity refs – 
which create graph edges that use edge label schema vertices. It is likely that 
it also affects other types in Atlas.

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



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


[jira] [Created] (ATLAS-2092) Failures following concurrent updates

2017-08-29 Thread Graham Wallis (JIRA)
Graham Wallis created ATLAS-2092:


 Summary: Failures following concurrent updates
 Key: ATLAS-2092
 URL: https://issues.apache.org/jira/browse/ATLAS-2092
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Graham Wallis






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


[jira] [Commented] (ATLAS-1805) Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

2017-08-29 Thread Nixon Rodrigues (JIRA)

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

Nixon Rodrigues commented on ATLAS-1805:


[~cuijunheng]
Enable HBase Hook for Atlas

* cd  hbase/bin

ADD  HBase Atlas hook to the HBASE classpath.

* cat hbase
{code}
#!/bin/bash

BIGTOP_DEFAULTS_DIR=${BIGTOP_DEFAULTS_DIR-/etc/default}
[ -n "${BIGTOP_DEFAULTS_DIR}" -a -r ${BIGTOP_DEFAULTS_DIR}/hbase ] && . 
${BIGTOP_DEFAULTS_DIR}/hbase

if [ -d "atlas/hook/hbase" ]; then
  if [ -z "${HBASE_CLASSPATH}" ]; then
export HBASE_CLASSPATH=atlas/hook/hbase/*
  else
export HBASE_CLASSPATH=${HBASE_CLASSPATH}:atlas/hook/hbase/*
  fi
fi

export ATLAS_HOME=${ATLAS_HOME:-~/atlas}
export HBASE_HOME=${HBASE_HOME:-~/hbase}
export HADOOP_HOME=${HADOOP_HOME:-~/hadoop}
export HADOOP_CONF=${HADOOP_HOME}/conf
export ZOOKEEPER_HOME=${ZOOKEEPER_HOME:~/zookeeper}
export 
HBASE_CLASSPATH=$HADOOP_CONF:$HADOOP_HOME/*:$HADOOP_HOME/lib/*:$ZOOKEEPER_HOME/*:$HBASE_CLASSPATH
export HBASE_OPTS="-Dhdp.version=${HDP_VERSION} ${HBASE_OPTS}"
exec hbase/bin/hbase.distro "$@"

{code}


3)  create   atlas-application.properties in hbase/conf folder

* cat atlas-application.properties
{code}
atlas.authentication.method.kerberos=false
atlas.cluster.name=cl1
atlas.hook.hbase.keepAliveTime=10
atlas.hook.hbase.maxThreads=5
atlas.hook.hbase.minThreads=5
atlas.hook.hbase.numRetries=3
atlas.hook.hbase.queueSize=1000
atlas.hook.hbase.synchronous=false
atlas.jaas.KafkaClient.loginModuleControlFlag=required
atlas.jaas.KafkaClient.loginModuleName=com.sun.security.auth.module.Krb5LoginModule
atlas.jaas.KafkaClient.option.keyTab=/etc/security/keytabs/hbase.service.keytab
atlas.jaas.KafkaClient.option.principal=hbase/_h...@example.com
atlas.jaas.KafkaClient.option.serviceName=cstm-kafka
atlas.jaas.KafkaClient.option.storeKey=True
atlas.jaas.KafkaClient.option.useKeyTab=True
atlas.kafka.bootstrap.servers=:6667
atlas.kafka.hook.group.id=atlas
atlas.kafka.sasl.kerberos.service.name=cstm-kafka
atlas.kafka.security.protocol=PLAINTEXTSASL
atlas.kafka.zookeeper.connect=:2181
atlas.kafka.zookeeper.connection.timeout.ms=3
atlas.kafka.zookeeper.session.timeout.ms=6
atlas.kafka.zookeeper.sync.time.ms=20
atlas.notification.create.topics=True
atlas.notification.replicas=1
atlas.notification.topics=ATLAS_HOOK,ATLAS_ENTITIES
atlas.rest.address=http://:21000
{code}


4) Adding the Atlas Hook to Hbase.
In Hbase Site.xml

{code} 
hbase.coprocessor.master.classes=org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor
 {code}

 This is in addition to what is there in the property.

> Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to 
> Atlas
> ---
>
> Key: ATLAS-1805
> URL: https://issues.apache.org/jira/browse/ATLAS-1805
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
> Attachments: 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names.patch
>
>
> Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to 
> Atlas



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


Re: Review Request 61940: ATLAS-2090 : UI - Cache busting for static content (css, js)

2017-08-29 Thread keval bhatt


> On Aug. 28, 2017, 3:37 p.m., Ashutosh Mestry wrote:
> > Question: _require.js_ does not have bust parameter. Is this intentional? 
> > If yes, what is the rationale?
> > 
> > http://localhost:21000/js/libs/requirejs/require.js

Yes, it is intentional Because its library and we are not going to change it.


- keval


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


On Aug. 28, 2017, 1:22 p.m., keval bhatt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61940/
> ---
> 
> (Updated Aug. 28, 2017, 1:22 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, 
> Nixon Rodrigues, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2090
> https://issues.apache.org/jira/browse/ATLAS-2090
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Grunt task is updated to handle Cache busting issue, so now after every 
> successful build grunt task will add new time as the query string for static 
> content i.e .CSS and .JS
> 
> 
> Diffs
> -
> 
>   dashboardv2/gruntfile.js 900ee40 
>   dashboardv2/package.json 6068c79 
>   dashboardv2/public/index.html f572049 
>   dashboardv2/public/index.html.tpl PRE-CREATION 
>   dashboardv2/public/js/main.js 63e9abc 
> 
> 
> Diff: https://reviews.apache.org/r/61940/diff/1/
> 
> 
> Testing
> ---
> 
> Build the atlas code and checked the query string for static content i.e.CSS 
> and .JS, its working as expected.
> 
> 
> Thanks,
> 
> keval bhatt
> 
>