[jira] [Updated] (ATLAS-1924) Search using entity and trait attributes - Filtering integral and float data types with != (NOT EQUALS) on negative number throws exception

2017-07-04 Thread Sharmadha Sainath (JIRA)

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

Sharmadha Sainath updated ATLAS-1924:
-
Description: 
Selected type = hive_table and applied filter 

{code}
Retention != -1
{code} 

The above throws 500 internal server error. Attached the application logs .

Other filters like <,>,>=,<=,= on negative numbers work as expected.

This happens for all integral and floating point data types

POST request body :
{code}
{  
   "entityFilters":{  
  "condition":"AND",
  "criterion":[  
 {  
"attributeName":"retention",
"operator":"!=",
"attributeValue":"-1"
 }
  ]
   },
   "tagFilters":null,
   "query":null,
   "excludeDeletedEntities":true,
   "limit":25,
   "typeName":"hive_table",
   "classification":null
}
{code}

  was:
Selected type = hive_table and applied filter 

{code}
Retention != -1
{code}

other filters like <,>,>=,<=,= on negative numbers work as expected.

This happens for all integral and floating point data types . 

The above threw 500 internal server error. Attached the application logs .

POST request body :
{code}
{  
   "entityFilters":{  
  "condition":"AND",
  "criterion":[  
 {  
"attributeName":"retention",
"operator":"!=",
"attributeValue":"-1"
 }
  ]
   },
   "tagFilters":null,
   "query":null,
   "excludeDeletedEntities":true,
   "limit":25,
   "typeName":"hive_table",
   "classification":null
}
{code}


> Search using entity and trait attributes - Filtering integral and float data 
> types with != (NOT EQUALS) on negative number throws exception
> ---
>
> Key: ATLAS-1924
> URL: https://issues.apache.org/jira/browse/ATLAS-1924
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Fix For: 0.9-incubating
>
> Attachments: NotEqualsSearchWithNegative.txt
>
>
> Selected type = hive_table and applied filter 
> {code}
> Retention != -1
> {code} 
> The above throws 500 internal server error. Attached the application logs .
> Other filters like <,>,>=,<=,= on negative numbers work as expected.
> This happens for all integral and floating point data types
> POST request body :
> {code}
> {  
>"entityFilters":{  
>   "condition":"AND",
>   "criterion":[  
>  {  
> "attributeName":"retention",
> "operator":"!=",
> "attributeValue":"-1"
>  }
>   ]
>},
>"tagFilters":null,
>"query":null,
>"excludeDeletedEntities":true,
>"limit":25,
>"typeName":"hive_table",
>"classification":null
> }
> {code}



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


[jira] [Commented] (ATLAS-1900) Test NotificationHookConsumerIT#testUpdateEntityPartial fails intermittently

2017-07-04 Thread Sneha Kanekar (JIRA)

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

Sneha Kanekar commented on ATLAS-1900:
--

Any update on this issue?

> Test NotificationHookConsumerIT#testUpdateEntityPartial fails intermittently
> 
>
> Key: ATLAS-1900
> URL: https://issues.apache.org/jira/browse/ATLAS-1900
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>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: application.log
>
>
> The integration test 
> org.apache.atlas.notification.NotificationHookConsumerIT.testUpdateEntityPartial
>  fails intermittently with Internal server error 500. This test fails on x86 
> and ppc64le platform. 
> {code:borderStyle=solid}
> testUpdateEntityPartial(org.apache.atlas.notification.NotificationHookConsumerIT)
>   Time elapsed: 0.646 sec  <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API 
> org.apache.atlas.AtlasBaseClient$APIInfo@3c2809c9 failed with status 500 
> (Internal Server Error) Response Body ({"error":"Could not execute operation 
> due to backend exception"})
> at 
> org.apache.atlas.notification.NotificationHookConsumerIT.testUpdateEntityPartial(NotificationHookConsumerIT.java:127)
> {code}
> The full error message from standard output is as follows:
> {code:borderStyle=solid}
> Jun 27, 2017 5:49:29 AM com.sun.jersey.spi.container.ContainerResponse 
> logException
> SEVERE: Mapped exception to response: 500 (Internal Server Error)
> javax.ws.rs.WebApplicationException
> at 
> org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:838)
> at 
> org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:764)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
> at 
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:76)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
> at 
> org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:157)
> at 
> 

