date:20170707

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

2017-07-07 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-1912: fix for defects reported by Coverity scan

--
[...truncated 541.95 KB...]
127.0.0.1 - - [08/Jul/2017:05:16:32 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:32 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:32 +] "GET 
/api/atlas/v2/types/typedef/name/PII_TraitN2iSG14hU9 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:32 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:32 +] "POST 
/api/atlas/entities/496fa758-fe3f-41b6-9520-e83e4bef34df/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:32 +] "GET 
/api/atlas/entities/496fa758-fe3f-41b6-9520-e83e4bef34df/traitDefinitions/PII_TraitN2iSG14hU9
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:32 +] "GET 
/api/atlas/entities/496fa758-fe3f-41b6-9520-e83e4bef34df/traitDefinitions 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:32 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "GET 
/api/atlas/entities/9a92379e-afb2-4813-8b87-25dd7281398e/traits HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST 
/api/atlas/entities/f64afb7a-e7a9-4ddc-800d-36665d6f7f5e HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "GET 
/api/atlas/entities/f64afb7a-e7a9-4ddc-800d-36665d6f7f5e HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST 
/api/atlas/entities/qualifiedName?type=hive_table=qualifiedName=tablexvi9MapIRd
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "GET 
/api/atlas/entities/f64afb7a-e7a9-4ddc-800d-36665d6f7f5e HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "GET 
/api/atlas/entities/cadfd1b7-c627-49d4-8b6e-366fd9ad2840/audit?count=10 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "GET 
/api/atlas/v2/types/typedef/name/YCPGQMMKeN HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "GET 
/api/atlas/entities/7586fbad-87ed-4bdf-af4e-15d2ee5696a8 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "GET 
/api/atlas/v2/entity/guid/748109be-e9cc-408b-afb9-b593f694ff2f HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST 
/api/atlas/v2/entity/guid/random/classifications HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:33 +] "POST /api/atlas/v2/entity/bulk/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:34 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:34 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:34 +] "DELETE 
/api/atlas/v2/entity/bulk/?guid=7918dd92-1dca-47f1-878a-84ce395eb315=904b5491-ff16-473d-b351-d2ddb77eec23
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:34 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:34 +] "DELETE 
/api/atlas/v2/entity/uniqueAttribute/type/hive_db_v2?attr:name=dbHo6cwIbjkb%EC%86%A8%E1%B0%8C%EE%8C%8D%EC%AF%9A%ED%8C%97%EA%99%BA%E1%B4%AC%E9%BA%B2%E2%A6%BE%E2%92%A0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:05:16:34 +] "DELETE

Re: Assign as contributor

2017-07-07 Thread Madhan Neethiraj

Chandana,

Done. Welcome to Apache Atlas community.

Madhan

On 7/7/17, 6:18 PM, "Chandana Mirashi"  wrote:

Hi,
I would like to contribute to Atlas. Can someone please add me so that 
I can assign myself JIRA to work on?
 
Regards,
Chandana Mirashi

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

2017-07-07 Thread Apache Jenkins Server

See 


Changes:

[madhan] updated documentation for import API

--
[...truncated 540.92 KB...]
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/ETL HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/Dimension HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/Metric HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/hive_db_v1 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/hive_column_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/hive_table_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/hive_process_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/Fact HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/ETL HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/Dimension HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/v2/types/typedef/name/Metric HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:44 +] "GET 
/api/atlas/lineage/hive/table/sales_fact_monthly_mvi88c2yr3pV/inputs/graph 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:46 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factCtFurVzOgm
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:46 +] "GET 
/api/atlas/lineage/0daf3353-94aa-40be-a831-6a3ea77fdbdb/outputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:47 +] "GET 
/api/atlas/lineage/hive/table/blah/schema HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:47 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvi88c2yr3pV
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:47 +] "GET 
/api/atlas/lineage/d251d82e-4687-490c-9bd0-90ea94a85c14/inputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:48 +] "GET 
/api/atlas/lineage/hive/table/sales_factCtFurVzOgm/outputs/graph HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:51 +] "GET 
/api/atlas/lineage/hive/table/SalesP3IC0Q1W0z/schema HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:51 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factCtFurVzOgm
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:51 +] "GET 
/api/atlas/lineage/0daf3353-94aa-40be-a831-6a3ea77fdbdb/schema HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:51 +] "GET 
/api/atlas/lineage/hive/table/sales_factCtFurVzOgm/schema HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:53 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 409 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:53 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:54 +] "GET /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:54 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:54 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [08/Jul/2017:00:15:54 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"

