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

[Apache Jenkins Server]

See 


Changes:

[ssubramanian] ATLAS-2078: Type update using v1 API doesn't route to

[ssubramanian] ATLAS-2079: Fix coverity scan issue and IT failures introduced by

--
[...truncated 510.60 KB...]
127.0.0.1 - - [23/Aug/2017:06:27:23 +] "GET 
/api/atlas/entities?type=testH2gmDpK1wH HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:23 +] "GET /api/atlas/entities/blah 
HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:23 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:23 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:23 +] "GET 
/api/atlas/v2/types/typedef/name/PII_TraitVFBJfP4vzK HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:23 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST 
/api/atlas/entities/7eb5915e-6e66-46a0-82e8-b1b76fb803f3/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "GET 
/api/atlas/entities/7eb5915e-6e66-46a0-82e8-b1b76fb803f3/traitDefinitions/PII_TraitVFBJfP4vzK
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "GET 
/api/atlas/entities/7eb5915e-6e66-46a0-82e8-b1b76fb803f3/traitDefinitions 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "GET 
/api/atlas/entities/0c060373-8f97-4820-b945-06895eea50fa/traits HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST 
/api/atlas/entities/d13e0213-f814-4543-a89f-7a967428f0ed HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "GET 
/api/atlas/entities/d13e0213-f814-4543-a89f-7a967428f0ed HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST 
/api/atlas/entities/qualifiedName?type=hive_table=qualifiedName=tableNqMejYFODI
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "GET 
/api/atlas/entities/1535487c-2a10-4e87-890a-1c027916959f HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "GET 
/api/atlas/entities/bd336609-70fe-4212-b8dc-127d3bfbb330/audit?count=10 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "GET 
/api/atlas/v2/types/typedef/name/BQzqPcf99g HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:24 +] "GET 
/api/atlas/entities/4a528c2e-2ce3-488f-b70b-4472f02ff769 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:25 +] "GET 
/api/atlas/v2/entity/guid/56c331a6-a6fb-4034-9019-3f3b7e41fe88 HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:25 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:25 +] "POST 
/api/atlas/v2/entity/guid/random/classifications HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:25 +] "POST /api/atlas/v2/entity/bulk/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:25 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:25 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:27:25 +] "DELETE 

[jira] [Created] (ATLAS-2080) Search using entity and trait attributes - tag filters are also added in the "attributes" list of the POST request body

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2080:


 Summary: Search using entity and trait attributes - tag filters 
are also added in the "attributes" list of the POST request body
 Key: ATLAS-2080
 URL: https://issues.apache.org/jira/browse/ATLAS-2080
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Assignee: Keval Bhatt
Priority: Critical


1. Created a tag tag1 with attributes attrib1 (string) , attrib2 (int)
2. Fired basic search classification = tag1 and filters attrib1 = "random_str".
3. Search failed with 500 Internal server error . Because "attrib1" (which is a 
tag filter) was also considered as one of the attributes. Only attributes in 
the entity filters are expected to be added in the "attributes" list.

{code}
{
"entityFilters":null,
"tagFilters":{"condition":"AND","criterion":[{"attributeName":"attrib1","operator":"=","attributeValue":"random_str"}]},
"attributes":["attrib1"],
"query":null,
"excludeDeletedEntities":true,
"limit":25,
"typeName":null,
"classification":"tag1"
}
{code}




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

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

[Apache Jenkins Server]

See 


Changes:

[ssubramanian] ATLAS-2078: Type update using v1 API doesn't route to

[ssubramanian] ATLAS-2079: Fix coverity scan issue and IT failures introduced by

--
[...truncated 507.05 KB...]
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "GET 
/api/atlas/entities?type=testoLovePI1Y7 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "GET /api/atlas/entities/blah 
HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "GET 
/api/atlas/v2/types/typedef/name/PII_TraitquoVT9YlmT HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST 
/api/atlas/entities/c7157716-334a-4ecc-b069-5aef627c7b0c/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "GET 
/api/atlas/entities/c7157716-334a-4ecc-b069-5aef627c7b0c/traitDefinitions/PII_TraitquoVT9YlmT
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "GET 
/api/atlas/entities/c7157716-334a-4ecc-b069-5aef627c7b0c/traitDefinitions 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "GET 
/api/atlas/entities/e5a51065-a893-4587-a687-f5179568c1ef/traits HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST 
/api/atlas/entities/0fbdc1d3-1eb2-4e02-ba05-b28cb5302b88 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "GET 
/api/atlas/entities/0fbdc1d3-1eb2-4e02-ba05-b28cb5302b88 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST 
/api/atlas/entities/qualifiedName?type=hive_table=qualifiedName=tableTcgMHVtgov
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "GET 
/api/atlas/entities/b3ed8ee5-d780-404a-a4f3-850f8c81f5d1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "GET 
/api/atlas/entities/35abd2ac-1d5a-40e3-8a9e-0ae8cc6a0997/audit?count=10 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "GET 
/api/atlas/v2/types/typedef/name/rTqZj2RgYo HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "GET 
/api/atlas/entities/8d3280dd-78e9-4210-83d7-53c0d211659b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "GET 
/api/atlas/v2/entity/guid/a800b97f-6405-4014-a683-cf2eeca72ee6 HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST 
/api/atlas/v2/entity/guid/random/classifications HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST /api/atlas/v2/entity/bulk/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:06:29:19 +] "DELETE 

[jira] [Created] (ATLAS-2081) Test EntityJerseyResourceIT#testPartialUpdate fails consistently

[Sneha Kanekar (JIRA)]

Sneha Kanekar created ATLAS-2081:


 Summary: Test EntityJerseyResourceIT#testPartialUpdate fails 
consistently
 Key: ATLAS-2081
 URL: https://issues.apache.org/jira/browse/ATLAS-2081
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Affects Versions: 0.9-incubating
 Environment: Ubuntu:14.04
$java -version
openjdk version "1.8.0_111"
OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
Reporter: Sneha Kanekar


The integration test 
org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate fails 
consistently with java assertion error. The error message is as follows:
{code:borderStyle=solid}
java.lang.AssertionError: expected:<1> but was:<3>
at 
org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate(EntityJerseyResourceIT.java:881)
{code}



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