[jira] [Updated] (ATLAS-1924) Search using entity and trait attributes - Filtering integral and float data types with != (NOT EQUALS) on negative number throws exception

2017-07-04 Thread Sharmadha Sainath (JIRA)

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

Sharmadha Sainath updated ATLAS-1924:
-
Description: 
Selected type = hive_table and applied filter 

{code}
Retention != -1
{code}

other filters like <,>,>=,<=,= on negative numbers work as expected.

This happens for all integral and floating point data types . 

The above threw 500 internal server error. Attached the application logs .

POST request body :
{code}
{  
   "entityFilters":{  
  "condition":"AND",
  "criterion":[  
 {  
"attributeName":"retention",
"operator":"!=",
"attributeValue":"-1"
 }
  ]
   },
   "tagFilters":null,
   "query":null,
   "excludeDeletedEntities":true,
   "limit":25,
   "typeName":"hive_table",
   "classification":null
}
{code}

  was:
Selected type = hive_table and applied filter 

{code}
Retention != -1
{code}

The above threw 500 internal server error. Attached the application logs .

POST request body :
{code}
{  
   "entityFilters":{  
  "condition":"AND",
  "criterion":[  
 {  
"attributeName":"retention",
"operator":"!=",
"attributeValue":"-1"
 }
  ]
   },
   "tagFilters":null,
   "query":null,
   "excludeDeletedEntities":true,
   "limit":25,
   "typeName":"hive_table",
   "classification":null
}
{code}


> Search using entity and trait attributes - Filtering integral and float data 
> types with != (NOT EQUALS) on negative number throws exception
> ---
>
> Key: ATLAS-1924
> URL: https://issues.apache.org/jira/browse/ATLAS-1924
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Fix For: 0.9-incubating
>
> Attachments: NotEqualsSearchWithNegative.txt
>
>
> Selected type = hive_table and applied filter 
> {code}
> Retention != -1
> {code}
> other filters like <,>,>=,<=,= on negative numbers work as expected.
> This happens for all integral and floating point data types . 
> The above threw 500 internal server error. Attached the application logs .
> POST request body :
> {code}
> {  
>"entityFilters":{  
>   "condition":"AND",
>   "criterion":[  
>  {  
> "attributeName":"retention",
> "operator":"!=",
> "attributeValue":"-1"
>  }
>   ]
>},
>"tagFilters":null,
>"query":null,
>"excludeDeletedEntities":true,
>"limit":25,
>"typeName":"hive_table",
>"classification":null
> }
> {code}



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


[jira] [Created] (ATLAS-1924) Search using entity and trait attributes - Filtering integral and float data types with != (NOT EQUALS) on negative number throws exception

2017-07-04 Thread Sharmadha Sainath (JIRA)
Sharmadha Sainath created ATLAS-1924:


 Summary: Search using entity and trait attributes - Filtering 
integral and float data types with != (NOT EQUALS) on negative number throws 
exception
 Key: ATLAS-1924
 URL: https://issues.apache.org/jira/browse/ATLAS-1924
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
 Fix For: 0.9-incubating
 Attachments: NotEqualsSearchWithNegative.txt

Selected type = hive_table and applied filter 

{code}
Retention != -1
{code}

The above threw 500 internal server error. Attached the application logs .

POST request body :
{code}
{  
   "entityFilters":{  
  "condition":"AND",
  "criterion":[  
 {  
"attributeName":"retention",
"operator":"!=",
"attributeValue":"-1"
 }
  ]
   },
   "tagFilters":null,
   "query":null,
   "excludeDeletedEntities":true,
   "limit":25,
   "typeName":"hive_table",
   "classification":null
}
{code}



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


