date:20171019

Build failed in Jenkins: Atlas-master-UnitTests #138

2017-10-19 Thread Apache Jenkins Server

See 


Changes:

[apoorvnaik] ATLAS-2218: Fix Model loading failure in ITs

--
[...truncated 493.31 KB...]
at 
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
at 
com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:253)
at 
com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:153)
at 
com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:105)
at com.sun.jersey.api.client.Client.handle(Client.java:652)
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:682)
at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74)
at 
com.sun.jersey.api.client.WebResource$Builder.method(WebResource.java:634)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:334)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:311)
at org.apache.atlas.AtlasBaseClient.callAPI(AtlasBaseClient.java:227)
at 
org.apache.atlas.AtlasClient.callAPIWithQueryParams(AtlasClient.java:962)
at org.apache.atlas.AtlasClient.listTypes(AtlasClient.java:344)
at org.apache.atlas.web.security.SSLTest.testService(SSLTest.java:147)

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.security.FileAuthenticationTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.869 sec - in 
org.apache.atlas.web.security.FileAuthenticationTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.security.UserDaoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.665 sec - in 
org.apache.atlas.web.security.UserDaoTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.resources.AdminExportTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.343 sec - in 
org.apache.atlas.web.resources.AdminExportTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.resources.EntityResourceTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.742 sec - in 
org.apache.atlas.web.resources.EntityResourceTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.resources.AdminResourceTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.349 sec - in 
org.apache.atlas.web.resources.AdminResourceTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$6
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.338 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$6
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$4
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.38 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$4
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$5
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.379 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$5
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntitiesREST
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.156 sec - in 
org.apache.atlas.web.adapters.TestEntitiesREST
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$1
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.359 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$1
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.748 sec - in 
org.apache.atlas.web.adapters.TestEntityREST
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$2
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.334 sec - in

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

2017-10-19 Thread Apache Jenkins Server

See 


Changes:

[apoorvnaik] ATLAS-2218: Fix Model loading failure in ITs

--
[...truncated 508.84 KB...]
127.0.0.1 - - [19/Oct/2017:20:00:50 +] "POST /api/atlas/entities HTTP/1.1" 
201 1101 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:51 +] "POST /api/atlas/entities HTTP/1.1" 
201 876 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:51 +] "POST /api/atlas/entities HTTP/1.1" 
201 1199 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:51 +] "POST /api/atlas/entities HTTP/1.1" 
201 1633 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:51 +] "POST /api/atlas/entities HTTP/1.1" 
201 1199 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:51 +] "POST /api/atlas/entities HTTP/1.1" 
201 1429 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:51 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvfQ4Awn6994
 HTTP/1.1" 200 4061 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:51 +] "GET 
/api/atlas/v2/lineage/d75b01d6-4ee5-4474-b60a-026b0ac9ba5f?depth=5=BOTH
 HTTP/1.1" 200 2878 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:53 +] "GET 
/api/atlas/lineage/hive/table/blah/schema HTTP/1.1" 404 51 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:53 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factV3RxPJxvcF
 HTTP/1.1" 200 4370 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:53 +] "GET 
/api/atlas/lineage/d99848b9-3c1f-4f71-b7df-03bcb7ad2f27/schema HTTP/1.1" 200 
2467 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:54 +] "GET 
/api/atlas/lineage/hive/table/sales_fact_monthly_mvyjREGIrSGL/inputs/graph 
HTTP/1.1" 200 2522 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:56 +] "GET 
/api/atlas/lineage/hive/table/SalesVyprQZvH2w/schema HTTP/1.1" 404 62 "-" 
"Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:56 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_facteyikjGhUhZ
 HTTP/1.1" 200 4004 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:56 +] "GET 
/api/atlas/v2/lineage/71724d97-53ab-41b9-b6a9-ef743f602711?depth=5=OUTPUT
 HTTP/1.1" 200 2417 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:57 +] "GET 
/api/atlas/lineage/hive/table/sales_factV3RxPJxvcF/schema HTTP/1.1" 200 2502 
"-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:00:58 +] "GET 
/api/atlas/lineage/hive/table/sales_factV3RxPJxvcF/outputs/graph HTTP/1.1" 200 
2014 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:00 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factV3RxPJxvcF
 HTTP/1.1" 200 4370 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:00 +] "GET 
/api/atlas/lineage/d99848b9-3c1f-4f71-b7df-03bcb7ad2f27/outputs/graph HTTP/1.1" 
200 1942 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:01 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvfQ4Awn6994
 HTTP/1.1" 200 4061 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:01 +] "GET 
/api/atlas/v2/lineage/d75b01d6-4ee5-4474-b60a-026b0ac9ba5f?depth=5=INPUT
 HTTP/1.1" 200 2879 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:02 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvyjREGIrSGL
 HTTP/1.1" 200 4433 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:02 +] "GET 