[jira] [Updated] (ATLAS-2080) Search using entity and trait attributes - tag filters are also added in the "attributes" list of the POST request body

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-2080:
---
Attachment: ATLAS-2080.patch

> Search using entity and trait attributes - tag filters are also added in the 
> "attributes" list of the POST request body
> ---
>
> Key: ATLAS-2080
> URL: https://issues.apache.org/jira/browse/ATLAS-2080
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2080.patch
>
>
> 1. Created a tag tag1 with attributes attrib1 (string) , attrib2 (int)
> 2. Fired basic search classification = tag1 and filters attrib1 = 
> "random_str".
> 3. Search failed with 500 Internal server error . Because "attrib1" (which is 
> a tag filter) was also considered as one of the attributes. Only attributes 
> in the entity filters are expected to be added in the "attributes" list.
> {code}
> {
> "entityFilters":null,
> "tagFilters":{"condition":"AND","criterion":[{"attributeName":"attrib1","operator":"=","attributeValue":"random_str"}]},
> "attributes":["attrib1"],
> "query":null,
> "excludeDeletedEntities":true,
> "limit":25,
> "typeName":null,
> "classification":"tag1"
> }
> {code}



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

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

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2049:
---
External issue URL: https://reviews.apache.org/r/61736  (was: 
https://reviews.apache.org/r/61736/#comment259238)

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



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

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

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2049:


Updated review comments (except 1) and hopefully created a correct patch that 
now mirrors what's on review board 

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



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

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

[Nigel Jones (JIRA)]

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

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

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



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

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

[Nigel Jones (JIRA)]

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

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

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



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

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

[Nigel Jones (JIRA)]

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

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

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



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

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

[Nigel Jones (JIRA)]

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

Nigel Jones reassigned ATLAS-1974:
--

Assignee: Nigel Jones

starting work on this

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



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

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

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-1974:
---
Summary: goveng omas : create skeleton implementation + generated swagger  
(was: gas omas : create skeleton implementation + generated swagger)

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



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

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

[Nigel Jones]

> On Aug. 18, 2017, 4:30 p.m., David Radley wrote:
> > docs/src/site/twiki/OMAS-Standards.twiki
> > Lines 9 (patched)
> > 
> >
> > I would not be this blunt. All of the existing applicaiton use the 
> > entity API. Instead, I suggest saying something like, 
> > " the OMAS APIs are access APIs that are not chatty and should be 
> > ideally tailors for consumers to access Atlas. As such we are looking to 
> > encourage Atlas application to move away from the lower level APIs and use 
> > the OMAS API instead.

I softened the statement slightly - though not as far as perhaps you suggested, 
to 

* Use of OMAS interfaces by applications is preferred over lower level Atlas 
interfaces

 Explanation: Whilst all existing applications use the existing Atlas API, 
the intent of OMAS is to provide a less chatty, tailored, set of interfaces 
that provide all the interactions applications need.

Is that better? I was trying to make it a specific actionable statement - I do 
think it's an important principle. We are aiming to provide full coverage 
across the suite of OMAS interfaces so that all atlas applications can find the 
function they need in an efficient form. Only when we've achieved this and have 
a critical mass could we even contemplate deprecation as there are many 
applications out there already - so this is more about best practices moving 
forward... but getting that transition started. If it's not felt we could do 
this, then why, does it mean we've missed something? Is the strategy wrong?


> On Aug. 18, 2017, 4:30 p.m., David Radley wrote:
> > docs/src/site/twiki/OMAS-Standards.twiki
> > Lines 12 (patched)
> > 
> >
> > I think you need to explain what OMRS and OMRS connectors are).

I removed this statement. However the document does still refer to OMAS, OMRS 
so the point is valid. I added an initial statement

Further background in relation to Open Metadata including explanations of OMAS, 
OMRS, may be found in the Atlas Wiki at 
https://cwiki.apache.org/confluence/display/ATLAS/Open+Metadata+and+Governance


> On Aug. 18, 2017, 4:30 p.m., David Radley wrote:
> > docs/src/site/twiki/OMAS-Standards.twiki
> > Lines 16 (patched)
> > 
> >
> > When you say "transforming, mapping data from Atlas/OMRS as required" - 
> > I suggest saying the OMAS implmentation will call the lower level resource 
> > specific APIs. I suggest not mentioning that the OMAS call Atlas - it calls 
> > OMRS which could be Atlas behind it.

I will change it to refer to OMRS only, since as you say, we could be talking 
to a non-Atlas based OMRS implementation. By definition (and given the link to 
the wiki above) these are lower level so I think just stopping there makes 
sense?

It now reads

 Explanation: OMAS interfaces are targetted at a particular type of 
consumer with the objective of making it easy for that consumer - transforming, 
mapping data from OMRS as required


> On Aug. 18, 2017, 4:30 p.m., David Radley wrote:
> > docs/src/site/twiki/OMAS-Standards.twiki
> > Lines 20 (patched)
> > 
> >
> > what do you mean by "some duplication is expected"?

I mean that the same, or very similar capability may surface through two 
different OMASs. I think this is inevitable since by definition the OMASs are 
consumer centric, and there will be some things that two different types of 
consumers may need. The chances are the information will be packaged slightly 
differently.

It;s certainly possible some applications could use multiple OMAS interfaces, 
but I think it's generally better if the functionality provided on an OMAS is 
closely tied to the type of application using it. For example a governance 
engine may need notification when an asset classification changes, so you might 
find that notification on the Governance engine omas topic, but also that same 
notification may be seen on the asset omas too, which could be monitored by the 
virtualizer. That to me makes sense ...

I added this statement to the text:

For example a change in an asset classification may be sent out through both 
the governance engine OMAS and the Asset OMAS.


> On Aug. 18, 2017, 4:30 p.m., David Radley wrote:
> > docs/src/site/twiki/OMAS-Standards.twiki
> > Lines 22 (patched)
> > 
> >
> > I think of the interface as the API - maybe we should say the 
> > implmnetaion of the OMAS interface or something like that.

Yes agreed, bad terminology from me there.

Updated to:
* OMAS implementations will use OMRS to manage the underlaying metadata (other 
than in any transitionary phase).


