Build failed in Jenkins: apache-atlas-nightly #417

2016-08-19 Thread Apache Jenkins Server 
See 

Changes:

[sumasai.shivaprasad] ATLAS-1129 Remove notification failed logs on retry and 
add sleep

--
[...truncated 11607 lines...]
[INFO] Finished at: 2016-08-19T20:04:09+00:00
[INFO] Final Memory: 959M/2537M
[INFO] 
+ mvn deploy
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.atlas:atlas-webapp:war:0.8-incubating-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:keytool-maven-plugin is missing. @ 
org.apache.atlas:atlas-webapp:[unknown-version], 
 line 
361, column 21
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] apache-atlas
[INFO] Apache Atlas Common
[INFO] Apache Atlas Typesystem
[INFO] Apache Atlas Client
[INFO] Apache Atlas Server API
[INFO] Apache Atlas Notification
[INFO] Apache Atlas Graph Database Projects
[INFO] Apache Atlas Graph Database API
[INFO] Graph Database Common Code
[INFO] Apache Atlas Titan 0.5.4 Graph DB Impl
[INFO] Apache Atlas Repository
[INFO] Apache Atlas Authorization
[INFO] Apache Atlas Business Catalog
[INFO] Apache Atlas UI
[INFO] Apache Atlas Web Application
[INFO] Apache Atlas Documentation
[INFO] Apache Atlas FileSystem Model
[INFO] Apache Atlas Plugin Classloader
[INFO] Apache Atlas Hive Bridge Shim
[INFO] Apache Atlas Hive Bridge
[INFO] Apache Atlas Falcon Bridge Shim
[INFO] Apache Atlas Falcon Bridge
[INFO] Apache Atlas Sqoop Bridge Shim
[INFO] Apache Atlas Sqoop Bridge
[INFO] Apache Atlas Storm Bridge Shim
[INFO] Apache Atlas Storm Bridge
[INFO] Apache Atlas Distribution
[INFO] 
[INFO] 
[INFO] Building apache-atlas 0.8-incubating-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- buildnumber-maven-plugin:1.4:create (default) @ apache-atlas ---
[INFO] Executing: /bin/sh -c cd 
' && 'git' 'rev-parse' 
'--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildNumber: f408e93eebfd870f7eef547438c41260f729fdd9 at 
timestamp: 1471637055856
[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] --- maven-remote-resources-plugin:1.5:process (default) @ apache-atlas 
---
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
apache-atlas ---
[INFO] No sources to compile
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
apache-atlas ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
apache-atlas ---
[INFO] 
[INFO] --- maven-failsafe-plugin:2.19.1:integration-test (integration-test) @ 
apache-atlas ---
[INFO] 
[INFO] --- maven-source-plugin:2.4:jar-no-fork (attach-sources) @ apache-atlas 
---
[INFO] 
[INFO] --- maven-source-plugin:2.4:test-jar-no-fork (attach-sources) @ 
apache-atlas ---
[INFO] 
[INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ apache-atlas ---
[INFO] 
[INFO] --- apache-rat-plugin:0.7:check (rat-check) @ apache-atlas ---
[INFO] Exclude: **/dependency-reduced-pom.xml
[INFO] Exclude: .reviewboardrc
[INFO] Exclude: 3party-licenses/**
[INFO] Exclude: **/.cache-main
[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: **/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/**

[jira] [Commented] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Madhan Neethiraj (JIRA) 

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

Madhan Neethiraj commented on ATLAS-1129:
-

+1 for ATLAS-1129-v3.patch. Thanks [~svimal2106]

> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1129-v2.patch, ATLAS-1129-v3.patch, 
> ATLAS-1129.3.patch, ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Vimal Sharma (JIRA) 

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

Vimal Sharma updated ATLAS-1129:

Attachment: ATLAS-1129-v3.patch

Thanks [~madhan.neethiraj] for the review. I have addressed your comments in 
the new patch 

> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1129-v2.patch, ATLAS-1129-v3.patch, 
> ATLAS-1129.3.patch, ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Suma Shivaprasad (JIRA) 

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

Suma Shivaprasad updated ATLAS-1129:

Attachment: ATLAS-1129.3.patch

Bumped up retry intervals

> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1129-v2.patch, ATLAS-1129.3.patch, ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Madhan Neethiraj (JIRA) 

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

Madhan Neethiraj commented on ATLAS-1129:
-

Comments:
bq. notificationRetryInterval = 
atlasProperties.getInt(ATLAS_NOTIFICATION_RETRY_INTERVAL, 100);
Default value of 100ms seems too low. I would suggest to use default value of 
at least 2 seconds.

bq. LOG.error("Notification send retry failed");
It will help to add a little more information in the log message, like: 
LOG.error("Failed to send notification - attempt #" + numRetries + "; error=" + 
e.getMessage());

bq. LOG.info("Sleeping for {} ms before retry", notificationRetryInterval);
Consider using 'debug' log level for this message


> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1129-v2.patch, ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1130) Issue processing entity rest response in browser

2016-08-19 Thread David Radley (JIRA) 
David Radley created ATLAS-1130:
---

 Summary: Issue processing entity rest response in browser
 Key: ATLAS-1130
 URL: https://issues.apache.org/jira/browse/ATLAS-1130
 Project: Atlas
  Issue Type: Bug
Reporter: David Radley


I issue call :
http://127.0.0.1:21000/api/atlas/ entities?type=hive_table
then issue another call to get the details of the Hive table:
http://127.0.0.1:21000/api/atlas/ entities/c702a914-942b-4b70-96dd-473dc484f10c

I am in Firefox debugging and see:
"definition":{
"typeName":"hive_table",
"id":{
"typeName":"hive_table",
"id":"c702a914-942b-4b70-96dd-473dc484f10c",

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"state":"ACTIVE",
"version":0
},
"traitNames":["Fraud.Customer"],
"values":{
"createTime":"2016-07-22T12:21:27.000Z",
"db":{
"typeName":"hive_db",
"id":"9b39b886-fa83-4f18-bbf2-f93b56d56dc0",

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"state":"ACTIVE",
"version":0
},
"lastAccessTime":"2016-07-22T12:21:27.000Z",
"qualifiedName":"default.customer@Sandbox",
"sd":{
"typeName":"hive_storagedesc",
"id":{
"typeName":"hive_storagedesc",
"id":"4390715e-b4d1-441c-87aa-e84b01a96f75",

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"state":"ACTIVE",
"version":0
},
"traitNames":[],
"values":{
"sortCols":null,
"compressed":false,
"serdeInfo":{
"typeName":"hive_serde",
"values":{

"serializationLib":"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe",
"name":null,
"parameters":{
"serialization.format":",
",
"field.delim":",
"
}
},

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct"
},

"location":"hdfs:\/\/sandbox.hortonworks.com:8020\/apps\/hive\/warehouse\/customer",

"outputFormat":"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat",
"bucketCols":null,
"qualifiedName":"default.customer@Sandbox_storage",
"storedAsSubDirectories":false,
"numBuckets":-1,

"inputFormat":"org.apache.hadoop.mapred.TextInputFormat",
"table":{
"typeName":"hive_table",
"id":"c702a914-942b-4b70-96dd-473dc484f10c",

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"state":"ACTIVE",
"version":0
},

the browser debugger errors Syntax Error: JSON parse bad control character in 
string literal at line 43 column 62 of the JSON data. It does not like the 
":"," below:
   "parameters":{
   "serialization.format":",
",

I have issued the rest call in JAVA and it tolerates this JSON. As a 
circumvention I am proxying the REST call in JAVA and removing the"sd" key 
(which is the key that has this offending JSON construct).  





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Vimal Sharma (JIRA) 

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

Vimal Sharma commented on ATLAS-1129:
-

Removed warning log from KafkaNotification as well

> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-1129-v2.patch, ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Vimal Sharma (JIRA) 

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

Vimal Sharma updated ATLAS-1129:

Attachment: ATLAS-1129-v2.patch

> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-1129-v2.patch, ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Shwetha G S (JIRA) 

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

Shwetha G S commented on ATLAS-1129:


The patch looks good otherwise

> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ATLAS-921) Processing encryption ... hangs

2016-08-19 Thread Oscar Segarra (JIRA) 

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

Oscar Segarra closed ATLAS-921.
---

> Processing encryption ... hangs
> ---
>
> Key: ATLAS-921
> URL: https://issues.apache.org/jira/browse/ATLAS-921
> Project: Atlas
>  Issue Type: Bug
>Reporter: Oscar Segarra
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Shwetha G S (JIRA) 

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

Shwetha G S commented on ATLAS-1129:


In NotificationHookConsumer, move log of sleeping before Thread.sleep

> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Vimal Sharma (JIRA) 

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

Vimal Sharma updated ATLAS-1129:

Attachment: ATLAS-1129.patch

> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

2016-08-19 Thread Vimal Sharma (JIRA) 
Vimal Sharma created ATLAS-1129:
---

 Summary: Remove notification failed logs on retry and add sleep 
between retries
 Key: ATLAS-1129
 URL: https://issues.apache.org/jira/browse/ATLAS-1129
 Project: Atlas
  Issue Type: Bug
Reporter: Vimal Sharma
Assignee: Vimal Sharma


Atlas notification interface logs the exception if it cannot send the message 
successfully. Further, the retries are attempted immediately.

Remove the exception logs for individual retry and add sleep between retries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)