[jira] [Created] (ATLAS-1923) Tag creation: hive_principal_type and file_action are shown in the drop down while adding attributes to a tag.

2017-07-04 Thread Ayub Pathan (JIRA)
Ayub Pathan created ATLAS-1923:
--

 Summary: Tag creation: hive_principal_type and file_action are 
shown in the drop down while adding attributes to a tag.
 Key: ATLAS-1923
 URL: https://issues.apache.org/jira/browse/ATLAS-1923
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Ayub Pathan
 Fix For: 0.9-incubating
 Attachments: Screen Shot 2017-07-05 at 10.38.50 AM.png

Tag creation: hive_principal_type and file_action are shown in the drop down 
while adding attributes to a tag.

Attaching screenshot for reference.



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


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

2017-07-04 Thread Apoorv Naik


> On July 4, 2017, 10:39 a.m., David Radley wrote:
> > client/src/main/java/org/apache/atlas/AtlasBaseClient.java
> > Lines 235 (patched)
> > 
> >
> > I wonder whether the fix to enable Knox integration should be for Atlas 
> > to add the generic ability to set Headers in the Atlas Client. 
> > 
> > Instead I suggest:
> > As we handle userid and passwords for the client, I suggest that we do 
> > not expose setHeaders ( a low level http orientated method) instead we 
> > expose a method like setKnoxSSOCookie; I think this would give the atlas 
> > client developer a clue as to why they might want to use this method; also 
> > it would not expose other low level http control functionality as a side 
> > effect.

Thanks David, that's good feedback. I think I've duplicated the effort that 
Nixon was already working on. His review does have the ability to add cookies 
to the request.


- Apoorv


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


On July 3, 2017, 5:16 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60603/
> ---
> 
> (Updated July 3, 2017, 5:16 p.m.)
> 
> 
> 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] [Created] (ATLAS-1922) Search using entity and trait attributes - On applying contains/ends with/begins with filter on a string with '/' (forward slash) in it, search results are empty.

2017-07-04 Thread Sharmadha Sainath (JIRA)
Sharmadha Sainath created ATLAS-1922:


 Summary: Search using entity and trait attributes - On applying 
contains/ends with/begins with filter on a string with '/' (forward slash) in 
it, search results are empty.
 Key: ATLAS-1922
 URL: https://issues.apache.org/jira/browse/ATLAS-1922
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
 Fix For: 0.9-incubating


Created a hive_table employee. The hive_storagedesc for the table had the 
location value "hdfs://localhost:8020/apps/hive/warehouse/employee" . 

Selected type as hive_storagedesc , and applied filter
{code}
 Location = hdfs\://localhost:\8020/apps/hive/warehouse/employee
{code}
which listed the storage descriptor of employee table

Selected type as hive_storagedesc and applied "contains" filter
{code}
Location contains /apps/hive/warehouse/employee
{code}

The above query didn't fetch any result .The same applies for ends with , 
begins with operators.

 Hence "/" works with "=" operator but not with others.

Application logs for the search with contains operator:
{code}
Converted query string with 3 replacements: [v."__typeName": (hive_storagedesc) 
AND ( v."hive_storagedesc.location": (*/apps/hive/warehouse/employee*) ) AND 
v."__state":ACTIVE] => [iyt_t: (hive_storagedesc) AND ( 9hc5_t: 
(*/apps/hive/warehouse/employee*) ) AND b2d_t:ACTIVE] (IndexSerializer:648)
{code}



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


[jira] [Updated] (ATLAS-1922) Search using entity and trait attributes - On applying contains/ends with/begins with filter on a string with '/' (forward slash) in it, search results are empty.

2017-07-04 Thread Sharmadha Sainath (JIRA)

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

Sharmadha Sainath updated ATLAS-1922:
-
Description: 
Created a hive_table employee. The hive_storagedesc for the table had the 
location value "hdfs://localhost:8020/apps/hive/warehouse/employee" . 