Review Request 60722: Fix for: Export of hive_table with fetchType "connected" fails

2017-07-07 Thread Ashutosh Mestry


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

Review request for atlas and Madhan Neethiraj.


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


Repository: atlas


Description
---

**Analysis**
The connected _fetchType_ in Export API had a potential for attempting to save 
same entity twice.

**Fix**
The entities saved to the _ZipSink_ are now maintained in a separate set. 
Before attempting to save to _ZipSink_ existence check is performed. If passed, 
save is prevented, else entity is saved to _ZipSink_.


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java 
3538cfd7 


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


Testing
---

**Unit tests**
- Executed existing unit tests.

**Functional tests**
- Executed standard set of tests.


Thanks,

Ashutosh Mestry

[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-07 Thread Ashutosh Mestry (JIRA)


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

Ashutosh Mestry updated ATLAS-1919:
---
Attachment: ATLAS-1919.patch

> 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
>
> Attachments: ATLAS-1919.patch
>
>
> 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 
>

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

2017-07-07 Thread David Radley (JIRA)


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

David Radley commented on ATLAS-1698:
-

I have put up a new version of the patch that includes many java files to 
generate a strongly typed rest 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: apidocs-2.zip, Atlas Glossary OMAS API proposal v1.0 
> .pdf, Atlas Glossary OMAS API proposal v1.1.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-07 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: apidocs.zip)

> 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: apidocs-2.zip, Atlas Glossary OMAS API proposal v1.0 
> .pdf, Atlas Glossary OMAS API proposal v1.1.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-07 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: apidocs-2.zip

> 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: apidocs-2.zip, Atlas Glossary OMAS API proposal v1.0 
> .pdf, Atlas Glossary OMAS API proposal v1.1.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)

Re: Review Request 60681: ATLAS-1698 Glossary OMAS API - early Swagger draft

2017-07-07 Thread David Radley


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

(Updated July 7, 2017, 10:18 p.m.)


Review request for atlas and Madhan Neethiraj.


Changes
---

adding strong types


Repository: atlas


Description (updated)
---

This is stub code to generate some Glossary OMAS REST interfaces. 

It does not include : 
- search
- finding all assets
- lineage

This patch is not to be committed at this time- it is for review purposes only.


Diffs (updated)
-

  glossaryomas/pom.xml PRE-CREATION 
  glossaryomas/src/main/java/org/apache/atlas/model/GlossaryOMASCategory.java 
PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/GlossaryOMASGraphEdgeDirection.java
 PRE-CREATION 
  glossaryomas/src/main/java/org/apache/atlas/model/GlossaryOMASPermission.java 
PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/AtlasGlossaryGraph.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/AtlasGlossaryGraphEdge.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/AtlasGlossaryGraphNode.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/AtlasGlossaryTreeElement.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/category/AtlasGlossaryCategory.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/glossary/Anchor.java 
PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/glossary/AtlasGlossary.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/AtlasGlossaryTerm.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/ExternalGlossaryLinks.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/ListTermCategorizations.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/Relatable.java 
PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/Antonym.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/ISA.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/PreferedTerm.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/RelatedTerm.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/RelatedTerms.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/ReplacementTerm.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/Synonym.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/Translation.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/ValidValue.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/SemanticAssignment/SemanticAssignment.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/contexts/Context.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/SpineObjects.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/TermHASARelationship.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/TermISATYPEOFRelationship.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/TermSpineRelationship.java
 PRE-CREATION 
  
glossaryomas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/TermTYPEDBYRelationship.java
 PRE-CREATION 
  omas/pom.xml PRE-CREATION 
  omas/src/main/java/org/apache/atlas/exception/AtlasOMASBaseException.java 
PRE-CREATION 
  omas/src/main/java/org/apache/atlas/exception/AtlasOMASErrorCode.java 
PRE-CREATION 
  omas/src/main/java/org/apache/atlas/model/EmbeddedMedia.java PRE-CREATION 
  omas/src/main/java/org/apache/atlas/model/PList.java PRE-CREATION 
  omas/src/main/java/org/apache/atlas/model/SearchFilter.java PRE-CREATION 
  omas/src/main/java/org/apache/atlas/model/instance/AtlasOMASEntity.java 