> On Aug. 18, 2017, 4:30 p.m., David Radley wrote:
> > 

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

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-2049:
---
External issue URL: https://reviews.apache.org/r/61736/#comment259238

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



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

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

[Nigel Jones]

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

(Updated Aug. 23, 2017, 2:25 p.m.)


Review request for atlas.


Changes
---

Updated with responses from Davids comments (except for common parms). Also 
review board should now be in sync with patch in JIRA


Repository: atlas


Description
---

ATLAS-2049 Document common standards for OMAS interfaces

As we start to build OMAS interfaces it seems having some common standards 
would be a good idea. I wanted to get this discussion going so opted to 
document this in twiki format & submit via review board. The intent isn't this 
first pass is correct, but that we come to a consensus ...

Open to suggestions as to whether this is a useful approach - Alternatives 
include
 - Simply posting on wiki - but I think we want to keep that for more consumer 
style documentation that's been agreed
 - Posting as a word doc or similar within the JIRA

See more info in the JIRA(s)

-- Nigel.


Diffs (updated)
-

  docs/src/site/twiki/OMAS-Standards.twiki PRE-CREATION 
  docs/src/site/twiki/index.twiki a8e7de9fb74bca0548eda5f5832e1e2bff3f7aec 


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

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


Testing
---

* Rebuilt twiki documentation to validate formatting, and reviewed in Safari.


Thanks,

Nigel Jones

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

[Nigel Jones (JIRA)]

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

Nigel Jones updated ATLAS-1696:
---
Description: 
Governance Engine OMAS is one of multiple consumer-centric based interfaces 
that will be added to Apache Atlas, & provides the API (REST and messaging) to 
support policy enforcement frameworks such as Apache Ranger. Detailed knowledge 
of the Atlas data models and structure can then be hidden from these consumers.

The functionality of gaf includes
 - ability to retrieve classifications associated to assets
  - restricted to "interesting" classifications 
  - restricted to interesting assets being managed by the requesting endpoint
 - to retrieve a list of interesting roles that relate to enforcement
 - to retrieve any template rule definitions/lookup tables that might be used 
to construct executable rules

The scoping constructs supported in the API will include
 - Only get classifications that are relevant for security enforcement (ie: 
only those inheriting from a specified supertype? Verify in ATLAS-1839)
 - only get information about assets (resources) in a certain part of the 
datalake (Q: HOW. By zone? How to specify? by asset type? By associated 
endpoint?)
 - pagination
 
See ATLAS-1839 for more information on the model and classifications

In the Atlas data model classifications propagate - for example
 * An database column DOB has no explicit classification
 * It's containing table CDB  is classified as "customer personal details"
 * The "SPI" classification is attached to this table with the value "sensitive"

At enforcement time all that an engine such as ranger cares about is that the 
column "DOB" is sensitive, how we got there isn't important.  In the example 
above the propogation occurs

 * Along the assigned term relationship 
 * along the structural containment relationship (table->column)

Therefore gaf omas will "flatten" the structure - so in this case we'll see
 table/CDB - SPI:sensitive
 column/DOB - SPI:sensitive

There will be cases where multiple classifications (of the same type) can be 
navigated to from an asset like DOB. This may not make logical sense, however, 
Until precedence is resolved in ATLAS-1839 & related Jiras, OMAS will pass 
through multiple classifications

This interface will also support message notifications of changes to managed 
resources such as a new role, classification. A single kafka topic will be 
used. 
 



A first pass swagger can be found at 
https://app.swaggerhub.com/apis/planetf1/GovernanceActionOMAS/0.1


NOTE: Updated 23 Aug with new name of GOVERNANCE ENGINE OMAS

  was:
Governance Action OMAS is one of multiple consumer-centric based interfaces 
that will be added to Apache Atlas, & provides the API (REST and messaging) to 
support policy enforcement frameworks such as Apache Ranger. Detailed knowledge 
of the Atlas data models and structure can then be hidden from these consumers.

The functionality of gaf includes
 - ability to retrieve classifications associated to assets
  - restricted to "interesting" classifications 
  - restricted to interesting assets being managed by the requesting endpoint
 - to retrieve a list of interesting roles that relate to enforcement
 - to retrieve any template rule definitions/lookup tables that might be used 
to construct executable rules

The scoping constructs supported in the API will include
 - Only get classifications that are relevant for security enforcement (ie: 
only those inheriting from a specified supertype? Verify in ATLAS-1839)
 - only get information about assets (resources) in a certain part of the 
datalake (Q: HOW. By zone? How to specify? by asset type? By associated 
endpoint?)
 - pagination
 
See ATLAS-1839 for more information on the model and classifications

In the Atlas data model classifications propagate - for example
 * An database column DOB has no explicit classification
 * It's containing table CDB  is classified as "customer personal details"
 * The "SPI" classification is attached to this table with the value "sensitive"

At enforcement time all that an engine such as ranger cares about is that the 
column "DOB" is sensitive, how we got there isn't important.  In the example 
above the propogation occurs

 * Along the assigned term relationship 
 * along the structural containment relationship (table->column)

Therefore gaf omas will "flatten" the structure - so in this case we'll see
 table/CDB - SPI:sensitive
 column/DOB - SPI:sensitive

There will be cases where multiple classifications (of the same type) can be 
navigated to from an asset like DOB. This may not make logical sense, however, 
Until precedence is resolved in ATLAS-1839 & related Jiras, OMAS will pass 
through multiple classifications

This interface will also support message notifications of changes to managed 
resources such as a new role, classification. A single kafka topic will be 
used. 
 

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

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues commented on ATLAS-1805:


[~rmani] Thanks for the patch.


After adding the hooks jar and configs in hbase end, I was able to verify basic 
functionality for create table in hbase to be working and Entities for 
Hbase-table and Hbase column family are getting reflected on Atlas UI.

 found one warning in atlas-application.log :

{code}
2017-08-23 07:05:13,897 WARN  - [NotificationHookConsumer thread-0:] ~ ignored 
unknown attribute hbase_table.qualifier (AtlasStructFormatConverter:161)
{code}

*+1* for this patch from my end.

> 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)

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

[Apache Jenkins Server]

See 


Changes:

[madhan] ATLAS-2080: fix - tag filters should not be added in the results