Selected type as hive_storagedesc , and applied filter
{code}
 Location = hdfs\://localhost\:8020/apps/hive/warehouse/employee
{code}
which listed the storage descriptor of employee table

Selected type as hive_storagedesc and applied "contains" filter
{code}
Location contains /apps/hive/warehouse/employee
{code}

The above query didn't fetch any result .The same applies for ends with , 
begins with operators.

 Hence "/" works with "=" operator but not with others.

Application logs for the search with contains operator:
{code}
Converted query string with 3 replacements: [v."__typeName": (hive_storagedesc) 
AND ( v."hive_storagedesc.location": (*/apps/hive/warehouse/employee*) ) AND 
v."__state":ACTIVE] => [iyt_t: (hive_storagedesc) AND ( 9hc5_t: 
(*/apps/hive/warehouse/employee*) ) AND b2d_t:ACTIVE] (IndexSerializer:648)
{code}

  was:
Created a hive_table employee. The hive_storagedesc for the table had the 
location value "hdfs://localhost:8020/apps/hive/warehouse/employee" . 

Selected type as hive_storagedesc , and applied filter
{code}
 Location = hdfs\://localhost:\8020/apps/hive/warehouse/employee
{code}
which listed the storage descriptor of employee table

Selected type as hive_storagedesc and applied "contains" filter
{code}
Location contains /apps/hive/warehouse/employee
{code}

The above query didn't fetch any result .The same applies for ends with , 
begins with operators.

 Hence "/" works with "=" operator but not with others.

Application logs for the search with contains operator:
{code}
Converted query string with 3 replacements: [v."__typeName": (hive_storagedesc) 
AND ( v."hive_storagedesc.location": (*/apps/hive/warehouse/employee*) ) AND 
v."__state":ACTIVE] => [iyt_t: (hive_storagedesc) AND ( 9hc5_t: 
(*/apps/hive/warehouse/employee*) ) AND b2d_t:ACTIVE] (IndexSerializer:648)
{code}


> Search using entity and trait attributes - On applying contains/ends 
> with/begins with filter on a string with '/' (forward slash) in it, search 
> results are empty.
> --
>
> Key: ATLAS-1922
> URL: https://issues.apache.org/jira/browse/ATLAS-1922
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Fix For: 0.9-incubating
>
>
> Created a hive_table employee. The hive_storagedesc for the table had the 
> location value "hdfs://localhost:8020/apps/hive/warehouse/employee" . 
> Selected type as hive_storagedesc , and applied filter
> {code}
>  Location = hdfs\://localhost\:8020/apps/hive/warehouse/employee
> {code}
> which listed the storage descriptor of employee table
> Selected type as hive_storagedesc and applied "contains" filter
> {code}
> Location contains /apps/hive/warehouse/employee
> {code}
> The above query didn't fetch any result .The same applies for ends with , 
> begins with operators.
>  Hence "/" works with "=" operator but not with others.
> Application logs for the search with contains operator:
> {code}
> Converted query string with 3 replacements: [v."__typeName": 
> (hive_storagedesc) AND ( v."hive_storagedesc.location": 
> (*/apps/hive/warehouse/employee*) ) AND v."__state":ACTIVE] => [iyt_t: 
> (hive_storagedesc) AND ( 9hc5_t: (*/apps/hive/warehouse/employee*) ) AND 
> b2d_t:ACTIVE] (IndexSerializer:648)
> {code}



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


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

2017-07-04 Thread Apache Jenkins Server
See 


Changes:

[kalyani.kashikar] ATLAS-1897 : UI - Render HTML element based on attribute 
data-type while