/api/atlas/lineage/08ca81ff-605e-4f53-9437-3e676224658b/inputs/graph HTTP/1.1" 
200 2428 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:03 +] "GET 
/api/atlas/v2/types/typedef/name/database HTTP/1.1" 200 794 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:03 +] "GET 
/api/atlas/v2/types/typedef/name/table HTTP/1.1" 404 82 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:03 +] "GET 
/api/atlas/v2/types/typedef/name/fetl HTTP/1.1" 404 81 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:03 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 200 2038 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:04 +] "GET 
/api/atlas/v2/types/classificationdef/name/fetl HTTP/1.1" 200 454 "-" 
"Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:04 +] "GET 
/api/atlas/v2/types/entitydef/name/database HTTP/1.1" 200 794 "-" 
"Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:04 +] "GET 
/api/atlas/v2/types/entitydef/name/table HTTP/1.1" 200 1491 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:04 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 200 535 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:04 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 409 86 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:04 +] "GET 
/api/atlas/v2/types/enumdef/name/blah HTTP/1.1" 404 81 "-" "Java/1.8.0_144"
127.0.0.1 - - [19/Oct/2017:20:01:04 +] "GET 
/api/atlas/v2/types/enumdef/guid/blah HTTP/1.1" 404 82 "-"

[jira] [Comment Edited] (ATLAS-2210) Add relationship methods to AtlasClientV2

2017-10-19 Thread Andrew Hulbert (JIRA)


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

Andrew Hulbert edited comment on ATLAS-2210 at 10/19/17 5:29 PM:
-

forgot to ask...can someone assign this to me or add me with perms to do so? I 
think it should be all wrapped up now: https://reviews.apache.org/r/62984/


was (Author: hulbs):
forgot to ask...can someone assign this to me or add me with perms to do so? I 
think it should be all wrapped up now: 
https://issues.apache.org/jira/browse/ATLAS-2210

> Add relationship methods to AtlasClientV2
> -
>
> Key: ATLAS-2210
> URL: https://issues.apache.org/jira/browse/ATLAS-2210
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Andrew Hulbert
>




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

[jira] [Updated] (ATLAS-2218) Test stability across branches

2017-10-19 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2218:
---
Description: 
The tests are pretty inconsistent in runs across master and branch-0.8. This 
has been preventing a clean build in apache jenkins for a while now. This JIRA 
is aimed at ensuring build success across master and latest release branch.

Goals:

1. Make IT runs consistent
2. Make UTs run successfully on both
3. Separate UTs and ITs in webapp module
4. Fix UTs in distro module

  was:
The tests are pretty inconsistent in runs across master and branch-0.8. This 
has been preventing a clean build in apache jenkins for a while now. This JIRA 
is aimed at ensuring build success across master and latest release branch.

Goals:

1. Make IT runs consistent
2. Make UTs run successfully on both
3. Separate UTs and ITs in webapp module


> Test stability across branches
> --
>
> Key: ATLAS-2218
> URL: https://issues.apache.org/jira/browse/ATLAS-2218
> Project: Atlas
>  Issue Type: Bug
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>
> The tests are pretty inconsistent in runs across master and branch-0.8. This 
> has been preventing a clean build in apache jenkins for a while now. This 
> JIRA is aimed at ensuring build success across master and latest release 
> branch.
> Goals:
> 1. Make IT runs consistent
> 2. Make UTs run successfully on both
> 3. Separate UTs and ITs in webapp module
> 4. Fix UTs in distro module



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

Review Request 63152: ATLAS-2218: TestMetadata.py fix

2017-10-19 Thread Apoorv Naik


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

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath 
Subramanian.


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


Repository: atlas


Description
---

Recent changes to the startup script introduced a polling mechanism which waits 
for atlas server's response (heartbeat check). As a side effect the python unit 
tests took longer to execute because of the polling logic.

This change introduces the mocks for getConfig, getConfigWithDefault and 
wait_for_startup to reduce the test time from 11 mins to ~5 secs


Diffs
-

  distro/src/test/python/scripts/TestMetadata.py 1fd9a8cf 


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


Testing
---

mvn clean package executes successfully.


Thanks,

Apoorv Naik

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

2017-10-19 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-1.zip

> Create Subject Area 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: ATLAS1698-1.patch, ATLAS1698.patch, Atlas Glossary OMAS 
> API proposal v1.0 .pdf, Atlas Glossary OMAS API proposal v1.1.pdf, Atlas 
> Glossary OMAS API proposal v1.2.pdf, Subject Area OMAS API proposal v1.3.pdf, 
> apidocs-1.zip, apidocs.zip
>
>
> The Subject Area 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 Subject Area OMAS makes heavy use of the Area 3 open metadata model.  See 
> https://issues.apache.org/jira/browse/ATLAS-1840



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

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