--
[...truncated 504.73 KB...]
127.0.0.1 - - [23/Aug/2017:16:52:21 +] "GET 
/api/atlas/entities/ddccf335-0a4b-459b-93b3-8979be755b69 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:21 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:21 +] "GET 
/api/atlas/entities/415b6ead-6382-4f7a-bb2d-baf960cc74f7/audit?count=100 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:21 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db+where+qualifiedName%3D'dbhOO1hzmzaX'=10=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:22 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:22 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db+where+qualifiedName%3D'dbhOO1hzmzaX'=10=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:23 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:23 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db+where+qualifiedName%3D'dbhOO1hzmzaX'=10=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "GET /api/atlas/entities?type=blah 
HTTP/1.1" 400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "DELETE 
/api/atlas/entities?guid=ce4a2ef6-84fe-4a77-b935-b639f28bf4fb=f8a2ae7c-0907-4f84-a0b9-5126fcadac25
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "GET 
/api/atlas/entities/f8a2ae7c-0907-4f84-a0b9-5126fcadac25 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "GET 
/api/atlas/entities/ce4a2ef6-84fe-4a77-b935-b639f28bf4fb HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "GET 
/api/atlas/v2/types/typedef/name/H0DWzkNIi0 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "GET 
/api/atlas/entities/7ce84cd6-845b-45ca-99c1-356d6d323934 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "DELETE 
/api/atlas/entities?guid=8d0e9387-8d9f-439e-a6fd-e33b301f96d2=f70939c2-4389-4e03-81a5-1d78ca14a9d6
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "GET 
/api/atlas/entities/f70939c2-4389-4e03-81a5-1d78ca14a9d6 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "GET 
/api/atlas/entities/8d0e9387-8d9f-439e-a6fd-e33b301f96d2 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:25 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:26 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:26 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:26 +] "POST 
/api/atlas/entities/bd1441e0-2314-475a-a951-0c7206eea28c HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:26 +] "GET 
/api/atlas/entities/bd1441e0-2314-475a-a951-0c7206eea28c HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:26 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:26 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:26 +] "GET 
/api/atlas/v2/types/typedef/name/PII_Traity8nKJfV5wd HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:16:52:27 +] "POST 
/api/atlas/entities/16bd01b7-61a4-4240-84dd-4d7e31dcd030/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"

[jira] [Commented] (ATLAS-2079) Fix IT failures introduced by ATLAS-2062

[Apoorv Naik (JIRA)]

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

Apoorv Naik commented on ATLAS-2079:


+1 Changes look good.

> Fix IT failures introduced by ATLAS-2062
> 
>
> Key: ATLAS-2079
> URL: https://issues.apache.org/jira/browse/ATLAS-2079
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>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-2079.2.patch
>
>
> Fix for coverity scan issues and following IT failures:
> Failed tests: 
>   
> NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621
>  » AtlasService
>   
> NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626
>  » 
>   EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3>
>   MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » 
> AtlasService Me...



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

[jira] [Assigned] (ATLAS-2082) Regression : Search using entity and trait attributes - Issue with capitalized string filter attributes and boolean filters

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reassigned ATLAS-2082:
---

Assignee: Madhan Neethiraj

> Regression : Search using entity and trait attributes - Issue with 
> capitalized string filter attributes and boolean filters
> ---
>
> Key: ATLAS-2082
> URL: https://issues.apache.org/jira/browse/ATLAS-2082
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2082.patch, BooleanAndCapsStringSearch.txt
>
>
> When a search is applied with 2 filters : boolean and string and if string 
> filter has capitalized characters, Atlas throws 500 Internal server error.
> Example POST body request :
> {code}
> {  
>"entityFilters":{  
>   "condition":"AND",
>   "criterion":[  
>  {  
> "attributeName":"isFile",
> "operator":"=",
> "attributeValue":"true"
>  },
>  {  
> "attributeName":"owner",
> "operator":"=",
> "attributeValue":"Hrt_qa"
>  }
>   ]
>},
>"tagFilters":null,
>"attributes":[  
>   "isFile"
>],
>"query":null,
>"excludeDeletedEntities":true,
>"limit":25,
>"typeName":"hdfs_path",
>"classification":null
> }
> {code}



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

Re: Review Request 61854: ATLAS-2082: basic-search fails when in-memory filters all results from index-query

[Sarath Subramanian]

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


Ship it!




Ship It!

- Sarath Subramanian