PRE-CREATION 
  pom.xml ebc07e21d2d721910f1aae7069305845284a8c21 
  webapp/pom.xml 465d2a5498376a2517dc1b01f970734c452c504d 
  webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java 
0f6eeb11d90f6495498e87d31b4ff5bb4cfea1e8 
  webapp/src/main/java/org/apache/atlas/web/rest/GlossaryOMASREST.java 
PRE-CREATION 


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

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


Testing
---

generated the swagger by running mvn clean install -DskipTests 
-DskipEnunciate=false. 
the output is

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

2017-07-07 Thread Kalyani Kashikar (JIRA)


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

Kalyani Kashikar updated ATLAS-1938:

Attachment: ATLAS-1938.1.patch

> UI - Search using entity and trait attributes - Refresh Button fires the 
> search query (Basic/DSL) again.
> 
>
> Key: ATLAS-1938
> URL: https://issues.apache.org/jira/browse/ATLAS-1938
> Project: Atlas
>  Issue Type: Bug
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1938.1.patch, ATLAS-1938.patch
>
>
> On clicking the Refresh Button to refresh types (data-id : refreshBtn) , 
> makes the following 2 queries :
> # /api/atlas/v2/types/typedefs/headers
> # 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
> http://localhost:21000/api/atlas/v2/search?
> which throws 500 Internal server error.



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

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

2017-07-07 Thread Kalyani Kashikar (JIRA)


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

Kalyani Kashikar updated ATLAS-1938:

Attachment: ATLAS-1938.patch

> UI - Search using entity and trait attributes - Refresh Button fires the 
> search query (Basic/DSL) again.
> 
>
> Key: ATLAS-1938
> URL: https://issues.apache.org/jira/browse/ATLAS-1938
> Project: Atlas
>  Issue Type: Bug
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1938.patch
>
>
> On clicking the Refresh Button to refresh types (data-id : refreshBtn) , 
> makes the following 2 queries :
> # /api/atlas/v2/types/typedefs/headers
> # 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
> http://localhost:21000/api/atlas/v2/search?
> which throws 500 Internal server error.



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

[jira] [Updated] (ATLAS-1774) Create the OMRS Connector for IBM's Information Governance Catalog (IGC)

2017-07-07 Thread Mandy Chessell (JIRA)


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

Mandy Chessell updated ATLAS-1774:
--
Summary: Create the OMRS Connector for IBM's Information Governance Catalog 
(IGC)  (was: Create the OMRS Connector for IBM's Information Governance Catalog)

> Create the OMRS Connector for IBM's Information Governance Catalog (IGC)
> 
>
> Key: ATLAS-1774
> URL: https://issues.apache.org/jira/browse/ATLAS-1774
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>
> This JIRA provides a connector for IBM’s Information Governance Catalog that 
> implements the OMRS Connector API defined in JIRA ATLAS-1773.



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

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

2017-07-07 Thread Kalyani Kashikar (JIRA)

Kalyani Kashikar created ATLAS-1938:
---

 Summary: UI - Search using entity and trait attributes - Refresh 
Button fires the search query (Basic/DSL) again.
 Key: ATLAS-1938
 URL: https://issues.apache.org/jira/browse/ATLAS-1938
 Project: Atlas
  Issue Type: Bug
Reporter: Kalyani Kashikar
Assignee: Kalyani Kashikar


On clicking the Refresh Button to refresh types (data-id : refreshBtn) , makes 
the following 2 queries :
# /api/atlas/v2/types/typedefs/headers
# 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
http://localhost:21000/api/atlas/v2/search?
which throws 500 Internal server error.



--
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-07 Thread Nixon Rodrigues (JIRA)


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

Nixon Rodrigues reassigned ATLAS-1906:
--

Assignee: Nixon Rodrigues  (was: 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: Nixon Rodrigues
> Attachments: 
> 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, 
> ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.3.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)

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

Re: Assign as contributor

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

Review Request 60722: Fix for: Export of hive_table with fetchType "connected" fails

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

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

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

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

Re: Review Request 60681: ATLAS-1698 Glossary OMAS API - early Swagger draft

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

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

[jira] [Updated] (ATLAS-1774) Create the OMRS Connector for IBM's Information Governance Catalog (IGC)

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

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

14 matches

Site Navigation

Mail list logo

Footer information