--
[...truncated 542.11 KB...]
127.0.0.1 - - [04/Jul/2017:14:46:03 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db_v2+where+name%3D'dbXdoTOj83RS'=10=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "PUT /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "GET 
/api/atlas/v2/entity/guid/7b500c1a-a1ff-40ed-b035-87d4e739ae20 HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/hive_db_v2?attr:name=dbXdoTOj83RS 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "GET /api/atlas/v2/entity/guid/blah 
HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "GET 
/api/atlas/entities/8f4e3288-2bef-44ca-9922-f95a0f11bda8/audit?count=10 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:04 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:05 +] "GET 
/api/atlas/v2/types/typedef/name/dKuTYSsGhX HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:05 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:05 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:05 +] "GET 
/api/atlas/v2/entity/guid/90d8a7dd-0400-4a95-8066-8ff82403a1e0 HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:05 +] "GET 
/api/atlas/discovery/search/dsl?query=from+hive_db_v1+name%3D%22dbsj00rgW7NZ%22 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:06 +] "GET 
/api/atlas/discovery/search/dsl?query=from+blah HTTP/1.1" 400 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:06 +] "GET 
/api/atlas/discovery/search?query=* HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:06 +] "GET 
/api/atlas/discovery/search?query=from+hive_db_v1+name%3D%22dbsj00rgW7NZ%22 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:06 +] "GET 
/api/atlas/discovery/search/gremlin?query=g.V.has('type',+'hive_table_v1').toList()
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 409 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "GET 
/api/atlas/v2/types/enumdef/name/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "GET 
/api/atlas/v2/types/enumdef/guid/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "GET 
/api/atlas/v2/types/structdef/name/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "GET 
/api/atlas/v2/types/structdef/guid/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "GET 
/api/atlas/v2/types/classificationdef/name/blah HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "GET 
/api/atlas/v2/types/classificationdef/guid/blah HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "GET 
/api/atlas/v2/types/entitydef/name/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "GET 
/api/atlas/v2/types/entitydef/guid/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:07 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:08 +] "GET 
/api/atlas/v2/types/typedefs/?supertype=AhmGvE9IBgC=CLASS HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:08 +] "GET 
/api/atlas/v2/types/typedefs/?notsupertype=BKFTQn7ydb0=AhmGvE9IBgC=CLASS
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jul/2017:14:46:08 +] "POST 

[jira] [Commented] (ATLAS-1897) UI - Render HTML element based on attribute data-type while assigning Tag to entity.

2017-07-04 Thread Kalyani Kashikar (JIRA)

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

Kalyani Kashikar commented on ATLAS-1897:
-

Thank [~nixonrodrigues] for review.
committed to master - 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/c4fd42b8

> UI - Render HTML element based on attribute data-type while assigning Tag to 
> entity.
> 
>
> Key: ATLAS-1897
> URL: https://issues.apache.org/jira/browse/ATLAS-1897
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1897.patch
>
>
> While assigning tag to entity, It allows inputs based on attribute data-type



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


[jira] [Created] (ATLAS-1921) UI : Search using entity and trait attributes : UI doesn't perform range check and allows providing out of bounds values for integral and float data types.

2017-07-04 Thread Sharmadha Sainath (JIRA)
Sharmadha Sainath created ATLAS-1921:


 Summary: UI : Search using entity and trait attributes : UI 
doesn't perform range check and allows providing out of bounds values for 
integral and float data types.
 Key: ATLAS-1921
 URL: https://issues.apache.org/jira/browse/ATLAS-1921
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Minor


When applying filter for integral/float data types , Number picker  (the up and 
down button) doesn't do range check according to the data type and lets user go 
up and down and set any value.Hence when filter is applied and search is made , 
500 Internal server error is thrown.

Ex : Maximum value for an integer data type is 2 ^31^ -1 
Number picker for integer allows user go to  2147483648 and throws Invalid 
number exception when searched.



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


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

2017-07-04 Thread David Radley

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




client/src/main/java/org/apache/atlas/AtlasBaseClient.java
Lines 146 (patched)


I think displaying or logging the Excpetion message would be useful here.



client/src/main/java/org/apache/atlas/AtlasBaseClient.java
Lines 234 (patched)