2017-10-19 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: ATLAS1698-1.patch

> Create Subject Area 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: ATLAS1698-1.patch, ATLAS1698.patch, Atlas Glossary OMAS 
> API proposal v1.0 .pdf, Atlas Glossary OMAS API proposal v1.1.pdf, Atlas 
> Glossary OMAS API proposal v1.2.pdf, Subject Area OMAS API proposal v1.3.pdf, 
> apidocs.zip
>
>
> The Subject Area 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 Subject Area OMAS makes heavy use of the Area 3 open metadata model.  See 
> https://issues.apache.org/jira/browse/ATLAS-1840



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

Re: Atlas issues about atlas hdfs hook

2017-10-19 Thread Madhan Neethiraj

Junheng Cui,

 

>> The Atlas Hdfs Hook is in development phase, I can see the feature on your 
>> website. So could you tell me when will it be published?

Atlas hook for HDFS is one of the often-asked features in Atlas. Once the 
details activities to track in HDFS are finalized, we can publish ETA. Please 
help by sharing the use-cases you are interested in.

 

>> The atlas nifi hook can be found in community, but it has many bugs. I 
>> modified them, and it worked well. Could I put the codes to the github?

NiFi hooks is not part of Atlas github. Perhaps it is in NiFi github?

 

Thanks,

Madhan

 

 

 

From: "Junheng Cui (崔俊珩)" 
Reply-To: 
Date: Thursday, October 19, 2017 at 8:35 AM
To: "dev@atlas.apache.org" 
Subject: Atlas issues about atlas hdfs hook

 

Dear Atlas development team，

 

I am a SW engineer working at Inspur China. Now I am using Atlas for data 
government. But I hava some questions, may I ask you about that?

 

1. The Atlas Hdfs Hook is in development phase, I can see the feature on your 
website.

 So could you tell me when will it be published?

 

2. The atlas nifi hook can be found in community, but it has many bugs. I 
modified them, and it worked well.

  Could I put the codes to the github?

 

The Atlas is a very useful program for data government, it helps my company so 
much.

Thanks a lot! 

 

 

Best regards,

Junheng Cui

 

Software Development Engineer of R Center of INSPUR SOFTWARE Co., Ltd

Address:1036 Langchao Road, Jinan, Shandong Province, China

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

2017-10-19 Thread David Radley


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

(Updated Oct. 19, 2017, 4 p.m.)


Review request for atlas and Madhan Neethiraj.


Repository: atlas


Description
---

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

It does not include : 
- lineage

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


Diffs (updated)
-

  build-tools/src/main/resources/enunciate.xml dafd66f9 
  pom.xml f01c3418 
  subjectarea-omas/pom.xml PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/category/Category.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/Classification.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/EmbeddedMedia.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/Entity.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/MediaUsage.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/PList.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/Permission.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/Reference.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/Relatable.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/Relationship.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/SearchFilter.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/common/Status.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/exception/OMASBaseException.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/exception/OMASErrorCode.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/glossary/Anchor.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/glossary/Glossary.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/graph/GlossaryGraph.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/graph/GlossaryGraphEdge.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/graph/GlossaryGraphEdgeDirection.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/graph/GlossaryGraphNode.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/graph/Graphformat.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/ExternalGlossaryLink.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/RelatedTerms/Antonym.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/RelatedTerms/ISA.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/RelatedTerms/PreferedTerm.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/RelatedTerms/RelatedTerm.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/RelatedTerms/RelatedTerms.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/RelatedTerms/ReplacementTerm.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/RelatedTerms/Synonym.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/RelatedTerms/Translation.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/RelatedTerms/ValidValue.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/SemanticAssignment/SemanticAssignment.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/Term.java 
PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/TermRelationshipStatus.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/contexts/Context.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/spineObjects/SpineObjects.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/spineObjects/TermHASARelationship.java
 PRE-CREATION 
  
subjectarea-omas/src/main/java/org/apache/atlas/omas/subjectarea/term/spineObjects/TermISATYPEOFRelationship.java
 PRE-CREATION

[jira] [Commented] (ATLAS-1757) Proposal to update graph DB

2017-10-19 Thread David Radley (JIRA)


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

David Radley commented on ATLAS-1757:
-

[~hulbs] The equivalent to the RDB grant is all done through Ranger - which 
gives us great separation of responsibility and flexibility.  I have no reason 
to think that Apache Ranger mechanism is not strong enough for the use cases we 
have looked at.   

If the data really needs to be separate - and does not need to be joined, then 
it might make sense to have them in separate data lakes - i.e. separate 
Atlas's. 