On Aug. 23, 2017, 10:44 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61854/
> ---
> 
> (Updated Aug. 23, 2017, 10:44 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-2082
> https://issues.apache.org/jira/browse/ATLAS-2082
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2044 introduced in-memory filtering of results returnred from 
> index-query, to address the issue of index-query returning more results than 
> expected when some special characters are present in the indexed values. When 
> this in-memory filters all results from index-query, basis-seach sent down 
> empty list of vertices to subsequent graph query - which resulted in this 
> failure. Fixed this issue by adding is-empty checks.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
>  29670bc9 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java
>  f4ac8ab7 
> 
> 
> Diff: https://reviews.apache.org/r/61854/diff/1/
> 
> 
> Testing
> ---
> 
> Verified that the search completes successfully without hitting the reported 
> error.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

[jira] [Updated] (ATLAS-2082) Regression : Search using entity and trait attributes - Issue with capitalized string filter attributes and boolean filters

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2082:

Attachment: ATLAS-2082.patch

Review board URL: https://reviews.apache.org/r/61854/

> Regression : Search using entity and trait attributes - Issue with 
> capitalized string filter attributes and boolean filters
> ---
>
> Key: ATLAS-2082
> URL: https://issues.apache.org/jira/browse/ATLAS-2082
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2082.patch, BooleanAndCapsStringSearch.txt
>
>
> When a search is applied with 2 filters : boolean and string and if string 
> filter has capitalized characters, Atlas throws 500 Internal server error.
> Example POST body request :
> {code}
> {  
>"entityFilters":{  
>   "condition":"AND",
>   "criterion":[  
>  {  
> "attributeName":"isFile",
> "operator":"=",
> "attributeValue":"true"
>  },
>  {  
> "attributeName":"owner",
> "operator":"=",
> "attributeValue":"Hrt_qa"
>  }
>   ]
>},
>"tagFilters":null,
>"attributes":[  
>   "isFile"
>],
>"query":null,
>"excludeDeletedEntities":true,
>"limit":25,
>"typeName":"hdfs_path",
>"classification":null
> }
> {code}



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

[jira] [Updated] (ATLAS-2082) Regression : Search using entity and trait attributes - Issue with capitalized string filter attributes and boolean filters

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2082:

Affects Version/s: (was: 0.9-incubating)
Fix Version/s: 0.8.1-incubating
   0.9-incubating

> Regression : Search using entity and trait attributes - Issue with 
> capitalized string filter attributes and boolean filters
> ---
>
> Key: ATLAS-2082
> URL: https://issues.apache.org/jira/browse/ATLAS-2082
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2082.patch, BooleanAndCapsStringSearch.txt
>
>
> When a search is applied with 2 filters : boolean and string and if string 
> filter has capitalized characters, Atlas throws 500 Internal server error.
> Example POST body request :
> {code}
> {  
>"entityFilters":{  
>   "condition":"AND",
>   "criterion":[  
>  {  
> "attributeName":"isFile",
> "operator":"=",
> "attributeValue":"true"
>  },
>  {  
> "attributeName":"owner",
> "operator":"=",
> "attributeValue":"Hrt_qa"
>  }
>   ]
>},
>"tagFilters":null,
>"attributes":[  
>   "isFile"
>],
>"query":null,
>"excludeDeletedEntities":true,
>"limit":25,
>"typeName":"hdfs_path",
>"classification":null
> }
> {code}



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

[jira] [Updated] (ATLAS-2079) Fix IT failures introduced by ATLAS-2062

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2079:
--
Attachment: (was: ATLAS-2079.1.patch)

> Fix IT failures introduced by ATLAS-2062
> 
>
> Key: ATLAS-2079
> URL: https://issues.apache.org/jira/browse/ATLAS-2079
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>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-2079.2.patch
>
>
> Fix for coverity scan issues and following IT failures:
> Failed tests: 
>   
> NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621
>  » AtlasService
>   
> NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626
>  » 
>   EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3>
>   MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » 
> AtlasService Me...



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

[jira] [Updated] (ATLAS-2079) Fix IT failures introduced by ATLAS-2062

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-2079:
--
Attachment: ATLAS-2079.2.patch

> Fix IT failures introduced by ATLAS-2062
> 
>
> Key: ATLAS-2079
> URL: https://issues.apache.org/jira/browse/ATLAS-2079
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>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-2079.2.patch
>
>
> Fix for coverity scan issues and following IT failures:
> Failed tests: 
>   
> NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621
>  » AtlasService
>   
> NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626
>  » 
>   EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3>
>   MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » 
> AtlasService Me...



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

[jira] [Reopened] (ATLAS-2079) Fix IT failures introduced by ATLAS-2062

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian reopened ATLAS-2079:
---

Missed few changes in last commit

> Fix IT failures introduced by ATLAS-2062
> 
>
> Key: ATLAS-2079
> URL: https://issues.apache.org/jira/browse/ATLAS-2079
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>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-2079.1.patch
>
>
> Fix for coverity scan issues and following IT failures:
> Failed tests: 
>   
> NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621
>  » AtlasService
>   
> NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626
>  » 
>   EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3>
>   MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » 
> AtlasService Me...



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

[jira] [Resolved] (ATLAS-2079) Fix IT failures introduced by ATLAS-2062

[Sarath Subramanian (JIRA)]

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

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

> Fix IT failures introduced by ATLAS-2062
> 
>
> Key: ATLAS-2079
> URL: https://issues.apache.org/jira/browse/ATLAS-2079
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>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-2079.2.patch
>
>
> Fix for coverity scan issues and following IT failures:
> Failed tests: 
>   
> NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621
>  » AtlasService
>   
> NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626
>  » 
>   EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3>
>   MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » 
> AtlasService Me...



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

Re: Review Request 61589: [ATLAS-2040]: Relationship with many-to-many cardinality gives incorrect relationship attribute value

[Sarath Subramanian]

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

(Updated Aug. 23, 2017, 10:28 a.m.)


Review request for atlas, David Radley and Madhan Neethiraj.


Changes
---

rebased patch.


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


Repository: atlas


Description
---

Relationship with many-to-many cardinality gives incorrect relationship 
attribute value when same attribute name and same type specified at both ends
When same attribute name and same type is mentioned in both ends of 
relationship definition. Creating new relationships fails to retireve the right 
value.
For e.g. employee-friends type: same attribute name 'friends' in type 
'Employee' specified at both ends
Add more unit tests to test these cases


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java 3de02d08 
  intg/src/main/java/org/apache/atlas/type/AtlasStructType.java 4304e745 
  intg/src/test/java/org/apache/atlas/TestRelationshipUtilsV2.java 98be2b8d 
  repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
0177f7e4 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
 42713763 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
 b8fd70e5 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphRetriever.java
 4e7aa473 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreHardDeleteV1Test.java
 2c311403 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreSoftDeleteV1Test.java
 33ef8c0f 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreV1Test.java
 a35647dc 


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

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


Testing
---

* added new  UTs to test many-to-many relationships on same attribute name/same 
type
* added new  UTs to test one-to-one relationships on same attribute name/same 
type
* mvn clean install -DskipITs=true suceeded without any failures


Thanks,

Sarath Subramanian

Re: Review Request 61247: [ATLAS-1984]: Use AtlasRelatedObjectId to refer to relationship attributes during entity create/update

[Sarath Subramanian]

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

(Updated Aug. 23, 2017, 10:27 a.m.)


Review request for atlas, David Radley and Madhan Neethiraj.


Changes
---

rebased patch


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


Repository: atlas


Description
---

AtlasObjectId is used to refer to entity attributes referring to another entity.
hive_table.columns => List
hive_table.db => AtlasObjectId
Change this to use AtlasRelatedObjectId with the following structure:
class AtlasRelatedObjectId
{ String relationshipGuid; String displayText; AtlasStruct 
relationshipAttributes; }


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/model/instance/AtlasRelationship.java 
41883713 
  intg/src/main/java/org/apache/atlas/model/instance/AtlasStruct.java 80f3a664 
  intg/src/main/java/org/apache/atlas/type/AtlasStructType.java 4304e745 
  intg/src/main/java/org/apache/atlas/type/AtlasTypeUtil.java 427439ca 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityGraphDiscoveryV1.java
 0210a118 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
 b8fd70e5 


Diff: https://reviews.apache.org/r/61247/diff/4/

Changes: https://reviews.apache.org/r/61247/diff/3-4/


Testing
---

Tested using POSTMAN REST client

mvn clean package - In Progress


Thanks,

Sarath Subramanian

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

[Apache Jenkins Server]

See 


Changes:

[ssubramanian] ATLAS-2079: Fix coverity scan issue and IT failures introduced by

--
[...truncated 35.40 MB...]
2017-08-23 17:46:09,967 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=2647808] (GraphToTypedInstanceMapper:387)
2017-08-23 17:46:09,968 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.description from vertex[id=2647808 type=hive_column 
guid=f60f9ace-3216-4f84-b7ad-f66484a7cff4] (GraphHelper:433)
2017-08-23 17:46:09,969 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo owner (GraphToTypedInstanceMapper:144)
2017-08-23 17:46:09,969 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=2647808] (GraphToTypedInstanceMapper:387)
2017-08-23 17:46:09,970 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2647808 type=hive_column 
guid=f60f9ace-3216-4f84-b7ad-f66484a7cff4] (GraphHelper:433)
2017-08-23 17:46:09,972 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2647808 type=hive_column 
guid=f60f9ace-3216-4f84-b7ad-f66484a7cff4] (GraphHelper:433)
2017-08-23 17:46:09,973 DEBUG - [NotificationHookConsumer thread-0:] ~ Finding 
edge for Titan0Vertex [id=2647552] -> label __hive_table.columns  
(GraphToTypedInstanceMapper:200)
2017-08-23 17:46:09,974 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property __guid from vertex[id=2648064 type=hive_column 
guid=7dc0f871-6908-4c99-83f6-a0f3b7c7f9f3] (GraphHelper:433)
2017-08-23 17:46:09,974 DEBUG - [NotificationHookConsumer thread-0:] ~ Found 
vertex Titan0Vertex [id=2648064] for label __hive_table.columns with guid 
7dc0f871-6908-4c99-83f6-a0f3b7c7f9f3 (GraphToTypedInstanceMapper:215)
2017-08-23 17:46:09,975 DEBUG - [NotificationHookConsumer thread-0:] ~ Found 
composite, mapping vertex to instance (GraphToTypedInstanceMapper:220)
2017-08-23 17:46:09,975 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
graph root vertex Titan0Vertex [id=2648064] to typed instance for guid 
7dc0f871-6908-4c99-83f6-a0f3b7c7f9f3 (GraphToTypedInstanceMapper:82)
2017-08-23 17:46:09,976 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property __typeName from vertex[id=2648064 type=hive_column 
guid=7dc0f871-6908-4c99-83f6-a0f3b7c7f9f3] (GraphHelper:433)
2017-08-23 17:46:09,980 DEBUG - [NotificationHookConsumer thread-0:] ~ Found 
createdBy : jenkins modifiedBy : jenkins createdTime: Wed Aug 23 17:46:05 UTC 
2017 modifedTime: Wed Aug 23 17:46:08 UTC 2017 (GraphToTypedInstanceMapper:95)
2017-08-23 17:46:09,982 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property __version from vertex[id=2648064 type=hive_column 
guid=7dc0f871-6908-4c99-83f6-a0f3b7c7f9f3] (GraphHelper:444)
2017-08-23 17:46:09,983 DEBUG - [NotificationHookConsumer thread-0:] ~ Created 
id (type: hive_column, id: 7dc0f871-6908-4c99-83f6-a0f3b7c7f9f3) for instance 
type hive_column (GraphToTypedInstanceMapper:102)
2017-08-23 17:46:09,983 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
vertex Titan0Vertex [id=2648064] to instance hive_column for fields 
(GraphToTypedInstanceMapper:131)
2017-08-23 17:46:09,983 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo type (GraphToTypedInstanceMapper:144)
2017-08-23 17:46:09,984 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=type, dataType={name=string, description=null}, 
multiplicity={lower=1, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2648064] (GraphToTypedInstanceMapper:387)
2017-08-23 17:46:09,985 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property hive_column.type from vertex[id=2648064 type=hive_column 
guid=7dc0f871-6908-4c99-83f6-a0f3b7c7f9f3] (GraphHelper:433)
2017-08-23 17:46:09,987 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property hive_column.type from vertex[id=2648064 type=hive_column 
guid=7dc0f871-6908-4c99-83f6-a0f3b7c7f9f3] (GraphHelper:433)
2017-08-23 17:46:09,988 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo comment (GraphToTypedInstanceMapper:144)
2017-08-23 17:46:09,989 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=comment, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=false, 

