date:20170703

Re: Review Request 60534: UI - Render HTML element based on attribute data-type while assigning Tag to entity.

2017-07-03 Thread Nixon Rodrigues


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


Ship it!




Ship It!

- Nixon Rodrigues


On June 29, 2017, 10:56 a.m., Kalyani Kashikar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60534/
> ---
> 
> (Updated June 29, 2017, 10:56 a.m.)
> 
> 
> Review request for atlas, keval bhatt, Madhan Neethiraj, and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-1897
> https://issues.apache.org/jira/browse/ATLAS-1897
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> While assigning tag to entity, It allows inputs based on attribute data-type.
> 
> 
> Note -This patch is dependent on ATLAS-1894.
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/js/views/tag/addTagModalView.js 7eaf23c 
> 
> 
> Diff: https://reviews.apache.org/r/60534/diff/1/
> 
> 
> Testing
> ---
> 
> Validation for all input field has been verified.
> 
> 
> Thanks,
> 
> Kalyani Kashikar
> 
>

[jira] [Created] (ATLAS-1916) UI - Search using entity and trait attributes - Using Date picker to change only month/year

2017-07-03 Thread Sharmadha Sainath (JIRA)

Sharmadha Sainath created ATLAS-1916:


 Summary: UI - Search using entity and trait attributes - Using 
Date picker to change only month/year
 Key: ATLAS-1916
 URL: https://issues.apache.org/jira/browse/ATLAS-1916
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
 Fix For: 0.9-incubating


1. Searched for hive_table and applied filter "Creation Time" with value 
07/05/2017 12:00 AM (Picked month year and then day) .
2.Now tried to modify only the year in the filter to 2016 using the datepicker. 
Selected 2016 from year and clicked Apply.The new value didn't persist.

If month/year is changed , date picker expects user to explicitly specify the 
day again. If day is picked , the new year/month is persisted along with day. 

But the user can change the text directly in the text box to modify year to 
2016, which works fine. 

CC : [~kevalbhatt]



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

[jira] [Updated] (ATLAS-1915) UI - Search using entity and trait attributes - Refresh Button fires the search query (Basic/DSL) again.

2017-07-03 Thread Sharmadha Sainath (JIRA)


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

Sharmadha Sainath updated ATLAS-1915:
-
Description: 
On clicking the Refresh Button to refresh types (data-id : refreshBtn) , makes 
the following 2 queries :
1./api/atlas/v2/types/typedefs/headers
2.Search query

Before the new search feature in place , only query no.1 was made. 

In Advanced search tab , when refresh button is clicked without any type or 
query , following invalid query is made in addition to query no.1
{code}
http://localhost:21000/api/atlas/v2/search?
{code}
which throws 500 Internal server error.

CC :[~kevalbhatt]

  was:
On clicking the Refresh Button to refresh types (data-id : refreshBtn) , makes 
the following 2 queries :
1./api/atlas/v2/types/typedefs/headers
2.Search query

Before the new search feature in place , only query no.1 was made. 

In Advanced search tab , when refresh button is clicked without any type or 
query , following invalid query is made in addition to query no.1
{code}
http://localhost:21000/api/atlas/v2/search?
{code}
which throws 500 Internal server error.



> UI - Search using entity and trait attributes - Refresh Button fires the 
> search query (Basic/DSL) again.
> 
>
> Key: ATLAS-1915
> URL: https://issues.apache.org/jira/browse/ATLAS-1915
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Fix For: 0.9-incubating
>
>
> On clicking the Refresh Button to refresh types (data-id : refreshBtn) , 
> makes the following 2 queries :
> 1./api/atlas/v2/types/typedefs/headers
> 2.Search query
> Before the new search feature in place , only query no.1 was made. 
> In Advanced search tab , when refresh button is clicked without any type or 
> query , following invalid query is made in addition to query no.1
> {code}
> http://localhost:21000/api/atlas/v2/search?
> {code}
> which throws 500 Internal server error.
> CC :[~kevalbhatt]



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

[jira] [Created] (ATLAS-1915) UI - Search using entity and trait attributes - Refresh Button fires the search query (Basic/DSL) again.

2017-07-03 Thread Sharmadha Sainath (JIRA)

Sharmadha Sainath created ATLAS-1915:


 Summary: UI - Search using entity and trait attributes - Refresh 
Button fires the search query (Basic/DSL) again.
 Key: ATLAS-1915
 URL: https://issues.apache.org/jira/browse/ATLAS-1915
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
 Fix For: 0.9-incubating


On clicking the Refresh Button to refresh types (data-id : refreshBtn) , makes 
the following 2 queries :
1./api/atlas/v2/types/typedefs/headers
2.Search query

Before the new search feature in place , only query no.1 was made. 

In Advanced search tab , when refresh button is clicked without any type or 
query , following invalid query is made in addition to query no.1
{code}
http://localhost:21000/api/atlas/v2/search?
{code}
which throws 500 Internal server error.




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

[jira] [Created] (ATLAS-1914) UI - Search using entity and trait attributes : "Clear" button doesn't clear the filter applied to a type

2017-07-03 Thread Sharmadha Sainath (JIRA)

Sharmadha Sainath created ATLAS-1914:


 Summary: UI - Search using entity and trait attributes : "Clear" 
button doesn't clear the filter applied to a type
 Key: ATLAS-1914
 URL: https://issues.apache.org/jira/browse/ATLAS-1914
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath


1. Searched type "hive_table" and applied filter "name = table1"
2.Clicked Search.
3.Clicked Clear button , which cleared the type selected.
4.Searched type "hive_table" again. The search had the same "name" filter 
applied before Clearing.

Expected that the Clear button would clear the filter too.

Is this expected ?
Should there be a Save button instead to explicitly save the queries ?
 
CC : [~kevalbhatt] [~apoorvnaik] [~ashutoshm][~madhan.neethiraj]






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

[jira] [Commented] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.

2017-07-03 Thread qinglin,xia (JIRA)


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

qinglin,xia commented on ATLAS-1877:


[~kevalbhatt] Hi, Bhatt, I have attached the revised patch, if you have some 
time, could you please take a look at it? 

> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
>  Labels: atlas
> Fix For: trunk, 0.9-incubating
>
> Attachments: 0001-Fix-ATLAS-1877-check-nested-supertype.patch, 
> 0001-fix-ATLAS-1877.patch, grand_child_load_process.png, 
> Process_Icon_Fixed.png, wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its 
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim 
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please 
> find attached screenshot )



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

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

2017-07-03 Thread Apache Jenkins Server

See 


Changes:

[apoorvnaik] ATLAS-1904: Relationship def validation(s)

--
[...truncated 542.25 KB...]
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "POST 
/api/atlas/entities/713503f5-3aec-4870-8eac-96c164463ff3/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "GET 
/api/atlas/entities/713503f5-3aec-4870-8eac-96c164463ff3/traitDefinitions/PII_TraitCfVpTfk4F5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "GET 
/api/atlas/entities/713503f5-3aec-4870-8eac-96c164463ff3/traitDefinitions 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "GET 
/api/atlas/entities/41c0754e-3607-4a22-909c-6797c1be2b55/traits HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "POST 
/api/atlas/entities/38509909-5f63-4913-afd4-b029cd30125a HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "GET 
/api/atlas/entities/38509909-5f63-4913-afd4-b029cd30125a HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "POST 
/api/atlas/entities/qualifiedName?type=hive_table&property=qualifiedName&value=tableVHRXMKpSeh
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "GET 
/api/atlas/entities/38509909-5f63-4913-afd4-b029cd30125a HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:34 +] "GET 
/api/atlas/entities/7c08057e-32a2-45f8-9248-65ddadb0fea1/audit?count=10 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "GET 
/api/atlas/v2/types/typedef/name/wrOmJv9rfH HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "GET 
/api/atlas/entities/41adc111-df18-40a3-8fb8-83e7852c1ccd HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "GET 
/api/atlas/v2/entity/guid/951b22ee-c790-47d0-a57c-0d9f46b88ed6 HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST 
/api/atlas/v2/entity/guid/random/classifications HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/v2/entity/bulk/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "DELETE 
/api/atlas/v2/entity/bulk/?guid=bb894357-e795-46be-b976-fd84babd6275&guid=28c49011-f90c-4fad-a173-3ca73a3b72e0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "DELETE 
/api/atlas/v2/entity/uniqueAttribute/type/hive_db_v2?attr:name=dbUXVqaUnbwb%EF%AF%9F%E6%9E%AB%EE%86%88%E4%A9%AC%EC%B4%BA%E5%AB%BA%ED%85%BA%C9%BF%EA%B1%A6%E0%A7%AD
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "DELETE 
/api/atlas/v2/entity/guid/random/classification/blah_trait HTTP/1.1" 400 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:35 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db_v2+where+name%3D'dbUXVqaUnbwb'&limit=10&offset=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:21:16:36 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db_v2+wher