Please can you junit this in AtlasClientTest.



client/src/main/java/org/apache/atlas/AtlasBaseClient.java
Lines 235 (patched)


I wonder whether the fix to enable Knox integration should be for Atlas to 
add the generic ability to set Headers in the Atlas Client. 

Instead I suggest:
As we handle userid and passwords for the client, I suggest that we do not 
expose setHeaders ( a low level http orientated method) instead we expose a 
method like setKnoxSSOCookie; I think this would give the atlas client 
developer a clue as to why they might want to use this method; also it would 
not expose other low level http control functionality as a side effect.


- David Radley


On July 3, 2017, 5:16 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60603/
> ---
> 
> (Updated July 3, 2017, 5:16 p.m.)
> 
> 
> 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-04 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.1.patch

This patch ATLAS-1906.1.patch  includes setHadoopJWTCookie method in 
AtlasBaseClient, this method can be used to update the fresh hadoopJWT cookie 
when old cookie is expired instead creating the new object of AtlasClient.

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


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

2017-07-04 Thread Nixon Rodrigues

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

(Updated July 4, 2017, 10:34 a.m.)


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


Changes
---

This patch includes setHadoopJWTCookie method in AtlasBaseClient, this method 
can be used to update the fresh hadoopJWT cookie when old cookie is expired 
instead creating the new object of AtlasClient.

Tested quickStart script with this AtlasClient api methods.


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

  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/2/

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


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] [Created] (ATLAS-1920) UI : Search using entity and trait attributes - Operators for enum and boolean data type filters.

2017-07-04 Thread Sharmadha Sainath (JIRA)
Sharmadha Sainath created ATLAS-1920:


 Summary: UI : Search using entity and trait attributes - Operators 
for enum and boolean data type filters.
 Key: ATLAS-1920
 URL: https://issues.apache.org/jira/browse/ATLAS-1920
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Minor
 Fix For: 0.9-incubating


Operators for attribute filters of enum , boolean data type have similar 
operators that of numerical data type (<,>,<=,>=,!=,=).

For such data types , EQUALS and NOT EQUALS operators would be sufficient.



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


[jira] [Updated] (ATLAS-1919) Export of hive_table with fetchType "connected" fails with duplicate entry. Seems like, same edge(asset) is traversed twice.

2017-07-04 Thread Ayub Pathan (JIRA)

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

Ayub Pathan updated ATLAS-1919:
---
Description: 
Export of hive_table with fetchType "connected" fails with duplicate entry. 
Seems like, same edge(asset) is traversed twice. Possibly a loop condition.

Export request payload
{noformat}
{
"itemsToExport": [
{
"typeName": "hive_table",
"uniqueAttributes": {
"qualifiedName": "any_random_table@cluster"
}
}
],
"options": {
"fetchType" : "connected"
}
}
{noformat}

stacktrace
{noformat}
2017-07-04 08:44:19,159 INFO  - [pool-2-thread-9 - 
8bc8d958-e650-4351-acf0-24c28d15627a:] ~ export(item=AtlasObjectId{guid='null', 
typeName='hive_table', uniqueAttributes={qualifiedName:db1.table1@cl1}}; 
matchType=null, fetchType=CONNECTED): found 1 entities (ExportService:280)
2017-07-04 08:44:19,794 ERROR - [pool-2-thread-9 - 
8bc8d958-e650-4351-acf0-24c28d15627a:] ~ Fetching entity failed for: 
AtlasObjectId{guid='null', typeName='hive_table', 
uniqueAttributes={qualifiedName:db1.table1@cl1}} (ExportService:207)
org.apache.atlas.exception.AtlasBaseException: Error writing file 
75a90231-3eca-4ba7-9e21-93e7ec2b0df2.
at org.apache.atlas.repository.impexp.ZipSink.saveToZip(ZipSink.java:91)
at org.apache.atlas.repository.impexp.ZipSink.add(ZipSink.java:50)
at 
org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:433)
at 
org.apache.atlas.repository.impexp.ExportService.processEntity(ExportService.java:297)
at 
org.apache.atlas.repository.impexp.ExportService.processObjectId(ExportService.java:198)
at 
org.apache.atlas.repository.impexp.ExportService.processItems(ExportService.java:162)
at 
org.apache.atlas.repository.impexp.ExportService.run(ExportService.java:95)
at 
org.apache.atlas.web.resources.AdminResource.export(AdminResource.java:325)
at sun.reflect.GeneratedMethodAccessor238.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)
at 
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)
at 
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)
at 
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
at 
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:78)
at 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
at 
org.apache.atlas.web.filters.StaleTransactionCleanupFilter.doFilter(StaleTransactionCleanupFilter.java:56)
at 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
at 