[jira] [Created] (ATLAS-2082) Regression : Search using entity and trait attributes - Issue with capitalized string filter attributes and boolean filters

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2082:


 Summary: Regression : Search using entity and trait attributes - 
Issue with capitalized string filter attributes and boolean filters
 Key: ATLAS-2082
 URL: https://issues.apache.org/jira/browse/ATLAS-2082
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Critical
 Attachments: BooleanAndCapsStringSearch.txt

When a search is applied with 2 filters : boolean and string and if string 
filter has capitalized characters, Atlas throws 500 Internal server error.
Example POST body request :
{code}
{  
   "entityFilters":{  
  "condition":"AND",
  "criterion":[  
 {  
"attributeName":"isFile",
"operator":"=",
"attributeValue":"true"
 },
 {  
"attributeName":"owner",
"operator":"=",
"attributeValue":"Hrt_qa"
 }
  ]
   },
   "tagFilters":null,
   "attributes":[  
  "isFile"
   ],
   "query":null,
   "excludeDeletedEntities":true,
   "limit":25,
   "typeName":"hdfs_path",
   "classification":null
}
{code}




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

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

[Apache Jenkins Server]

See 


Changes:

[madhan] ATLAS-2080: fix - tag filters should not be added in the results

[ssubramanian] ATLAS-2079: Fix coverity scan issue and IT failures introduced by