Re: Review Request 60532: ATLAS-1904

2017-07-03 Thread Apoorv Naik


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


Ship it!




I've committed the patch on master. Thanks David

- Apoorv Naik


On June 29, 2017, 10:03 a.m., David Radley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60532/
> ---
> 
> (Updated June 29, 2017, 10:03 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-1904. I have cleaned the code up in the validation logic to resolve 
> this issue. I have refactored the junit so the names are more intuitive and 
> it tests this case.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 
> 49ead6e39e623a617cd3c90405bb41a348f79624 
>   intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java 
> f85cf35cc229c9e4b3e54984ae21a9a312cebd96 
>   intg/src/test/java/org/apache/atlas/type/TestAtlasRelationshipType.java 
> 41aac8fb976f15c33765d91f5c2f973b78b232a7 
> 
> 
> Diff: https://reviews.apache.org/r/60532/diff/1/
> 
> 
> Testing
> ---
> 
> Ran junits and created a composition relationshipDef as expected.
> 
> 
> Thanks,
> 
> David Radley
> 
>

Re: Review Request 60532: ATLAS-1904

2017-07-03 Thread Apoorv Naik


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


Ship it!




Ship It!

- Apoorv Naik


On June 29, 2017, 10:03 a.m., David Radley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60532/
> ---
> 
> (Updated June 29, 2017, 10:03 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-1904. I have cleaned the code up in the validation logic to resolve 
> this issue. I have refactored the junit so the names are more intuitive and 
> it tests this case.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 
> 49ead6e39e623a617cd3c90405bb41a348f79624 
>   intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java 
> f85cf35cc229c9e4b3e54984ae21a9a312cebd96 
>   intg/src/test/java/org/apache/atlas/type/TestAtlasRelationshipType.java 
> 41aac8fb976f15c33765d91f5c2f973b78b232a7 
> 
> 
> Diff: https://reviews.apache.org/r/60532/diff/1/
> 
> 
> Testing
> ---
> 
> Ran junits and created a composition relationshipDef as expected.
> 
> 
> Thanks,
> 
> David Radley
> 
>

[jira] [Commented] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header

2017-07-03 Thread Nixon Rodrigues (JIRA)


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

Nixon Rodrigues commented on ATLAS-1906:



Currently Atlas Client supports UGI & Basic Auth, as part of this jira i have 
overloaded the Atlas Client constructor to support Knox SSO cookie by adding 
below constructor.

AtlasClient(atlasURL, cookieName, CookieValue, path, domain);
AtlasClient(atlasURL, Cookie);

Added patch ATLAS-1906.patch for it.

> Atlas client should support setting hadoop-jwt token in header
> --
>
> Key: ATLAS-1906
> URL: https://issues.apache.org/jira/browse/ATLAS-1906
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Hemanth Yamijala
>Assignee: Apoorv Naik
> Attachments: 
> 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, 
> ATLAS-1906.patch
>
>
> In ATLAS-1767, support was added to make the Atlas REST API calls take a 
> hadoop-jwt token coming from Knox SSO and authenticate the user.
> This works perfectly when using a vanilla HTTP client. We have found it 
> convenient to use the Atlas client Java binding for our work. However, it 
> does not seem to support setting the hadoop-jwt token. Hence, we don't seem 
> to be able to use it with a Knox SSO enabled Atlas server for API calls.
> Could this support be added please?



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

[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header

2017-07-03 Thread Nixon Rodrigues (JIRA)


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

Nixon Rodrigues updated ATLAS-1906:
---
Attachment: ATLAS-1906.patch

> Atlas client should support setting hadoop-jwt token in header
> --
>
> Key: ATLAS-1906
> URL: https://issues.apache.org/jira/browse/ATLAS-1906
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Hemanth Yamijala
>Assignee: Apoorv Naik
> Attachments: 
> 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, 
> ATLAS-1906.patch
>
>
> In ATLAS-1767, support was added to make the Atlas REST API calls take a 
> hadoop-jwt token coming from Knox SSO and authenticate the user.
> This works perfectly when using a vanilla HTTP client. We have found it 
> convenient to use the Atlas client Java binding for our work. However, it 
> does not seem to support setting the hadoop-jwt token. Hence, we don't seem 
> to be able to use it with a Knox SSO enabled Atlas server for API calls.
> Could this support be added please?



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

Review Request 60627: ATLAS-1906 :- Atlas client should support setting hadoop-jwt token in header

2017-07-03 Thread Nixon Rodrigues


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

Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, 
Sarath Subramanian, and Hemanth Yamijala.


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


Repository: atlas


Description
---

This patch adds support to AtlasClient(Rest) to add Knox SSO Cookie as 
authentication header for Atlas.

Currently Atlas Client supports UGI & Basic Auth, as part of this jira i will 
overload the Atlas Client constructor to support Knox SSO cookie by adding 
below constructor.

AtlasClient(atlasURL, cookieName, CookieValue, path, domain);
AtlasClient(atlasURL, Cookie);


Diffs
-

  client/src/main/java/org/apache/atlas/AtlasAdminClient.java b61b2bf 
  client/src/main/java/org/apache/atlas/AtlasBaseClient.java 98da51e 
  client/src/main/java/org/apache/atlas/AtlasClient.java ec482da 
  client/src/main/java/org/apache/atlas/AtlasClientV2.java 7e287e7 
  common/src/main/java/org/apache/atlas/utils/AuthenticationUtil.java 09d8085 


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


Testing
---

Unit test cases are running fine using mvn clean install.
Ran Quick Start and Atlas admin script using the new Atlasclient Constructor.

AltasClient(atlasUrl, new Cookie("hadoop-jwt" , 
"eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJhZG1pbiIsImlzcyI6IktOT1hTU08iLCJleHAiOjE1MDE5NzUzNTV9.K7lTaXniXJtrdkXAG_k7MwhWpL363NPC75fA4hvY7ilNXCOr-_gVV-ZLndVxMGFmbSl-cLHv3ormDH2W2hvUQhUDvXg3QN5iQGlEoVDPjO6O1yoNnMBW0VgVhAbSimRQ5NTMgAF09gkTsPIfG8Qhu2kcvkKEMFOfcsDyrKn2cRM");


Thanks,

Nixon Rodrigues

[jira] [Commented] (ATLAS-1913) Fix ODF build process in feature-odf branch

2017-07-03 Thread Robert Kern (JIRA)


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

Robert Kern commented on ATLAS-1913:


For some reason I cannot assign this issue to myself. Assumably, I don't have 
the right authorization.

> Fix ODF build process in feature-odf branch
> ---
>
> Key: ATLAS-1913
> URL: https://issues.apache.org/jira/browse/ATLAS-1913
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Reporter: Robert Kern
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix ODF build issues introduced by package rename.



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

[jira] [Commented] (ATLAS-1913) Fix ODF build process in feature-odf branch

2017-07-03 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ATLAS-1913:
---

GitHub user robkern opened a pull request:

https://github.com/apache/incubator-atlas/pull/38

ATLAS-1913: Fix ODF build process in feature-odf branch

This pull request fixes some ODF build issues that were caused by 
inconsistent and missing package names, copyright headers in files which do not 
support comments, and a missing source code file. The pull request also fixes a 
node and npm version incompatibility and removes an outdated Jenkins 
documentation page.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/robkern/incubator-atlas 
robkern_fix_feature_odf_build_issues

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/38.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #38


commit 21925d18fd9527e16a7a7a19ae2ec5f1da4c6e92
Author: Robert Kern 
Date:   2017-07-03T16:11:06Z

Fix ODF build issues introduced by package rename

commit d74f50a94d13c527f0227f68227bbda1b01dd67e
Author: Robert Kern 
Date:   2017-07-03T17:33:19Z

Replace misleading license headers in markdown files




> Fix ODF build process in feature-odf branch
> ---
>
> Key: ATLAS-1913
> URL: https://issues.apache.org/jira/browse/ATLAS-1913
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Reporter: Robert Kern
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Fix ODF build issues introduced by package rename.



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

[GitHub] incubator-atlas pull request #38: ATLAS-1913: Fix ODF build process in featu...

2017-07-03 Thread robkern

GitHub user robkern opened a pull request:

https://github.com/apache/incubator-atlas/pull/38

ATLAS-1913: Fix ODF build process in feature-odf branch

This pull request fixes some ODF build issues that were caused by 
inconsistent and missing package names, copyright headers in files which do not 
support comments, and a missing source code file. The pull request also fixes a 
node and npm version incompatibility and removes an outdated Jenkins 
documentation page.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/robkern/incubator-atlas 
robkern_fix_feature_odf_build_issues

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/38.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #38


commit 21925d18fd9527e16a7a7a19ae2ec5f1da4c6e92
Author: Robert Kern 
Date:   2017-07-03T16:11:06Z

Fix ODF build issues introduced by package rename

commit d74f50a94d13c527f0227f68227bbda1b01dd67e
Author: Robert Kern 
Date:   2017-07-03T17:33:19Z

Replace misleading license headers in markdown files




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Review Request 60603: ATLAS-1906: Support for custom header(s) in AtlasClient

2017-07-03 Thread Apoorv Naik


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

Review request for atlas.


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


Repository: atlas


Description
---

New capability exposed under V1 and V2 client. 
```java
  setHeader(String name, String value)
  setHeaders(Map headers)
```

PS: Due to code rearrangement the diff is much bigger


Diffs
-

  client/src/main/java/org/apache/atlas/AtlasBaseClient.java 98da51e3 


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


Testing
---

Setting custom header(s) was successful


Thanks,

Apoorv Naik

[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header

2017-07-03 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-1906:
---
Attachment: 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch

AtlasClient can now set custom header(s)

> Atlas client should support setting hadoop-jwt token in header
> --
>
> Key: ATLAS-1906
> URL: https://issues.apache.org/jira/browse/ATLAS-1906
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Hemanth Yamijala
>Assignee: Apoorv Naik
> Attachments: 
> 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch
>
>
> In ATLAS-1767, support was added to make the Atlas REST API calls take a 
> hadoop-jwt token coming from Knox SSO and authenticate the user.
> This works perfectly when using a vanilla HTTP client. We have found it 
> convenient to use the Atlas client Java binding for our work. However, it 
> does not seem to support setting the hadoop-jwt token. Hence, we don't seem 
> to be able to use it with a Knox SSO enabled Atlas server for API calls.
> Could this support be added please?



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

[jira] [Assigned] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header

2017-07-03 Thread Apoorv Naik (JIRA)


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

Apoorv Naik reassigned ATLAS-1906:
--

Assignee: Apoorv Naik

> Atlas client should support setting hadoop-jwt token in header
> --
>
> Key: ATLAS-1906
> URL: https://issues.apache.org/jira/browse/ATLAS-1906
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Hemanth Yamijala
>Assignee: Apoorv Naik
>
> In ATLAS-1767, support was added to make the Atlas REST API calls take a 
> hadoop-jwt token coming from Knox SSO and authenticate the user.
> This works perfectly when using a vanilla HTTP client. We have found it 
> convenient to use the Atlas client Java binding for our work. However, it 
> does not seem to support setting the hadoop-jwt token. Hence, we don't seem 
> to be able to use it with a Knox SSO enabled Atlas server for API calls.
> Could this support be added please?



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

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

2017-07-03 Thread Apache Jenkins Server

See 


Changes:

[apoorvnaik] Coverity fixes for ATLAS-1880

--
[...truncated 542.59 KB...]
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "POST 
/api/atlas/entities/8e5c322a-d44e-422e-bfa6-808508ee9a0d/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "GET 
/api/atlas/entities/8e5c322a-d44e-422e-bfa6-808508ee9a0d/traitDefinitions/PII_TraitlVstMVv9EX
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "GET 
/api/atlas/entities/8e5c322a-d44e-422e-bfa6-808508ee9a0d/traitDefinitions 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "GET 
/api/atlas/entities/a043e8ba-48e8-4209-bf2d-6e86f4d9e066/traits HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "POST 
/api/atlas/entities/d9eaa61b-79d4-4d24-a4ba-788d90a7db6a HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "GET 
/api/atlas/entities/d9eaa61b-79d4-4d24-a4ba-788d90a7db6a HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "POST 
/api/atlas/entities/qualifiedName?type=hive_table&property=qualifiedName&value=tableWapGVxid9z
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:43 +] "GET 
/api/atlas/entities/d9eaa61b-79d4-4d24-a4ba-788d90a7db6a HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "GET 
/api/atlas/entities/712ac803-bcb5-454c-b2b0-c7515500edbb/audit?count=10 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "GET 
/api/atlas/v2/types/typedef/name/X25n4r7frO HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "GET 
/api/atlas/entities/8b3ee56f-e7df-408e-bcda-df13a37092b6 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "GET 
/api/atlas/v2/entity/guid/1dc20ef1-b1db-40d5-aae1-2f33bc4b6fe1 HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST 
/api/atlas/v2/entity/guid/random/classifications HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:44 +] "POST /api/atlas/v2/entity/bulk/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:45 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:45 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:45 +] "DELETE 
/api/atlas/v2/entity/bulk/?guid=eadd1714-3b07-49aa-bd10-4177a6e8ba44&guid=a87eeb19-4f53-4f9f-a119-0adfb4b372c7
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:45 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:45 +] "DELETE 
/api/atlas/v2/entity/uniqueAttribute/type/hive_db_v2?attr:name=dbj6cBWM3ddQ%E4%87%B0%E3%9A%A6%E0%B6%A9%E0%AD%89%E2%8E%83%E6%BB%82%ED%90%85%EE%80%B3%E4%AC%A5%E7%96%87
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:45 +] "DELETE 
/api/atlas/v2/entity/guid/random/classification/blah_trait HTTP/1.1" 400 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:45 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db_v2+where+name%3D'dbj6cBWM3ddQ'&limit=10&offset=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [03/Jul/2017:17:02:46 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db_v2+where+name%3D'

[jira] [Created] (ATLAS-1913) Fix ODF build process in feature-odf branch

2017-07-03 Thread Robert Kern (JIRA)

Robert Kern created ATLAS-1913:
--

 Summary: Fix ODF build process in feature-odf branch
 Key: ATLAS-1913
 URL: https://issues.apache.org/jira/browse/ATLAS-1913
 Project: Atlas
  Issue Type: Sub-task
  Components:  atlas-core
Reporter: Robert Kern


Fix ODF build issues introduced by package rename.



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

[jira] [Assigned] (ATLAS-1698) Create Glossary OMAS API

2017-07-03 Thread David Radley (JIRA)


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

David Radley reassigned ATLAS-1698:
---

Assignee: David Radley

> Create Glossary OMAS API
> 
>
> Key: ATLAS-1698
> URL: https://issues.apache.org/jira/browse/ATLAS-1698
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
>
> The Glossary OMAS provides a specialized API for glossary applications to 
> retrieve and store their glossary metadata and link assets of different types 
> to these glossary entries.
> The Glossary OMAS makes heavy use of the Area 2 open metadata model.  See 
> https://cwiki.apache.org/confluence/display/ATLAS/Area+2+-+Glossary



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

[jira] [Commented] (ATLAS-1696) Governance Action Framework OMAS

2017-07-03 Thread David Radley (JIRA)


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

David Radley commented on ATLAS-1696:
-

[~jonesn] Some comments on the Swagger:
comments on the Swagger : 
- how are we defining tags vs classifications. /v2/gaf/tags is the uri, but the 
description is "Get all classifications". It is inconsistent. 
-  /v2/gaf/roles - get list of roles assigned to entities. I would think that 
the endpoint should be assigned roles or return all the roles Atlas knows 
about.  

I suggest we do not mention Ranger in the API docs and keep the GAF 
implementaton neutral. 

> Governance Action Framework OMAS
> 
>
> Key: ATLAS-1696
> URL: https://issues.apache.org/jira/browse/ATLAS-1696
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>  Labels: VirtualDataConnector
>
> 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. 
>  
> A first pass swagger can be found at 
> https://app.swaggerhub.com/apis/planetf1/GovernanceActionOMAS/0.1



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

[jira] [Commented] (ATLAS-1898) Initial commit to feature-odf branch

2017-07-03 Thread Robert Kern (JIRA)


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

Robert Kern commented on ATLAS-1898:


The ODF build process currently fails, mainly due to package naming 
inconsistencies and missing package references in .json and .properties files. 
I have created a fix for that. How should I apply it to the *feature-odf* 
branch? Should I create a separate issue?

> Initial commit to feature-odf branch
> 
>
> Key: ATLAS-1898
> URL: https://issues.apache.org/jira/browse/ATLAS-1898
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Reporter: Mandy Chessell
>  Labels: open-metadata
> Attachments: 0001-ATLAS-1898-initial-commit-of-ODF.patch, 
> 0002-ATLAS-1898-initial-commit-of-ODF.patch
>
>
> This is the initial commit of the ODF code.  The changes from the initial IBM 
> code drop basically change java package names from com.ibm.iis.odf.* to 
> org.apache.atlas.odf.*.  There are still references to IBM Box directories 
> where deployment scripts look for the Atlas build.  these scripts need 
> rethinking as we make the ODF a buildable component of Atlas



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

Review Request 60601: ATLAS-1012 Coverity issues raised in AtlasRelationshipDefStoreV1

2017-07-03 Thread David Radley


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

Review request for atlas and Madhan Neethiraj.


Repository: atlas


Description
---

** CID 164823:  Null pointer dereferences  (NULL_RETURNS)

/repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java:
 88 in 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipDefStoreV1.preCreate(org.apache.atlas.model.typedef.AtlasRelationshipDef)()




*** CID 164823:  Null pointer dereferences  (NULL_RETURNS)

/repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java:
 88 in 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipDefStoreV1.preCreate(org.apache.atlas.model.typedef.AtlasRelationshipDef)()
82 final String type1 = endDef1.getType();
83 final AtlasRelationshipEndDef endDef2 = 
relationshipDef.getEndDef2();
84 final String type2 = endDef2.getType();
85 final String name1 = endDef1.getName();
86 final String name2 = endDef2.getName();
87 
>>> CID 164823:  Null pointer dereferences  (NULL_RETURNS)
>>> Assigning: "end1TypeVertex" = null return value from 
"findTypeVertexByName".
88 AtlasVertex end1TypeVertex = 
typeDefStore.findTypeVertexByName(type1);
89 
90 AtlasVertex end2TypeVertex = 
typeDefStore.findTypeVertexByName(type2);
91 // create an edge between the relationshipDef and each of 
the entityDef vertices.
92 AtlasEdge edge1 = 
typeDefStore.getOrCreateEdge(relationshipDefVertex, end1TypeVertex, 
AtlasGraphUtilsV1.RELATIONSHIPTYPE_EDGE_LABEL);


Diffs
-

  intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 
49ead6e39e623a617cd3c90405bb41a348f79624 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java
 bd7416e6f699773e7477c89b9fcdfb2fccacdcfc 


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


Testing
---

Ran units tests 
Created a relationshipDef.


Thanks,

David Radley

[jira] [Assigned] (ATLAS-1912) Coverity issue in AtlasRelationshipDefStoreV1

2017-07-03 Thread David Radley (JIRA)


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

David Radley reassigned ATLAS-1912:
---

Assignee: David Radley

https://reviews.apache.org/r/60601/

> Coverity issue in AtlasRelationshipDefStoreV1
> -
>
> Key: ATLAS-1912
> URL: https://issues.apache.org/jira/browse/ATLAS-1912
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>Assignee: David Radley
>
> ** CID 164823:  Null pointer dereferences  (NULL_RETURNS)
> 
> /repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java:
>  88 in 
> org.apache.atlas.repository.store.graph.v1.AtlasRelationshipDefStoreV1.preCreate(org.apache.atlas.model.typedef.AtlasRelationshipDef)()
> 
> 
> 
> 
> *** CID 164823:  Null pointer dereferences  (NULL_RETURNS)
> 
> /repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java:
>  88 in 
> org.apache.atlas.repository.store.graph.v1.AtlasRelationshipDefStoreV1.preCreate(org.apache.atlas.model.typedef.AtlasRelationshipDef)()
> 82 final String type1 = endDef1.getType();
> 83 final AtlasRelationshipEndDef endDef2 = 
> relationshipDef.getEndDef2();
> 84 final String type2 = endDef2.getType();
> 85 final String name1 = endDef1.getName();
> 86 final String name2 = endDef2.getName();
> 87 
> >>> CID 164823:  Null pointer dereferences  (NULL_RETURNS)
> >>> Assigning: "end1TypeVertex" = null return value from 
> "findTypeVertexByName".
> 88 AtlasVertex end1TypeVertex = 
> typeDefStore.findTypeVertexByName(type1);
> 89 
> 90 AtlasVertex end2TypeVertex = 
> typeDefStore.findTypeVertexByName(type2);
> 91 // create an edge between the relationshipDef and each of 
> the entityDef vertices.
> 92 AtlasEdge edge1 = 
> typeDefStore.getOrCreateEdge(relationshipDefVertex, end1TypeVertex, 
> AtlasGraphUtilsV1.RELATIONSHIPTYPE_EDGE_LABEL);



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

[jira] [Created] (ATLAS-1912) Coverity issue in AtlasRelationshipDefStoreV1

2017-07-03 Thread David Radley (JIRA)

David Radley created ATLAS-1912:
---

 Summary: Coverity issue in AtlasRelationshipDefStoreV1
 Key: ATLAS-1912
 URL: https://issues.apache.org/jira/browse/ATLAS-1912
 Project: Atlas
  Issue Type: Bug
Reporter: David Radley


** CID 164823:  Null pointer dereferences  (NULL_RETURNS)

/repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java:
 88 in 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipDefStoreV1.preCreate(org.apache.atlas.model.typedef.AtlasRelationshipDef)()




*** CID 164823:  Null pointer dereferences  (NULL_RETURNS)

/repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java:
 88 in 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipDefStoreV1.preCreate(org.apache.atlas.model.typedef.AtlasRelationshipDef)()
82 final String type1 = endDef1.getType();
83 final AtlasRelationshipEndDef endDef2 = 
relationshipDef.getEndDef2();
84 final String type2 = endDef2.getType();
85 final String name1 = endDef1.getName();
86 final String name2 = endDef2.getName();
87 
>>> CID 164823:  Null pointer dereferences  (NULL_RETURNS)
>>> Assigning: "end1TypeVertex" = null return value from 
"findTypeVertexByName".
88 AtlasVertex end1TypeVertex = 
typeDefStore.findTypeVertexByName(type1);
89 
90 AtlasVertex end2TypeVertex = 
typeDefStore.findTypeVertexByName(type2);
91 // create an edge between the relationshipDef and each of 
the entityDef vertices.
92 AtlasEdge edge1 = 
typeDefStore.getOrCreateEdge(relationshipDefVertex, end1TypeVertex, 
AtlasGraphUtilsV1.RELATIONSHIPTYPE_EDGE_LABEL);



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

Re: Review Request 60532: ATLAS-1904

2017-07-03 Thread David Radley



> On June 29, 2017, 5:12 p.m., Sarath Subramanian wrote:
> > Ship It!
> 
> David Radley wrote:
> Hi Srath - please could you commit this, David.

typo sorry Sarath


- David


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


On June 29, 2017, 10:03 a.m., David Radley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60532/
> ---
> 
> (Updated June 29, 2017, 10:03 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-1904. I have cleaned the code up in the validation logic to resolve 
> this issue. I have refactored the junit so the names are more intuitive and 
> it tests this case.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 
> 49ead6e39e623a617cd3c90405bb41a348f79624 
>   intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java 
> f85cf35cc229c9e4b3e54984ae21a9a312cebd96 
>   intg/src/test/java/org/apache/atlas/type/TestAtlasRelationshipType.java 
> 41aac8fb976f15c33765d91f5c2f973b78b232a7 
> 
> 
> Diff: https://reviews.apache.org/r/60532/diff/1/
> 
> 
> Testing
> ---
> 
> Ran junits and created a composition relationshipDef as expected.
> 
> 
> Thanks,
> 
> David Radley
> 
>

Re: Review Request 60532: ATLAS-1904

2017-07-03 Thread David Radley



> On June 29, 2017, 5:12 p.m., Sarath Subramanian wrote:
> > Ship It!

Hi Srath - please could you commit this, David.


- David


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


On June 29, 2017, 10:03 a.m., David Radley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60532/
> ---
> 
> (Updated June 29, 2017, 10:03 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-1904. I have cleaned the code up in the validation logic to resolve 
> this issue. I have refactored the junit so the names are more intuitive and 
> it tests this case.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 
> 49ead6e39e623a617cd3c90405bb41a348f79624 
>   intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java 
> f85cf35cc229c9e4b3e54984ae21a9a312cebd96 
>   intg/src/test/java/org/apache/atlas/type/TestAtlasRelationshipType.java 
> 41aac8fb976f15c33765d91f5c2f973b78b232a7 
> 
> 
> Diff: https://reviews.apache.org/r/60532/diff/1/
> 
> 
> Testing
> ---
> 
> Ran junits and created a composition relationshipDef as expected.
> 
> 
> Thanks,
> 
> David Radley
> 
>

[jira] [Updated] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.

2017-07-03 Thread Nixon Rodrigues (JIRA)


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

Nixon Rodrigues updated ATLAS-1908:
---
Attachment: ATLAS-1908.patch

> Updating old Kafka consumer api properties to reflect change in new 
> KafkaConsumer configs for Atlas.
> 
>
> Key: ATLAS-1908
> URL: https://issues.apache.org/jira/browse/ATLAS-1908
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
> Attachments: ATLAS-1908.patch
>
>
> In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer 
> api.
> Due to this update, there were changes in configs.
>  
> New property:
> atlas.kafka.session.timeout.ms=3
>  
> Renamed property:
> atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false
>  
> New default value:
> atlas.kafka.auto.offset.reset=smallest to 
> atlas.kafka.auto.offset.reset=earliest
> Need to handle old configs, so that Kafka consumer starts gracefully even if 
> new configs are not added explicitly.



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

Review Request 60597: ATLAS-1908 : - Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas

2017-07-03 Thread Nixon Rodrigues


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

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


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


Repository: atlas


Description
---

This patch handles old kafka consumer configs values to be added as new configs 
if new configs are not present , so that Kafka consumer starts gracefully even 
if new configs are not added explicitly.

eg. atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false
atlas.kafka.auto.offset.reset=smallest to 
atlas.kafka.auto.offset.reset=earliest
atlas.kafka.session.timeout.ms=3

Also added poll.timeout.ms in configs so kafka consumer can be 
configurable.This involve change in AtlasKafkaConsumer receive interface.


Diffs
-

  distro/src/conf/atlas-application.properties 474f253 
  notification/src/main/java/org/apache/atlas/kafka/AtlasKafkaConsumer.java 
9c15243 
  notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
366c8a7 
  
notification/src/main/java/org/apache/atlas/notification/NotificationConsumer.java
 22e40f9 
  notification/src/test/java/org/apache/atlas/kafka/KafkaConsumerTest.java 
70059cb 
  notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationTest.java 
c791d43 
  
notification/src/test/java/org/apache/atlas/notification/AbstractNotificationConsumerTest.java
 8324b57 
  
webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
 9e5b864 
  
webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerKafkaTest.java
 650ca0a 
  webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
c036cfa 


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


Testing
---

Executed UT/IT's using mvn clean install.
Tested KafkaConsumer with Hive Hook by creating table in hive.
Atlas starts gracefully and Kafka consumer is up without error when new 
properties are not added.


Thanks,

Nixon Rodrigues

[jira] [Assigned] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.

2017-07-03 Thread Nixon Rodrigues (JIRA)


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

Nixon Rodrigues reassigned ATLAS-1908:
--

Assignee: Nixon Rodrigues

> Updating old Kafka consumer api properties to reflect change in new 
> KafkaConsumer configs for Atlas.
> 
>
> Key: ATLAS-1908
> URL: https://issues.apache.org/jira/browse/ATLAS-1908
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Attachments: ATLAS-1908.patch
>
>
> In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer 
> api.
> Due to this update, there were changes in configs.
>  
> New property:
> atlas.kafka.session.timeout.ms=3
>  
> Renamed property:
> atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false
>  
> New default value:
> atlas.kafka.auto.offset.reset=smallest to 
> atlas.kafka.auto.offset.reset=earliest
> Need to handle old configs, so that Kafka consumer starts gracefully even if 
> new configs are not added explicitly.



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

[jira] [Created] (ATLAS-1911) UI / Search using entity and trait attributes : Specifying no value for one of the filters makes the complete filter null.

2017-07-03 Thread Sharmadha Sainath (JIRA)

Sharmadha Sainath created ATLAS-1911:


 Summary: UI / Search using entity and trait attributes : 
Specifying no value for one of the filters makes the complete filter null.
 Key: ATLAS-1911
 URL: https://issues.apache.org/jira/browse/ATLAS-1911
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath


1.Created a kafka_topic with name="kt1" and empty description.
2.Searched kafka_topic in typeName , applied filters:
 1. Name = kt1 
 2. Description =  (empty Description)
3.The body sent to POST request is :
{code}
{"entityFilters":null,"tagFilters":null,"query":null,"excludeDeletedEntities":true,"limit":25,"typeName":"kafka_topic","classification":null}
{code}
entityFilters is null , and the Name applied filter was not found in UI or in 
the request body.The search result was similar to typeName='kafka_topic'.

The same applies to tag filters.




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

[jira] [Commented] (ATLAS-1910) Classpath issue in import-hive.sh script

2017-07-03 Thread Benjamin BONNET (JIRA)


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

Benjamin BONNET commented on ATLAS-1910:


Inverting the order of HADOOP_CLASSPATH and  HIVE_CLASSPATH computation does 
the trick.
Please see : https://github.com/apache/incubator-atlas/pull/37

> Classpath issue in import-hive.sh script
> 
>
> Key: ATLAS-1910
> URL: https://issues.apache.org/jira/browse/ATLAS-1910
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.8-incubating, 0.9-incubating
> Environment: HDP2.6 sandbox
>Reporter: Benjamin BONNET
>
> Hi,
> trying to run Hive bridge, I get the following error :
> {{
> [root@sandbox hook-bin]# ./import-hive.sh
> /usr/hdp/2.6.0.3-8/hadoop/conf:/usr/hdp/2.6.0.3-8/hadoop/lib/*:/usr/hdp/2.6.0.3-8/hadoop/.//*:/usr/hdp/2.6.0.3-8/hadoop-hdfs/./:/usr/hdp/2.6.0.3-8/hadoop-hdfs/lib/*:/usr/hdp/2.6.0.3-8/hadoop-hdfs/.//*:/usr/hdp/2.6.0.3-8/hadoop-yarn/lib/*:/usr/hdp/2.6.0.3-8/hadoop-yarn/.//*:/usr/hdp/2.6.0.3-8/hadoop-mapreduce/lib/*:/usr/hdp/2.6.0.3-8/hadoop-mapreduce/.//*::jdbc-mysql.jar:mysql-connector-java-5.1.17.jar:mysql-connector-java-5.1.37.jar:mysql-connector-java.jar:/usr/hdp/2.6.0.3-8/tez/*:/usr/hdp/2.6.0.3-8/tez/lib/*:/usr/hdp/2.6.0.3-8/tez/conf
> Using Hive configuration directory [/etc/hive/conf]
> Log file for import is /usr/hdp/current/atlas-client/logs/import-hive.log
> CP=:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-client-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-common-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-notification-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/gson-2.5.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/guice-multibindings-4.1.0.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/hdfs-model-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/hive-bridge-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-ast_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-core_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-native_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/kafka_2.11-0.10.1.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/kafka-clients-0.10.1.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-compiler-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-library-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scalap-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-reflect-2.11.8.jar:/etc/hive/conf:/usr/hdp/current/atlas-client/../hive/lib/accumulo-core-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-fate-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-start-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-trace-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/activation-1.1.jar:/usr/hdp/current/atlas-client/../hive/lib/ant-1.9.1.jar:/usr/hdp/current/atlas-client/../hive/lib/ant-launcher-1.9.1.jar:/usr/hdp/current/atlas-client/../hive/lib/antlr-2.7.7.jar:/usr/hdp/current/atlas-client/../hive/lib/antlr-runtime-3.4.jar:/usr/hdp/current/atlas-client/../hive/lib/apache-log4j-extras-1.2.17.jar:/usr/hdp/current/atlas-client/../hive/lib/asm-commons-3.1.jar:/usr/hdp/current/atlas-client/../hive/lib/asm-tree-3.1.jar:/usr/hdp/current/atlas-client/../hive/lib/avatica-1.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/avatica-metrics-1.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/avro-1.7.5.jar:/usr/hdp/current/atlas-client/../hive/lib/bonecp-0.8.0.RELEASE.jar:/usr/hdp/current/atlas-client/../hive/lib/calcite-core-1.2.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/calcite-linq4j-1.2.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-cli-1.2.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-codec-1.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-collections-3.2.2.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-compiler-2.7.6.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-compress-1.4.1.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-dbcp-1.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-httpclient-3.0.1.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-io-2.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-lang-2.6.jar:/u

[jira] [Commented] (ATLAS-1910) Classpath issue in import-hive.sh script

2017-07-03 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on ATLAS-1910:
---

GitHub user bonnetb opened a pull request:

https://github.com/apache/incubator-atlas/pull/37

ATLAS-1910 : Hive Bridge Classpath issue

Classpath issue in import-hive.sh script

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bonnetb/incubator-atlas patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/37.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #37


commit 1f70b8257da360f0f8252957caf37ea877c05a65
Author: Benjamin BONNET 
Date:   2017-07-03T12:02:56Z

ATLAS-1910 : Hive Bridge Classpath issue

Classpath issue in import-hive.sh script




> Classpath issue in import-hive.sh script
> 
>
> Key: ATLAS-1910
> URL: https://issues.apache.org/jira/browse/ATLAS-1910
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.8-incubating, 0.9-incubating
> Environment: HDP2.6 sandbox
>Reporter: Benjamin BONNET
>
> Hi,
> trying to run Hive bridge, I get the following error :
> {{
> [root@sandbox hook-bin]# ./import-hive.sh
> /usr/hdp/2.6.0.3-8/hadoop/conf:/usr/hdp/2.6.0.3-8/hadoop/lib/*:/usr/hdp/2.6.0.3-8/hadoop/.//*:/usr/hdp/2.6.0.3-8/hadoop-hdfs/./:/usr/hdp/2.6.0.3-8/hadoop-hdfs/lib/*:/usr/hdp/2.6.0.3-8/hadoop-hdfs/.//*:/usr/hdp/2.6.0.3-8/hadoop-yarn/lib/*:/usr/hdp/2.6.0.3-8/hadoop-yarn/.//*:/usr/hdp/2.6.0.3-8/hadoop-mapreduce/lib/*:/usr/hdp/2.6.0.3-8/hadoop-mapreduce/.//*::jdbc-mysql.jar:mysql-connector-java-5.1.17.jar:mysql-connector-java-5.1.37.jar:mysql-connector-java.jar:/usr/hdp/2.6.0.3-8/tez/*:/usr/hdp/2.6.0.3-8/tez/lib/*:/usr/hdp/2.6.0.3-8/tez/conf
> Using Hive configuration directory [/etc/hive/conf]
> Log file for import is /usr/hdp/current/atlas-client/logs/import-hive.log
> CP=:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-client-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-common-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-notification-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/gson-2.5.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/guice-multibindings-4.1.0.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/hdfs-model-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/hive-bridge-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-ast_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-core_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-native_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/kafka_2.11-0.10.1.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/kafka-clients-0.10.1.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-compiler-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-library-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scalap-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-reflect-2.11.8.jar:/etc/hive/conf:/usr/hdp/current/atlas-client/../hive/lib/accumulo-core-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-fate-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-start-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-trace-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/activation-1.1.jar:/usr/hdp/current/atlas-client/../hive/lib/ant-1.9.1.jar:/usr/hdp/current/atlas-client/../hive/lib/ant-launcher-1.9.1.jar:/usr/hdp/current/atlas-client/../hive/lib/antlr-2.7.7.jar:/usr/hdp/current/atlas-client/../hive/lib/antlr-runtime-3.4.jar:/usr/hdp/current/atlas-client/../hive/lib/apache-log4j-extras-1.2.17.jar:/usr/hdp/current/atlas-client/../hive/lib/asm-commons-3.1.jar:/usr/hdp/current/atlas-client/../hive/lib/asm-tree-3.1.jar:/usr/hdp/current/atlas-client/../hive/lib/avatica-1.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/avatica-metrics-1.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/avro-1.7.5.jar:/usr/hdp/current/atlas-client/../hive/lib/bonecp-0.8.0.RELEASE.jar:/usr/hdp/current/atlas-client/../hive/lib/calcite-core-1.2.0.2.6.0.3-8.jar:/usr/hdp/cu

[GitHub] incubator-atlas pull request #37: ATLAS-1910 : Hive Bridge Classpath issue

2017-07-03 Thread bonnetb

GitHub user bonnetb opened a pull request:

https://github.com/apache/incubator-atlas/pull/37

ATLAS-1910 : Hive Bridge Classpath issue

Classpath issue in import-hive.sh script

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bonnetb/incubator-atlas patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/37.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #37


commit 1f70b8257da360f0f8252957caf37ea877c05a65
Author: Benjamin BONNET 
Date:   2017-07-03T12:02:56Z

ATLAS-1910 : Hive Bridge Classpath issue

Classpath issue in import-hive.sh script




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (ATLAS-1910) Classpath issue in import-hive.sh script

2017-07-03 Thread Benjamin BONNET (JIRA)


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

Benjamin BONNET updated ATLAS-1910:
---
Description: 
Hi,
trying to run Hive bridge, I get the following error :

{{
[root@sandbox hook-bin]# ./import-hive.sh
/usr/hdp/2.6.0.3-8/hadoop/conf:/usr/hdp/2.6.0.3-8/hadoop/lib/*:/usr/hdp/2.6.0.3-8/hadoop/.//*:/usr/hdp/2.6.0.3-8/hadoop-hdfs/./:/usr/hdp/2.6.0.3-8/hadoop-hdfs/lib/*:/usr/hdp/2.6.0.3-8/hadoop-hdfs/.//*:/usr/hdp/2.6.0.3-8/hadoop-yarn/lib/*:/usr/hdp/2.6.0.3-8/hadoop-yarn/.//*:/usr/hdp/2.6.0.3-8/hadoop-mapreduce/lib/*:/usr/hdp/2.6.0.3-8/hadoop-mapreduce/.//*::jdbc-mysql.jar:mysql-connector-java-5.1.17.jar:mysql-connector-java-5.1.37.jar:mysql-connector-java.jar:/usr/hdp/2.6.0.3-8/tez/*:/usr/hdp/2.6.0.3-8/tez/lib/*:/usr/hdp/2.6.0.3-8/tez/conf
Using Hive configuration directory [/etc/hive/conf]
Log file for import is /usr/hdp/current/atlas-client/logs/import-hive.log
CP=:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-client-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-common-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-notification-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/gson-2.5.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/guice-multibindings-4.1.0.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/hdfs-model-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/hive-bridge-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-ast_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-core_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-native_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/kafka_2.11-0.10.1.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/kafka-clients-0.10.1.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-compiler-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-library-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scalap-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-reflect-2.11.8.jar:/etc/hive/conf:/usr/hdp/current/atlas-client/../hive/lib/accumulo-core-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-fate-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-start-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-trace-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/activation-1.1.jar:/usr/hdp/current/atlas-client/../hive/lib/ant-1.9.1.jar:/usr/hdp/current/atlas-client/../hive/lib/ant-launcher-1.9.1.jar:/usr/hdp/current/atlas-client/../hive/lib/antlr-2.7.7.jar:/usr/hdp/current/atlas-client/../hive/lib/antlr-runtime-3.4.jar:/usr/hdp/current/atlas-client/../hive/lib/apache-log4j-extras-1.2.17.jar:/usr/hdp/current/atlas-client/../hive/lib/asm-commons-3.1.jar:/usr/hdp/current/atlas-client/../hive/lib/asm-tree-3.1.jar:/usr/hdp/current/atlas-client/../hive/lib/avatica-1.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/avatica-metrics-1.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/avro-1.7.5.jar:/usr/hdp/current/atlas-client/../hive/lib/bonecp-0.8.0.RELEASE.jar:/usr/hdp/current/atlas-client/../hive/lib/calcite-core-1.2.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/calcite-linq4j-1.2.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-cli-1.2.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-codec-1.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-collections-3.2.2.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-compiler-2.7.6.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-compress-1.4.1.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-dbcp-1.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-httpclient-3.0.1.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-io-2.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-lang-2.6.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-logging-1.1.3.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-math-2.1.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-pool-1.5.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-vfs2-2.0.jar:/usr/hdp/current/atlas-client/../hive/lib/curator-client-2.6.0.jar:/usr/hdp/current/atlas-client/../hive/lib/curator-framework-2.6.0.jar:/usr/hdp/current/atlas-client/../hive/lib/curator-recipes-2.6.0.jar:/usr/hdp/current/atlas-client/../hive/lib/datanucleus-api-jdo-4.2.1.jar:/usr/hdp/current/atlas-client/../hive/lib/datanucleus-core-4.1.6

[jira] [Created] (ATLAS-1910) Classpath issue in import-hive.sh script

2017-07-03 Thread Benjamin BONNET (JIRA)

Benjamin BONNET created ATLAS-1910:
--

 Summary: Classpath issue in import-hive.sh script
 Key: ATLAS-1910
 URL: https://issues.apache.org/jira/browse/ATLAS-1910
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.8-incubating, trunk, 0.9-incubating
 Environment: HDP2.6 sandbox
Reporter: Benjamin BONNET


Hi,
trying to run Hive bridge, I get the following error :

{{[root@sandbox hook-bin]# ./import-hive.sh
/usr/hdp/2.6.0.3-8/hadoop/conf:/usr/hdp/2.6.0.3-8/hadoop/lib/*:/usr/hdp/2.6.0.3-8/hadoop/.//*:/usr/hdp/2.6.0.3-8/hadoop-hdfs/./:/usr/hdp/2.6.0.3-8/hadoop-hdfs/lib/*:/usr/hdp/2.6.0.3-8/hadoop-hdfs/.//*:/usr/hdp/2.6.0.3-8/hadoop-yarn/lib/*:/usr/hdp/2.6.0.3-8/hadoop-yarn/.//*:/usr/hdp/2.6.0.3-8/hadoop-mapreduce/lib/*:/usr/hdp/2.6.0.3-8/hadoop-mapreduce/.//*::jdbc-mysql.jar:mysql-connector-java-5.1.17.jar:mysql-connector-java-5.1.37.jar:mysql-connector-java.jar:/usr/hdp/2.6.0.3-8/tez/*:/usr/hdp/2.6.0.3-8/tez/lib/*:/usr/hdp/2.6.0.3-8/tez/conf
Using Hive configuration directory [/etc/hive/conf]
Log file for import is /usr/hdp/current/atlas-client/logs/import-hive.log
CP=:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-client-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-common-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-notification-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/gson-2.5.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/guice-multibindings-4.1.0.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/hdfs-model-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/hive-bridge-0.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-ast_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-core_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/json4s-native_2.11-3.2.11.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/kafka_2.11-0.10.1.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/kafka-clients-0.10.1.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-compiler-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-library-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scalap-2.11.8.jar:/usr/hdp/current/atlas-client/hook/hive/atlas-hive-plugin-impl/scala-reflect-2.11.8.jar:/etc/hive/conf:/usr/hdp/current/atlas-client/../hive/lib/accumulo-core-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-fate-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-start-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/accumulo-trace-1.7.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/activation-1.1.jar:/usr/hdp/current/atlas-client/../hive/lib/ant-1.9.1.jar:/usr/hdp/current/atlas-client/../hive/lib/ant-launcher-1.9.1.jar:/usr/hdp/current/atlas-client/../hive/lib/antlr-2.7.7.jar:/usr/hdp/current/atlas-client/../hive/lib/antlr-runtime-3.4.jar:/usr/hdp/current/atlas-client/../hive/lib/apache-log4j-extras-1.2.17.jar:/usr/hdp/current/atlas-client/../hive/lib/asm-commons-3.1.jar:/usr/hdp/current/atlas-client/../hive/lib/asm-tree-3.1.jar:/usr/hdp/current/atlas-client/../hive/lib/avatica-1.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/avatica-metrics-1.8.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/avro-1.7.5.jar:/usr/hdp/current/atlas-client/../hive/lib/bonecp-0.8.0.RELEASE.jar:/usr/hdp/current/atlas-client/../hive/lib/calcite-core-1.2.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/calcite-linq4j-1.2.0.2.6.0.3-8.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-cli-1.2.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-codec-1.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-collections-3.2.2.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-compiler-2.7.6.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-compress-1.4.1.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-dbcp-1.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-httpclient-3.0.1.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-io-2.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-lang-2.6.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-logging-1.1.3.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-math-2.1.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-pool-1.5.4.jar:/usr/hdp/current/atlas-client/../hive/lib/commons-vfs2-2.0.jar:/usr/hdp/current/atlas-client/../hive/lib/curator-client-2.6.0.jar:/usr/hdp/current/atlas-client/../hive/lib/curator-framework

[jira] [Created] (ATLAS-1909) Import/Export : Exception while using "transforms" option during import

2017-07-03 Thread Sharmadha Sainath (JIRA)

Sharmadha Sainath created ATLAS-1909:


 Summary: Import/Export : Exception while using "transforms" option 
during import
 Key: ATLAS-1909
 URL: https://issues.apache.org/jira/browse/ATLAS-1909
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Blocker
 Attachments: Import_transforms_error.txt

1. Created a table t5 in cluster1.
2. Created the export zip file for table t5 on firing export API on cluster1.
3. Created the t5transforms.json file 
{code}
{

  "options": {

   "transforms": {
"hive_table": {
  "qualifiedName": [
"replace:@cl1:@cl2"
  ]
}
  }
}
  }
{code}
4.Fired import API on cluster2 using curl call :

{code}
curl -v -g -X POST -u admin:admin -H "Content-Type: multipart/form-data" -H 
"Cache-Control: no-cache" -F request=@t5transforms.json -F data=@t5.zip 
"http://cluster2:21000/api/atlas/admin/import";
{code}

Request failed with 500 Internal server error and the following message :
{code}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
 java.lang.NullPointerException"}
{code}

Attached the complete exception stack trace found in cluster2's  application 
logs.




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

Re: Review Request 60578: [ATLA-1907]: Create RelationshipDefs for all base models and use this definitions when creating edges for entities

2017-07-03 Thread Mandy Chessell


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



The Atlas WIKI has UML diagrams of each of the current models. They are located 
on child pages under 
https://cwiki.apache.org/confluence/display/ATLAS/Atlas+Model
I am happy to update the diagrams is you create me a subtask for this Jira

- Mandy Chessell


On June 30, 2017, 8:25 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60578/
> ---
> 
> (Updated June 30, 2017, 8:25 p.m.)
> 
> 
> Review request for atlas, David Radley and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-1907
> https://issues.apache.org/jira/browse/ATLAS-1907
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Create relationshipDefs for all out of the box models. Use relationshipDef 
> information when creating edges for composite attributes in entities.
> 
> 
> Diffs
> -
> 
>   addons/models/0010-base_model.json 7f64d85e 
>   addons/models/0030-hive_model.json b359ea82 
>   addons/models/0050-falcon_model.json b7398ef4 
>   addons/models/0060-hbase_model.json 42fe00c4 
>   addons/models/0080-storm_model.json 095936e0 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 49ead6e3 
>   intg/src/main/java/org/apache/atlas/model/instance/AtlasRelationship.java 
> 8d2e7ec5 
>   intg/src/main/java/org/apache/atlas/type/AtlasEntityType.java 70e3067a 
>   intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java 
> f85cf35c 
>   intg/src/main/java/org/apache/atlas/type/AtlasStructType.java c2e0be50 
>   intg/src/main/java/org/apache/atlas/type/AtlasTypeRegistry.java 29fae1c8 
>   
> repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
>  4530f51b 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
>  5ea4ff20 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasGraphUtilsV1.java
>  7b3f1e6e 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreV1.java
>  86212338 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
>  ebf6a201 
>   
> repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreV1Test.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/60578/diff/1/
> 
> 
> Testing
> ---
> 
> Tested using Postman REST client.
> Validated all hive_table creation works fine and lineage is rendered right.
> 
> UTs/ITs in progress.
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 60578: [ATLA-1907]: Create RelationshipDefs for all base models and use this definitions when creating edges for entities

2017-07-03 Thread Mandy Chessell


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



Please rename the following JSON files to permit the common model 
(https://issues.apache.org/jira/browse/ATLAS-1768) to be inserted between 0010 
Base Model and the Hadoop models.

* 1020 FS Model
* 1030 Hive Model
* 1040 Sqoop Model
* 1050 Falcon Model
* 1060 HBase Model
* 1070 Kafka Model
* 1080 Storm Model

- Mandy Chessell


On June 30, 2017, 8:25 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60578/
> ---
> 
> (Updated June 30, 2017, 8:25 p.m.)
> 
> 
> Review request for atlas, David Radley and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-1907
> https://issues.apache.org/jira/browse/ATLAS-1907
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Create relationshipDefs for all out of the box models. Use relationshipDef 
> information when creating edges for composite attributes in entities.
> 
> 
> Diffs
> -
> 
>   addons/models/0010-base_model.json 7f64d85e 
>   addons/models/0030-hive_model.json b359ea82 
>   addons/models/0050-falcon_model.json b7398ef4 
>   addons/models/0060-hbase_model.json 42fe00c4 
>   addons/models/0080-storm_model.json 095936e0 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 49ead6e3 
>   intg/src/main/java/org/apache/atlas/model/instance/AtlasRelationship.java 
> 8d2e7ec5 
>   intg/src/main/java/org/apache/atlas/type/AtlasEntityType.java 70e3067a 
>   intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java 
> f85cf35c 
>   intg/src/main/java/org/apache/atlas/type/AtlasStructType.java c2e0be50 
>   intg/src/main/java/org/apache/atlas/type/AtlasTypeRegistry.java 29fae1c8 
>   
> repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
>  4530f51b 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
>  5ea4ff20 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasGraphUtilsV1.java
>  7b3f1e6e 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreV1.java
>  86212338 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
>  ebf6a201 
>   
> repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreV1Test.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/60578/diff/1/
> 
> 
> Testing
> ---
> 
> Tested using Postman REST client.
> Validated all hive_table creation works fine and lineage is rendered right.
> 
> UTs/ITs in progress.
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

[jira] [Created] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.

2017-07-03 Thread Nixon Rodrigues (JIRA)

Nixon Rodrigues created ATLAS-1908:
--

 Summary: Updating old Kafka consumer api properties to reflect 
change in new KafkaConsumer configs for Atlas.
 Key: ATLAS-1908
 URL: https://issues.apache.org/jira/browse/ATLAS-1908
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer 
api.
Due to this update, there were changes in configs.
 
New property:
atlas.kafka.session.timeout.ms=3
 
Renamed property:
atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false
 
New default value:
atlas.kafka.auto.offset.reset=smallest to atlas.kafka.auto.offset.reset=earliest

Need to handle old configs, so that Kafka consumer starts gracefully even if 
new configs are not added explicitly.





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

[jira] [Comment Edited] (ATLAS-1766) Atlas with Kafka SASL_SSL protocol

2017-07-03 Thread Nixon Rodrigues (JIRA)


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

Nixon Rodrigues edited comment on ATLAS-1766 at 7/3/17 7:26 AM:


Thanks [~madhan.neethiraj] for commit, Thanks 
[~sarath.ku...@gmail.com],[~apoorvnaik],[~suma.shivaprasad] & 
[~madhan.neethiraj] for inputs & review. 

Patch commited on the following branch. 

* master :- 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0e7f8ea4
* 0.8-incubating :- 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/7ec95fe7



was (Author: nixonrodrigues):
Thanks [~madhan.neethiraj] for commit, Thanks 
[~sarath.ku...@gmail.com],[~apoorvnaik],[~suma.shivaprasad] & 
[~madhan.neethiraj] inputs & reviews 

Patch commited on the following branch. 

* master :- 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0e7f8ea4
* 0.8-incubating :- 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/7ec95fe7


> Atlas with Kafka SASL_SSL protocol
> --
>
> Key: ATLAS-1766
> URL: https://issues.apache.org/jira/browse/ATLAS-1766
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Sandeep Nemuri
>Assignee: Nixon Rodrigues
> Attachments: ATLAS-1766.1.patch, ATLAS-1766-9.patch
>
>
> Creating this jira to add support to Kafka SASL_SSL protocol for Atlas.
> Atlas is currently using old consumer api which doesn't support SSL 
> protocols. To support SSL protocol the consumer code should be re-written in 
> new consumer api.



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

[jira] [Resolved] (ATLAS-1766) Atlas with Kafka SASL_SSL protocol

2017-07-03 Thread Nixon Rodrigues (JIRA)


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

Nixon Rodrigues resolved ATLAS-1766.

Resolution: Fixed

Thanks [~madhan.neethiraj] for commit, Thanks 
[~sarath.ku...@gmail.com],[~apoorvnaik],[~suma.shivaprasad] & 
[~madhan.neethiraj] inputs & reviews 

Patch commited on the following branch. 

* master :- 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0e7f8ea4
* 0.8-incubating :- 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/7ec95fe7


> Atlas with Kafka SASL_SSL protocol
> --
>
> Key: ATLAS-1766
> URL: https://issues.apache.org/jira/browse/ATLAS-1766
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Sandeep Nemuri
>Assignee: Nixon Rodrigues
> Attachments: ATLAS-1766.1.patch, ATLAS-1766-9.patch
>
>
> Creating this jira to add support to Kafka SASL_SSL protocol for Atlas.
> Atlas is currently using old consumer api which doesn't support SSL 
> protocols. To support SSL protocol the consumer code should be re-written in 
> new consumer api.



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

43 matches

Mail list logo