[jira] [Created] (ATLAS-1919) Export of hive_table with fetchType "connected" fails with duplicate entry. Seems like, same edge(asset) is traversed twice.

2017-07-04 Thread Ayub Pathan (JIRA)
Ayub Pathan created ATLAS-1919:
--

 Summary: Export of hive_table with fetchType "connected" fails 
with duplicate entry. Seems like, same edge(asset) is traversed twice.
 Key: ATLAS-1919
 URL: https://issues.apache.org/jira/browse/ATLAS-1919
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Ayub Pathan
Priority: Critical
 Fix For: 0.9-incubating


Export of hive_table with fetchType "connected" fails with duplicate entry. 
Seems like, same edge(asset) is traversed twice. Possibly a loop condition.

Export request payload
{noformat}
{
"itemsToExport": [
{
"typeName": "hive_table",
"uniqueAttributes": {
"qualifiedName": "any_random_table@cluster"
}
}
],
"options": {
"fetchType" : "connected"
}
}
{noformat}

stacktrace
{noformat}
2017-07-04 08:44:19,159 INFO  - [pool-2-thread-9 - 
8bc8d958-e650-4351-acf0-24c28d15627a:] ~ export(item=AtlasObjectId{guid='null', 
typeName='hive_table', uniqueAttributes={qualifiedName:db1.table1@cl1}}; 
matchType=null, fetchType=CONNECTED): found 1 entities (ExportService:280)
2017-07-04 08:44:19,794 ERROR - [pool-2-thread-9 - 
8bc8d958-e650-4351-acf0-24c28d15627a:] ~ Fetching entity failed for: 
AtlasObjectId{guid='null', typeName='hive_table', 
uniqueAttributes={qualifiedName:db1.table1@cl1}} (ExportService:207)
org.apache.atlas.exception.AtlasBaseException: Error writing file 
75a90231-3eca-4ba7-9e21-93e7ec2b0df2.
at org.apache.atlas.repository.impexp.ZipSink.saveToZip(ZipSink.java:91)
at org.apache.atlas.repository.impexp.ZipSink.add(ZipSink.java:50)
at 
org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:433)
at 
org.apache.atlas.repository.impexp.ExportService.processEntity(ExportService.java:297)
at 
org.apache.atlas.repository.impexp.ExportService.processObjectId(ExportService.java:198)
at 
org.apache.atlas.repository.impexp.ExportService.processItems(ExportService.java:162)
at 
org.apache.atlas.repository.impexp.ExportService.run(ExportService.java:95)
at 
org.apache.atlas.web.resources.AdminResource.export(AdminResource.java:325)
at sun.reflect.GeneratedMethodAccessor238.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)
at 
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)
at 
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)
at 
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
at 
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:78)
at 

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

2017-07-04 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1698:

Attachment: Atlas Glossary OMAS API proposal v1.0 .pdf

Back ground to the OMAS Glossary API

> 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
> Attachments: Atlas Glossary OMAS API proposal v1.0 .pdf
>
>
> 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] [Updated] (ATLAS-1698) Create Glossary OMAS API

2017-07-04 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1698:

Attachment: (was: Atlas Glossary OMAS API proposal v1.0 (Autosaved).pdf)

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