--
[...truncated 36.44 MB...]
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@6dbb9e18 failed with status 404 (Not 
Found) Response Body ({"error":"Instance hive_table with unique attribute 
{qualifiedName=default.tablekhabo9fwut@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.121 
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.166 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.548 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@7f3d18a6 failed with status 404 (Not 
Found) Response Body ({"error":"Instance hive_column with unique attribute 
{qualifiedName=dbblv2qpgsui.table4bchiybgb1.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.485 
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@bf5ca10 failed with status 404 (Not 
Found) Response Body ({"error":"Instance hive_table with unique attribute 
{qualifiedName=default.tabletrviye4h3c@primary} does not exist"})
at 
org.apache.atlas.hive.hook.HiveHookIT.testTruncateTable(HiveHookIT.java:1197)

testUpdateProcess(org.apache.atlas.hive.hook.HiveHookIT)  Time elapsed: 9.99 
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@37af0eaf failed with status 404 (Not 
Found) Response Body ({"error":"Instance hive_process with unique attribute 
{qualifiedName=QUERY:default.tablezgarvajuuj@primary:1503510421000->: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
  

[VOTE] Release Apache Atlas 0.8.1 - release candidate 1

[Sarath Subramanian]

Atlas team,

I have created a build for Apache Atlas 0.8.1 - release candidate #1.
Thanks to everyone who have contributed to this release and tested
this.


Changes since last release-candidate:

   - ATLAS-2038: Minor refactoring to use
org.apache.commons.codec.binary.Base64.
   - ATLAS-2073: UI - removing tag or type from drop-down will not
exclude respective filters
   - ATLAS-2074: AtlasType.resolveReferences() method made package-private
   - ATLAS-2078: Type update using v1 API doesn't route to
createUpdateTypesDef in v2 API
   - ATLAS-2079: Fix coverity scan issue and IT failures introduced by
ATLAS-2062
   - ATLAS-2080: fix - tag filters should not be added in the results
attributes list
   - ATLAS-2082: basic-search fails when in-memory filters all results
from index-query

Git tag for the release:

https://github.com/apache/atlas/tree/release-0.8.1-rc1


Sources for the release:

https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1-sources.tar.gz

Source release verification:
  PGP Signature :
https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1-sources.tar.gz.asc
  MD5 Checksum :
https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1-sources.tar.gz.md5

  SHA512 Checksum :
https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1-sources.tar.gz.sha512

Keys to verify the signature of the release artifacts are available at:

https://dist.apache.org/repos/dist/dev/atlas/KEYS


List of improvements and issues addressed in this release:

https://issues.apache.org/jira/browse/ATLAS-2066?jql=project%20%3D%20ATLAS%20AND%20status%20%3D%20Resolved%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8.1-incubating%20ORDER%20BY%20key%20DESC


Note that this is a source only release and we are voting on the
source *release-0.8.1-rc1*. Please download, test, and try it out.

Voting will be open for at least *72 hours* (until the required number
of votes are obtained) till 26th August, 2017 04:45 PM PT.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

+1 from my side for the release.


Thanks,

Sarath Subramanian

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

[Richard Ding (JIRA)]

Richard Ding created ATLAS-2083:
---

 Summary: Refactor AtlasDefStore classes to reduce code 
duplication
 Key: ATLAS-2083
 URL: https://issues.apache.org/jira/browse/ATLAS-2083
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 0.8-incubating
Reporter: Richard Ding
Assignee: Richard Ding
 Fix For: 0.9-incubating


Currently each top-level TypeDef defines its own DefStore interface. These 
interfaces have the same methods.  I suggest that we use generic interface to 
reduce the code duplication.

We can also tighten the type restriction on these interfaces. Replacing Object 
reference with AtlasVertex reference.



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

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

[Richard Ding via Review Board]

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

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


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


Repository: atlas


Description
---

1. Use generic interface to reduce code duplication
2. Move the common code in the implementation classes to the base class
3. Tighten the types required in the interface methods 
4. Move two test classes to the correct package


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasClassificationDefStore.java
 92a59f39 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasDefStore.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasEntityDefStore.java
 08391ba5 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasEnumDefStore.java
 d0f98e2f 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasRelationshipDefStore.java
 df67958b 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasStructDefStore.java
 ebd2b706 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasTypeDefGraphStore.java
 22e14436 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasAbstractDefStoreV1.java
 baf23092 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasClassificationDefStoreV1.java
 89445048 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityDefStoreV1.java
 d6cb2fd4 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEnumDefStoreV1.java
 39c4dd93 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java
 bdde58bc 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasStructDefStoreV1.java
 62729e79 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasTypeDefGraphStoreV1.java
 50a42166 
  repository/src/test/java/org/apache/atlas/TestModules.java 4bc14872 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/AtlasEntityDefStoreV1Test.java
 5f011362 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/AtlasRelationshipDefStoreV1Test.java
 00d49779 


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


Testing
---

All unit tests passed.


Thanks,

Richard Ding

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

[Apache Jenkins Server]

See 


Changes:

[madhan] ATLAS-2082: basic-search fails when in-memory filters all results from

--
[...truncated 489.57 KB...]
127.0.0.1 - - [23/Aug/2017:18:45:38 +] "GET 
/api/atlas/entities/b5434af2-7038-4e8c-927e-9d5ff1a98b45 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:38 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:38 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:38 +] "GET 
/api/atlas/v2/types/typedef/name/PII_TraitUepR7cPiRX HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:38 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:38 +] "POST 
/api/atlas/entities/bbbdd0bd-cadd-4b15-be96-2d15b5128a2b/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:38 +] "GET 
/api/atlas/entities/bbbdd0bd-cadd-4b15-be96-2d15b5128a2b/audit?count=100 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "DELETE 
/api/atlas/entities/bbbdd0bd-cadd-4b15-be96-2d15b5128a2b/traits/PII_TraitUepR7cPiRX
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "GET 
/api/atlas/entities/bbbdd0bd-cadd-4b15-be96-2d15b5128a2b/traitDefinitions/PII_TraitUepR7cPiRX
 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "GET 
/api/atlas/entities/bbbdd0bd-cadd-4b15-be96-2d15b5128a2b/audit?count=100 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "GET 
/api/atlas/entities/e239ddd1-7632-41fc-a98e-c0b92d4beef0/audit?count=10 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "GET 
/api/atlas/v2/types/typedef/name/PII_TraitB85B7kOCak HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST 
/api/atlas/entities/6b07fe83-9058-493b-97c2-4034746606a9/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST 
/api/atlas/entities/6b07fe83-9058-493b-97c2-4034746606a9/traits HTTP/1.1" 400 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST 
/api/atlas/entities/qualifiedName?type=hive_table=qualifiedName=tabletTdHLy6Amp
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "GET 
/api/atlas/entities/f90689f2-0d1b-4564-843a-225306709083 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST 
/api/atlas/entities/random/traits HTTP/1.1" 400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST 
/api/atlas/entities/ca9957fa-038d-422d-89d9-a5238dcd2d45?property=db HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "GET 
/api/atlas/v2/types/typedef/name/PII_TraitouPAcXp4Bv HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:39 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:40 +] "DELETE 
/api/atlas/entities/3dc3e1ca-992f-4466-8f00-85252bc235ee/traits/PII_TraitouPAcXp4Bv
 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:40 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:40 +] "GET 
/api/atlas/entities?type=hive_db=qualifiedName=e05XYuT9eX 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Aug/2017:18:45:40 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 

[jira] [Resolved] (ATLAS-2081) Test EntityJerseyResourceIT#testPartialUpdate fails consistently

[Sarath Subramanian (JIRA)]

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

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

Don't see this anymore from master. 

> Test EntityJerseyResourceIT#testPartialUpdate fails consistently
> 
>
> Key: ATLAS-2081
> URL: https://issues.apache.org/jira/browse/ATLAS-2081
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 0.9-incubating
> Environment: Ubuntu:14.04
> $java -version
> openjdk version "1.8.0_111"
> OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
> OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
>Reporter: Sneha Kanekar
>  Labels: ppc64le, x86
> Attachments: standard_output_log.txt
>
>
> The integration test 
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate 
> fails consistently with java assertion error. The error message is as follows:
> {code:borderStyle=solid}
> java.lang.AssertionError: expected:<1> but was:<3>
>   at 
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate(EntityJerseyResourceIT.java:881)
> {code}



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

[jira] [Commented] (ATLAS-1863) Set default value for primitive types attributes in entity based on attributeDef in Typedef

[Pierre Padovani (JIRA)]

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

Pierre Padovani commented on ATLAS-1863:


IMHO - A default value implies that the field is 'not null' *NOT* optional. 
This implies that the field is required to have a value when the entity is 
created, just that user input of the field is optional. Having a default value 
set for an optional field just doesn't make that much sense to me, however 
having it set for a field that is required makes a little more sense but still 
doesn't quite work either.

> Set default value for primitive types attributes in entity based on 
> attributeDef in Typedef
> ---
>
> Key: ATLAS-1863
> URL: https://issues.apache.org/jira/browse/ATLAS-1863
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Reporter: Nixon Rodrigues
>Assignee: Ruchi Solani
>Priority: Critical
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1863.2.patch, ATLAS-1863.3.patch, ATLAS-1863.patch
>
>
> While creating entity if attribute value are not set explicitly for primitive 
> type which are optional, then default value should be set from attributedef.
> eg of typedef attributeDef
> {code}
> "attributeDefs": [{
>   "name": "sourceCode",
>   "typeName": "string",
>   "isOptional": true,
>   "cardinality": "SINGLE",
>   "valuesMinCount": 0,
>   "valuesMaxCount": 1,
>   "isUnique": false,
>   "isIndexable": true,
>   "defaultValue": "xyz"
>   }
> {code}



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

[jira] [Commented] (ATLAS-1764) Design and implement Atlas Collections

[Pierre Padovani (JIRA)]

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

Pierre Padovani commented on ATLAS-1764:


My use case:

Consider a composite metadata entity that is made up of many (50-70+) Atlas 
entities. This composite entity is pulled in order to drive a portion of a data 
pipeline. The composite might contain things like:
* tables
* columns
* config
* target system information

Individually, the small Atlas metadata entities are useless to the data 
pipeline, only if the runtime engine has all of the metadata required will it 
be able to function.   Currently composing and decomposing an entity such as 
this requires specialized code that understands how to traverse and retrieve 
all of the pieces. Implementing a form of entity collection would allow for the 
creation of these types of composed metadata sets that could be retrieved etc. 
far easier.

> Design and implement Atlas Collections
> --
>
> Key: ATLAS-1764
> URL: https://issues.apache.org/jira/browse/ATLAS-1764
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>  Labels: features
>
> Design and implement Atlas Collections - A first class element in Atlas to 
> group related entities together and perform operations on these collections - 
> associate tags, add/remove entities...
> Operations:
> ---
> a. Create collection(s) with attributes, constraints
> b. Update existing collection(s)
> c. Delete collection(s) - soft delete, hard delete
> d. Retrieve collections by id, name
> e. Add entity(s) to collection(s)
> f. Remove entity(s) from collection(s)
> g. Associate classification(s) to collection(s)
> h. Disassociate classification(s) from collection(s)



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

[jira] [Commented] (ATLAS-2080) Search using entity and trait attributes - tag filters are also added in the "attributes" list of the POST request body

[Sharmadha Sainath (JIRA)]

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

Sharmadha Sainath commented on ATLAS-2080:
--

Verified by applying the patch on master. The tag filters are not added to the 
attributes list , only the entity filters are added.
+1

> Search using entity and trait attributes - tag filters are also added in the 
> "attributes" list of the POST request body
> ---
>
> Key: ATLAS-2080
> URL: https://issues.apache.org/jira/browse/ATLAS-2080
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2080.patch
>
>
> 1. Created a tag tag1 with attributes attrib1 (string) , attrib2 (int)
> 2. Fired basic search classification = tag1 and filters attrib1 = 
> "random_str".
> 3. Search failed with 500 Internal server error . Because "attrib1" (which is 
> a tag filter) was also considered as one of the attributes. Only attributes 
> in the entity filters are expected to be added in the "attributes" list.
> {code}
> {
> "entityFilters":null,
> "tagFilters":{"condition":"AND","criterion":[{"attributeName":"attrib1","operator":"=","attributeValue":"random_str"}]},
> "attributes":["attrib1"],
> "query":null,
> "excludeDeletedEntities":true,
> "limit":25,
> "typeName":null,
> "classification":"tag1"
> }
> {code}



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