> Proposal to update graph DB
> ---
>
> Key: ATLAS-1757
> URL: https://issues.apache.org/jira/browse/ATLAS-1757
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Graham Wallis
> Attachments: ATLAS-1757 Proposal to change graph database.pdf, 
> ATLAS-1757-v1.patch, ATLAS-1757-v2.patch
>
>
> Given the formation of the JanusGraph open source project (under the Linux 
> Foundation) to continue the development and support of the Titan DB, should 
> we aim to deprecate Titan and move over to JanusGraph?
> If we did this, we could keep the graph abstraction layer and use it to 
> support Titan 0, Titan 1 and JanusGraph.
> Are there other graph databases that we should consider?



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

Atlas issues about atlas hdfs hook

2017-10-19 Thread 崔俊珩

Dear Atlas development team，

 

I am a SW engineer working at Inspur China. Now I am using Atlas for data
government. But I hava some questions, may I ask you about that?

 

1. The Atlas Hdfs Hook is in development phase, I can see the feature on
your website.

 So could you tell me when will it be published?

 

2. The atlas nifi hook can be found in community, but it has many bugs. I
modified them, and it worked well.

  Could I put the codes to the github?

 

The Atlas is a very useful program for data government, it helps my company
so much.

Thanks a lot! 

 

 

Best regards,

Junheng Cui

 

  _  

Software Development Engineer of R Center of INSPUR SOFTWARE Co., Ltd

Address:1036 Langchao Road, Jinan, Shandong Province, China 

 



smime.p7s
Description: S/MIME cryptographic signature

[jira] [Commented] (ATLAS-1757) Proposal to update graph DB

2017-10-19 Thread Andrew Hulbert (JIRA)


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

Andrew Hulbert commented on ATLAS-1757:
---

[~davidrad] I'll try to take a look over at the Virtual Data Connector pages 
and discussions. I think that "field-level" visibility is definitely something 
that's useful for what I'm working on but the "cell-level" visibility is 
probably (as you mentioned) not as much on the radar at the moment. But I'll 
try to chat with he VD connector group and see what they are thinking. We have 
customers that need to segregate data from different divisions and want that 
strong guarantee on a per "entity" basis.

> Proposal to update graph DB
> ---
>
> Key: ATLAS-1757
> URL: https://issues.apache.org/jira/browse/ATLAS-1757
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Graham Wallis
> Attachments: ATLAS-1757 Proposal to change graph database.pdf, 
> ATLAS-1757-v1.patch, ATLAS-1757-v2.patch
>
>
> Given the formation of the JanusGraph open source project (under the Linux 
> Foundation) to continue the development and support of the Titan DB, should 
> we aim to deprecate Titan and move over to JanusGraph?
> If we did this, we could keep the graph abstraction layer and use it to 
> support Titan 0, Titan 1 and JanusGraph.
> Are there other graph databases that we should consider?



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

[jira] [Commented] (ATLAS-2210) Add relationship methods to AtlasClientV2

2017-10-19 Thread Andrew Hulbert (JIRA)


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

Andrew Hulbert commented on ATLAS-2210:
---

forgot to ask...can someone assign this to me or add me with perms to do so? I 
think it should be all wrapped up now: 
https://issues.apache.org/jira/browse/ATLAS-2210

> Add relationship methods to AtlasClientV2
> -
>
> Key: ATLAS-2210
> URL: https://issues.apache.org/jira/browse/ATLAS-2210
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Andrew Hulbert
>




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

[jira] [Created] (ATLAS-2219) UI Regression : Unable to provide exponential values for tag attribute values in UI.

2017-10-19 Thread Sharmadha Sainath (JIRA)

Sharmadha Sainath created ATLAS-2219:


 Summary: UI Regression : Unable to provide exponential values for 
tag attribute values in UI.
 Key: ATLAS-2219
 URL: https://issues.apache.org/jira/browse/ATLAS-2219
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath
Assignee: Keval Bhatt
Priority: Critical


For tag attributes of data type double , float etc, the corresponding text box 
is not accepting 'E' character for providing exponential values.




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

Build failed in Jenkins: Atlas-master-UnitTests #138

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

[jira] [Comment Edited] (ATLAS-2210) Add relationship methods to AtlasClientV2

[jira] [Updated] (ATLAS-2218) Test stability across branches

Review Request 63152: ATLAS-2218: TestMetadata.py fix

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

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

Re: Atlas issues about atlas hdfs hook

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

[jira] [Commented] (ATLAS-1757) Proposal to update graph DB

Atlas issues about atlas hdfs hook

[jira] [Commented] (ATLAS-1757) Proposal to update graph DB

[jira] [Commented] (ATLAS-2210) Add relationship methods to AtlasClientV2

[jira] [Created] (ATLAS-2219) UI Regression : Unable to provide exponential values for tag attribute values in UI.

14 matches

Site Navigation

Mail list logo

Footer information