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

2017-10-16 Thread Jerry He (JIRA)

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

Jerry He commented on ATLAS-1757:
-

[~hulbs]  Please see this ticket on JanusGraph 
https://github.com/JanusGraph/janusgraph/issues/493

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


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

2017-10-16 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2213: Remove unused attributes from Hive hook

--
[...truncated 515.02 KB...]
127.0.0.1 - - [16/Oct/2017:19:32:29 +] "POST 
/api/atlas/entities/b1489c21-f33b-48af-86c2-6d463db7c0dc/traits HTTP/1.1" 201 - 
"-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:29 +] "POST 
/api/atlas/entities/b1489c21-f33b-48af-86c2-6d463db7c0dc/traits HTTP/1.1" 400 - 
"-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:29 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:29 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:30 +] "DELETE 
/api/atlas/entities?guid=4311e8ae-9c43-4b10-8fac-ef6691c92815&guid=befa1a85-026a-4cda-8831-7dfb680c4ca4
 HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:30 +] "GET 
/api/atlas/entities/befa1a85-026a-4cda-8831-7dfb680c4ca4 HTTP/1.1" 200 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:30 +] "GET 
/api/atlas/entities/4311e8ae-9c43-4b10-8fac-ef6691c92815 HTTP/1.1" 200 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:30 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:30 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:30 +] "GET 
/api/atlas/entities?type=hive_table HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:30 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:31 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:31 +] "GET 
/api/atlas/v2/types/typedef/name/PII_TraitlNqgqa9ef4 HTTP/1.1" 404 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:31 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "DELETE 
/api/atlas/entities/4fd5e08b-d4bb-4ff5-9917-54b0f3b3e2da/traits/PII_TraitlNqgqa9ef4
 HTTP/1.1" 404 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "POST 
/api/atlas/entities/qualifiedName?type=hive_table&property=qualifiedName&value=tablepMLylnVMLK
 HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "GET 
/api/atlas/entities/6bb4ea95-d607-4116-8e32-651306dac5ea HTTP/1.1" 200 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "DELETE 
/api/atlas/entities?guid=9496961f-f7c9-47a5-b4fd-2503c01789a5&guid=366cae84-9ecb-4326-9439-ad05eafd8ab5
 HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "GET 
/api/atlas/entities/366cae84-9ecb-4326-9439-ad05eafd8ab5 HTTP/1.1" 200 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "GET 
/api/atlas/entities/9496961f-f7c9-47a5-b4fd-2503c01789a5 HTTP/1.1" 200 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:32 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:33 +] "POST 
/api/atlas/entities/13936de7-479b-445a-97cf-d8102b0755d7 HTTP/1.1" 200 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:33 +] "GET 
/api/atlas/entities/13936de7-479b-445a-97cf-d8102b0755d7 HTTP/1.1" 200 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:34 +] "GET 
/api/atlas/v2/types/typedef/name/PII_Traituqmz1MCgcr HTTP/1.1" 404 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:34 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:19:32:34 +] "POST 
/api/atlas/entities/37c33967-d072-4163-8860-e0c24af10df3/traits HTTP/1.1" 201 - 
"-" "Java/1.8.0_144"
127.0.0.1 -

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

2017-10-16 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2213: Remove unused attributes from Hive hook

--
[...truncated 459.17 KB...]
[INFO] 
[INFO] 
[INFO] --- jetty-maven-plugin:9.4.0.v20161208:deploy-war (start-jetty) @ 
atlas-webapp ---
[INFO] Logging initialized @624391ms to org.eclipse.jetty.util.log.Slf4jLog
[INFO] Configuring Jetty for project: Apache Atlas Web Application
[INFO] Context path = /
[INFO] Tmp directory = 

[INFO] Web defaults = org/eclipse/jetty/webapp/webdefault.xml
[INFO] Web overrides =  none
[INFO] jetty-9.4.0.v20161208
[INFO] Scanning elapsed time=21128ms
[INFO] No Spring WebApplicationInitializer types detected on classpath
[WARNING] Using @Deprecated Class 
org.springframework.web.util.Log4jConfigListener
[INFO] DefaultSessionIdManager workerName=node0
[INFO] No SessionScavenger set, using defaults
[INFO] Scavenging every 66ms
[INFO] Set web app root system property: 'webapp.root' = 
[
log4j:WARN No such property [maxFileSize] in org.apache.log4j.PatternLayout.
log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.PatternLayout.
log4j:WARN No such property [maxFileSize] in org.apache.log4j.PatternLayout.
log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.PatternLayout.
log4j:WARN No such property [maxFileSize] in org.apache.log4j.PatternLayout.
[INFO] Initializing Spring root WebApplicationContext
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.servlet.SpringServlet getContext
INFO: Using default applicationContext
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, typesREST, of type 
org.apache.atlas.web.rest.TypesREST as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, lineageREST, of type 
org.apache.atlas.web.rest.LineageREST as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, relationshipREST, of type 
org.apache.atlas.web.rest.RelationshipREST as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, entityREST, of type 
org.apache.atlas.web.rest.EntityREST as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, discoveryREST, of type 
org.apache.atlas.web.rest.DiscoveryREST as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, taxonomyService, of type 
org.apache.atlas.web.resources.TaxonomyService as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, metadataDiscoveryResource, of type 
org.apache.atlas.web.resources.MetadataDiscoveryResource as a root resource 
class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, adminResource, of type 
org.apache.atlas.web.resources.AdminResource as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, lineageResource, of type 
org.apache.atlas.web.resources.LineageResource as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, entityService, of type 
org.apache.atlas.web.resources.EntityService as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, typesResource, of type 
org.apache.atlas.web.resources.TypesResource as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, dataSetLineageResource, of type 
org.apache.atlas.web.resources.DataSetLineageResource as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentProviderFactory 
registerSpringBeans
INFO: Registering Spring bean, entityResource, of type 
org.apache.atlas.web.resources.EntityResource as a root resource class
Oct 16, 2017 7:25:14 PM 
com.sun.jersey.spi.spring.container.SpringComponentPr

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

2017-10-16 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2213: Remove unused attributes from Hive hook

--
[...truncated 509.76 KB...]
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.654 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.702 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.293 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.528 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.TaxonomyServiceTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.02 sec - in 
org.apache.atlas.web.resources.TaxonomyServiceTest
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.367 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.337 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.304 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.33 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: 13.027 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.306 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: 13.659 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.344 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$2
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$7
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.407 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$7
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapter

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

2017-10-16 Thread Sarath Subramanian (JIRA)

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

Sarath Subramanian commented on ATLAS-1757:
---

[~grahamwallis] could you rebase your latest patch and upload it to review 
board, it fails to apply on master. 

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


Re: Review Request 62889: ATLAS-1757 POM changes

2017-10-16 Thread Apoorv Naik

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


Ship it!




Ship It!

- Apoorv Naik


On Oct. 11, 2017, 1:43 p.m., Graham Wallis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62889/
> ---
> 
> (Updated Oct. 11, 2017, 1:43 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch contains changes to 13 POM files to simplify the selection of 
> graph database, which should be 
> performed by specifying the GRAPH-PROVIDER system variable, e.g.
> 
> mvn clean install -DGRAPH-PROVIDER=titan0
> 
> If GRAPH-PROVIDER is not specified, the default graph database is selected. 
> This is currently titan0
> If GRAPH-PROVIDER is specified, valid values are titan0 and titan1.
> 
> The old graph profiles ('titan0', 'titan1') have been removed.
> 
> This patch also simplifies dependency management in the POM files and removes 
> a number of duplicate entries.
> 
> 
> Diffs
> -
> 
>   catalog/pom.xml 0d13ae47bc1ce1890d706c6ee6c2d3ddeeb42d73 
>   distro/pom.xml 9bea00852cb10ddca363ef1e726487394f6947f3 
>   distro/src/conf/atlas-application.properties 
> 585a57919d8ce5f5a921918c27e45c0dbc660043 
>   graphdb/api/pom.xml 186e7455353c4d073f297868cc884c178d102106 
>   graphdb/graphdb-impls/pom.xml 62a09944f7655098319d477d362c7181f4b373d1 
>   graphdb/titan0/pom.xml df89e4fa52581f60e5ba962b114911a1b582f0b0 
>   graphdb/titan0/src/test/resources/atlas-application.properties 
> 3058330668424e0b860d0bfe932f78bfb3db8ec1 
>   graphdb/titan1/pom.xml 146155b73c24dbe10408a5d7071d6c9df02cf514 
>   graphdb/titan1/src/test/resources/atlas-application.properties 
> 99fe18a9d177403c8d7b41f2486709f1c6f24c3d 
>   pom.xml 39ae6e7239b690cbf6dff69028b0d6e392777415 
>   repository/pom.xml b7eedde0a30a1716bc9665f2acfa02e169ba183f 
>   typesystem/src/test/resources/atlas-application.properties 
> d7537a516551d745fa0ab5f854c9207cb7a2cfc1 
>   webapp/pom.xml bfa79e8101f1de962c26c48e3c71beb8e73b8876 
> 
> 
> Diff: https://reviews.apache.org/r/62889/diff/1/
> 
> 
> Testing
> ---
> 
> Builds before and after POM changes with no new test failures being 
> introduced.
> 
> 
> Thanks,
> 
> Graham Wallis
> 
>



Re: Review Request 62984: ATLAS-2210 Get and Delete Relationships in AtlasClientV2

2017-10-16 Thread Andrew Hulbert


> On Oct. 16, 2017, 2:44 p.m., Apoorv Naik wrote:
> > client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java
> > Lines 387 (patched)
> > 
> >
> > Yes, the responseType param should be set to null for methods with 204 
> > response(no body). 
> > 
> > ```java 
> > 
> > public void deleteRelationshipByGuid(String guid) throws 
> > AtlasServiceException {
> > callAPI(API_V2.DELETE_RELATIONSHIP_BY_GUID, null, null, guid);
> > }
> > 
> > ```
> > 
> > This should work.

cool, thanks.


- Andrew


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


On Oct. 13, 2017, 2:48 p.m., Andrew Hulbert wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62984/
> ---
> 
> (Updated Oct. 13, 2017, 2:48 p.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2210
> https://issues.apache.org/jira/browse/ATLAS-2210
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add calls to get and delete relationships to AtlasClientV2
> 
> 
> Diffs
> -
> 
>   client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 24a3ef6 
> 
> 
> Diff: https://reviews.apache.org/r/62984/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Andrew Hulbert
> 
>



Review Request 63041: ATLAS-1757 Introduction of janus

2017-10-16 Thread Graham Wallis

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

Review request for atlas.


Repository: atlas


Description
---

ATLAS-1757-v2.patch
This patch contains the POM changes post v1 review, and the first pass at the 
janus module.
There has been no testing of the janus module yet - this is work in progress.


Diffs
-

  catalog/pom.xml 0d13ae47bc1ce1890d706c6ee6c2d3ddeeb42d73 
  distro/pom.xml 9bea00852cb10ddca363ef1e726487394f6947f3 
  distro/src/conf/atlas-application.properties 
585a57919d8ce5f5a921918c27e45c0dbc660043 
  graphdb/api/pom.xml 186e7455353c4d073f297868cc884c178d102106 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/NativeTitanGraphQuery.java
 288b325acd5649eecee9b67346fb3aa6ff9603d2 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/NativeTitanQueryFactory.java
 ac7ff9e81f658e2d0939a9be2555dd9a18083d30 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/TitanGraphQuery.java
 dfdb91b587b812a41a407acae8e794a23ec1c077 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/expr/AndCondition.java
 db5093f518ca36fbb4ab9786cc4c47349fa05cd8 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/expr/HasPredicate.java
 0652c41bcfb30b098d8aa08ac96685d8f6cad312 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/expr/InPredicate.java
 ca0e8ab53e2e1083bf01b486945a0c3cffeda527 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/expr/OrCondition.java
 e7a8a75238cf5df0f94b9ceb7723fd983a8866d9 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/expr/QueryPredicate.java
 a80522b56558fbf73177eb1cf6fc34ba09f6d769 
  graphdb/graphdb-impls/pom.xml 62a09944f7655098319d477d362c7181f4b373d1 
  graphdb/janus/pom.xml PRE-CREATION 
  graphdb/janus/readme.txt PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusEdge.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusEdgeLabel.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusElement.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraph.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraphDatabase.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraphIndex.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraphManagement.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusIndexQuery.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusObjectFactory.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusPropertyKey.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusVertex.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusVertexQuery.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/GraphDbObjectFactory.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/graphson/AtlasElementPropertyConfig.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/graphson/AtlasGraphSONMode.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/graphson/AtlasGraphSONTokens.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/graphson/AtlasGraphSONUtility.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/query/AtlasJanusGraphQuery.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/query/NativeJanusGraphQuery.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/serializer/BigDecimalSerializer.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/serializer/BigIntegerSerializer.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/serializer/StringListSerializer.java
 PRE-CREATION 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/serializer/TypeCategorySerializer.java
 PRE-CREATION 
  
graphdb/janus/src/main/resources/META-INF/services/javax.script.ScriptEngineFactory
 PRE-CREATION 
  
graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/AbstractGraphDat

Re: Review Request 62984: ATLAS-2210 Get and Delete Relationships in AtlasClientV2

2017-10-16 Thread Apoorv Naik

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




client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java
Lines 387 (patched)


Yes, the responseType param should be set to null for methods with 204 
response(no body). 

```java 

public void deleteRelationshipByGuid(String guid) throws 
AtlasServiceException {
callAPI(API_V2.DELETE_RELATIONSHIP_BY_GUID, null, null, guid);
}

```

This should work.


- Apoorv Naik


On Oct. 13, 2017, 6:48 p.m., Andrew Hulbert wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62984/
> ---
> 
> (Updated Oct. 13, 2017, 6:48 p.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2210
> https://issues.apache.org/jira/browse/ATLAS-2210
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add calls to get and delete relationships to AtlasClientV2
> 
> 
> Diffs
> -
> 
>   client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 24a3ef6 
> 
> 
> Diff: https://reviews.apache.org/r/62984/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Andrew Hulbert
> 
>



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

2017-10-16 Thread Graham Wallis (JIRA)

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

Graham Wallis updated ATLAS-1757:
-
Attachment: ATLAS-1757-v2.patch

> 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] [Updated] (ATLAS-1757) Proposal to update graph DB

2017-10-16 Thread Graham Wallis (JIRA)

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

Graham Wallis updated ATLAS-1757:
-
Attachment: (was: ATLAS-1757-v2.patch)

> 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] [Comment Edited] (ATLAS-1757) Proposal to update graph DB

2017-10-16 Thread Andrew Hulbert (JIRA)

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

Andrew Hulbert edited comment on ATLAS-1757 at 10/16/17 6:18 PM:
-

Is there anything on the roadmap for the future to support visibility filtering 
with Atlas + JanusGraph + HBase? For example, it would be interesting to have 
the ability to access control specific vertices, attributes, or relationships 
based on visibilities which systems like bigtable systems like HBase and 
Accumulo can support. I'd be interested to see if anyone else desires this and 
if so I'd probably put a vote in for JanusGraph and contributing to help make 
that a top level feature in both Atlas and JanusGraph.

On another note, I like having the Apache 2 and Hadoop-related graph 
implementation. There's lots of HBase already out there so having at least 1 
graph implementation on that keeps Atlas in line with that stack.


was (Author: hulbs):
Is there anything on the roadmap for the future to support visibility filtering 
with Atlas + JanusGraph + HBase? For example, it would be interesting to have 
the ability to access control specific vertices, attributes, or relationships 
based on visibilities which systems like bigtable systems like HBase and 
Accumulo can support. I'd be interested to see if anyone else desires this and 
if so I'd probably put a vote in for JanusGraph and contributing to help make 
that a top level feature in both Atlas and JanusGraph.

> 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-1757) Proposal to update graph DB

2017-10-16 Thread Andrew Hulbert (JIRA)

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

Andrew Hulbert commented on ATLAS-1757:
---

Is there anything on the roadmap for the future to support visibility filtering 
with Atlas + JanusGraph + HBase? For example, it would be interesting to have 
the ability to access control specific vertices, attributes, or relationships 
based on visibilities which systems like bigtable systems like HBase and 
Accumulo can support. I'd be interested to see if anyone else desires this and 
if so I'd probably put a vote in for JanusGraph and contributing to help make 
that a top level feature in both Atlas and JanusGraph.

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


Re: Review Request 63037: ATLAS-2213: Remove unused attributes from Hive hook

2017-10-16 Thread Sarath Subramanian

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


Ship it!




Ship It!

- Sarath Subramanian


On Oct. 16, 2017, 10:45 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63037/
> ---
> 
> (Updated Oct. 16, 2017, 10:45 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-2213
> https://issues.apache.org/jira/browse/ATLAS-2213
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Removed API calls to retrieve queryType value, as this field is not unsed in 
> Atlas Hive entities.
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> f815773e 
> 
> 
> Diff: https://reviews.apache.org/r/63037/diff/1/
> 
> 
> Testing
> ---
> 
> Verified that UTs pass successfully.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



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

2017-10-16 Thread Graham Wallis (JIRA)

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

Graham Wallis updated ATLAS-1757:
-
Attachment: ATLAS-1757-v2.patch

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


Re: Review Request 62984: ATLAS-2210 Get and Delete Relationships in AtlasClientV2

2017-10-16 Thread Andrew Hulbert


> On Oct. 13, 2017, 4:52 p.m., Apoorv Naik wrote:
> > client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java
> > Lines 387 (patched)
> > 
> >
> > formatPathParameters call is not needed here
> > 
> > instead do exactly what you did for the get call
> > 
> > ```java 
> > public static final API_V2 DELETE_RELATIONSHIP_BY_GUID = new 
> > API_V2(RELATIONSHIPS_URI + "guid/", HttpMethod.DELETE, 
> > Response.Status.NO_CONTENT);
> > 
> > public void deleteRelationshipByGuid(String guid) throws 
> > AtlasServiceException {
> > callAPI(API_V2.DELETE_RELATIONSHIP_BY_GUID, 
> > AtlasRelationship.class, null, guid);
> > }
> > ```

Note that the response is null so I set it to null (instead of 
AtlasRelationship.class) and it seems to return 204 no content ok. Let me know!


- Andrew


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


On Oct. 13, 2017, 2:48 p.m., Andrew Hulbert wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62984/
> ---
> 
> (Updated Oct. 13, 2017, 2:48 p.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2210
> https://issues.apache.org/jira/browse/ATLAS-2210
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add calls to get and delete relationships to AtlasClientV2
> 
> 
> Diffs
> -
> 
>   client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 24a3ef6 
> 
> 
> Diff: https://reviews.apache.org/r/62984/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Andrew Hulbert
> 
>



[jira] [Updated] (ATLAS-2213) HiveHook update to remove unused attributes

2017-10-16 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj updated ATLAS-2213:

Attachment: ATLAS-2213.patch

> HiveHook update to remove unused attributes
> ---
>
> Key: ATLAS-2213
> URL: https://issues.apache.org/jira/browse/ATLAS-2213
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 0.8.1
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Attachments: ATLAS-2213.patch
>
>
> Atas Hive hook calls Hive APIs to get values to populate Hive entity 
> attributes. Some of these values obtained from Hive are unused in Hive 
> entities - like queryType. Hive hook should be updated to remove such unused 
> attributes.



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


Review Request 63037: ATLAS-2213: Remove unused attributes from Hive hook

2017-10-16 Thread Madhan Neethiraj

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

Review request for atlas.


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


Repository: atlas


Description
---

Removed API calls to retrieve queryType value, as this field is not unsed in 
Atlas Hive entities.


Diffs
-

  addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
f815773e 


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


Testing
---

Verified that UTs pass successfully.


Thanks,

Madhan Neethiraj



Re: Review Request 62889: ATLAS-1757 POM changes

2017-10-16 Thread Graham Wallis


> On Oct. 11, 2017, 3:51 p.m., Apoorv Naik wrote:
> > catalog/pom.xml
> > Line 46 (original), 49 (patched)
> > 
> >
> > Any issues with Lucene 4.10.4 with TP2 ?

Hi Apoorv, For catalog I just preserved the dependency versions we were already 
using. Catalog is due for removal so I don't think there would be any point 
updating its dependencies.

The 4.10.4 lucene version property was only if we are in the 'titan1' profile, 
but we know that catalog doesn't work with titan1 because catalog is code to 
TP2, so I stuck with the non-titan1-profile version, i.e 4.8.1.


- Graham


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


On Oct. 11, 2017, 1:43 p.m., Graham Wallis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62889/
> ---
> 
> (Updated Oct. 11, 2017, 1:43 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch contains changes to 13 POM files to simplify the selection of 
> graph database, which should be 
> performed by specifying the GRAPH-PROVIDER system variable, e.g.
> 
> mvn clean install -DGRAPH-PROVIDER=titan0
> 
> If GRAPH-PROVIDER is not specified, the default graph database is selected. 
> This is currently titan0
> If GRAPH-PROVIDER is specified, valid values are titan0 and titan1.
> 
> The old graph profiles ('titan0', 'titan1') have been removed.
> 
> This patch also simplifies dependency management in the POM files and removes 
> a number of duplicate entries.
> 
> 
> Diffs
> -
> 
>   catalog/pom.xml 0d13ae47bc1ce1890d706c6ee6c2d3ddeeb42d73 
>   distro/pom.xml 9bea00852cb10ddca363ef1e726487394f6947f3 
>   distro/src/conf/atlas-application.properties 
> 585a57919d8ce5f5a921918c27e45c0dbc660043 
>   graphdb/api/pom.xml 186e7455353c4d073f297868cc884c178d102106 
>   graphdb/graphdb-impls/pom.xml 62a09944f7655098319d477d362c7181f4b373d1 
>   graphdb/titan0/pom.xml df89e4fa52581f60e5ba962b114911a1b582f0b0 
>   graphdb/titan0/src/test/resources/atlas-application.properties 
> 3058330668424e0b860d0bfe932f78bfb3db8ec1 
>   graphdb/titan1/pom.xml 146155b73c24dbe10408a5d7071d6c9df02cf514 
>   graphdb/titan1/src/test/resources/atlas-application.properties 
> 99fe18a9d177403c8d7b41f2486709f1c6f24c3d 
>   pom.xml 39ae6e7239b690cbf6dff69028b0d6e392777415 
>   repository/pom.xml b7eedde0a30a1716bc9665f2acfa02e169ba183f 
>   typesystem/src/test/resources/atlas-application.properties 
> d7537a516551d745fa0ab5f854c9207cb7a2cfc1 
>   webapp/pom.xml bfa79e8101f1de962c26c48e3c71beb8e73b8876 
> 
> 
> Diff: https://reviews.apache.org/r/62889/diff/1/
> 
> 
> Testing
> ---
> 
> Builds before and after POM changes with no new test failures being 
> introduced.
> 
> 
> Thanks,
> 
> Graham Wallis
> 
>



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

2017-10-16 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2212: UI fix to allow negative number input for tag attributes

--
[...truncated 474.55 KB...]
127.0.0.1 - - [16/Oct/2017:16:56:09 +] "GET 
/api/atlas/entities?type=hive_table_v1&property=qualifiedName&value=sales_fact_monthly_mvKmblmwTCV9
 HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:09 +] "GET 
/api/atlas/lineage/da775ecd-abc1-445d-aaa1-e717591a4eb8/inputs/graph HTTP/1.1" 
200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:11 +] "GET 
/api/atlas/lineage/hive/table/sales_factTZG2HxEH7k/outputs/graph HTTP/1.1" 200 
- "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:13 +] "GET 
/api/atlas/entities?type=hive_table_v1&property=qualifiedName&value=sales_factTZG2HxEH7k
 HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:13 +] "GET 
/api/atlas/lineage/c0a9e4d7-3174-4534-ae64-7cfd19074841/outputs/graph HTTP/1.1" 
200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:14 +] "GET 
/api/atlas/lineage/hive/table/sales_factTZG2HxEH7k/schema HTTP/1.1" 200 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:15 +] "GET 
/api/atlas/lineage/hive/table/SalessFSuZeXvdJ/schema HTTP/1.1" 404 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:15 +] "GET 
/api/atlas/entities?type=hive_table_v1&property=qualifiedName&value=sales_factTZG2HxEH7k
 HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:15 +] "GET 
/api/atlas/lineage/c0a9e4d7-3174-4534-ae64-7cfd19074841/schema HTTP/1.1" 200 - 
"-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:15 +] "GET 
/api/atlas/lineage/hive/table/blah/schema HTTP/1.1" 404 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 409 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/tableType HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/serdeType HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/hive_db_v2 HTTP/1.1" 404 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/hive_column_v2 HTTP/1.1" 404 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/hive_table_v2 HTTP/1.1" 404 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/hive_process_v2 HTTP/1.1" 404 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/classification HTTP/1.1" 200 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/pii HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/phi HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/pci HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/sox HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/sec HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "GET 
/api/atlas/v2/types/typedef/name/finance HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:16 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:17 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:17 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:17 +] "GET 
/api/atlas/v2/entity/guid/692dc358-2610-45bd-9538-39fc16c2cde7 HTTP/1.1" 200 - 
"-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:17 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:17 +] "POST 
/api/atlas/v2/entity/guid/random/classifications HTTP/1.1" 404 - "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:17 +] "POST /api/atlas/v2/entity/bulk 
HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:18 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:18 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:18 +] "DELETE 
/api/atlas/v2/entity/bulk?guid=19248ba4-8c46-4029-95c2-6cafef80c706&guid=9f116500-d0e5-4720-9678-37813ca02c00
 HTTP/1.1" 200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:56:18 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2

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

2017-10-16 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2212: UI fix to allow negative number input for tag attributes

--
[...truncated 509.12 KB...]
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.filters.ActiveServerFilterTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.964 sec - in 
org.apache.atlas.web.filters.ActiveServerFilterTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.filters.AtlasCSRFPreventionFilterTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.242 sec - in 
org.apache.atlas.web.filters.AtlasCSRFPreventionFilterTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.filters.AtlasAuthenticationKerberosFilterTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.345 sec - in 
org.apache.atlas.web.filters.AtlasAuthenticationKerberosFilterTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.filters.AuditFilterTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.27 sec - in 
org.apache.atlas.web.filters.AuditFilterTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.AtlasZookeeperSecurityPropertiesTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.42 sec - in 
org.apache.atlas.web.service.AtlasZookeeperSecurityPropertiesTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.ServiceStateTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.849 sec - in 
org.apache.atlas.web.service.ServiceStateTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.CuratorFactoryTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.25 sec - in 
org.apache.atlas.web.service.CuratorFactoryTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.SecureEmbeddedServerTest
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 48.59 sec <<< 
FAILURE! - in org.apache.atlas.web.service.SecureEmbeddedServerTest
testServerConfiguredUsingCredentialProvider(org.apache.atlas.web.service.SecureEmbeddedServerTest)
  Time elapsed: 43.673 sec  <<< FAILURE!
java.lang.AssertionError: War deploy failed
at sun.security.ssl.InputRecord.read(InputRecord.java:505)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983)
at 
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397)
at 
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
at 
org.apache.atlas.web.service.SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider(SecureEmbeddedServerTest.java:74)

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.ActiveInstanceStateTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.91 sec - in 
org.apache.atlas.web.service.ActiveInstanceStateTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.ActiveInstanceElectorServiceTest
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.113 sec - in 
org.apache.atlas.web.service.ActiveInstanceElect

[jira] [Created] (ATLAS-2213) HiveHook update to remove unused attributes

2017-10-16 Thread Madhan Neethiraj (JIRA)
Madhan Neethiraj created ATLAS-2213:
---

 Summary: HiveHook update to remove unused attributes
 Key: ATLAS-2213
 URL: https://issues.apache.org/jira/browse/ATLAS-2213
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Affects Versions: 0.8.1
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Atas Hive hook calls Hive APIs to get values to populate Hive entity 
attributes. Some of these values obtained from Hive are unused in Hive entities 
- like queryType. Hive hook should be updated to remove such unused attributes.



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


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

2017-10-16 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2212: UI fix to allow negative number input for tag attributes

--
[...truncated 464.03 KB...]
INFO: Registering Spring bean, notFoundExceptionMapper, of type 
org.apache.atlas.web.errors.NotFoundExceptionMapper as a provider class
Oct 16, 2017 4:43:09 PM 
com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.19 02/11/2015 03:25 AM'
[INFO] Started 
o.e.j.m.p.JettyWebAppContext@684876e8{/,file://
[INFO] Started ServerConnector@dab2a4c{HTTP/1.1,[http/1.1]}{0.0.0.0:31000}
[INFO] Started @480014ms
[INFO] Started Jetty Server
[INFO] 
[INFO] --- maven-failsafe-plugin:2.18.1:integration-test (integration-test) @ 
atlas-webapp ---
[WARNING] useSystemClassloader setting has no effect when not forking
[INFO] Failsafe report directory: 

Running TestSuite
127.0.0.1 - - [16/Oct/2017:16:43:12 +] "GET 
/api/atlas/v2/types/typedef/name/database HTTP/1.1" 404 85 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:12 +] "GET 
/api/atlas/v2/types/typedef/name/table HTTP/1.1" 404 82 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:12 +] "GET 
/api/atlas/v2/types/typedef/name/fetl HTTP/1.1" 404 81 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:12 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 200 2653 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/classificationdef/name/fetl HTTP/1.1" 200 454 "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/entitydef/name/database HTTP/1.1" 200 614 "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/entitydef/name/table HTTP/1.1" 200 1491 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 200 535 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 409 86 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/enumdef/name/blah HTTP/1.1" 404 81 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/enumdef/guid/blah HTTP/1.1" 404 82 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/structdef/name/blah HTTP/1.1" 404 81 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/structdef/guid/blah HTTP/1.1" 404 82 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/classificationdef/name/blah HTTP/1.1" 404 81 "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/classificationdef/guid/blah HTTP/1.1" 404 82 "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/entitydef/name/blah HTTP/1.1" 404 81 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/entitydef/guid/blah HTTP/1.1" 404 82 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 200 1918 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/typedefs?supertype=ANDMWWtkWxQ&type=CLASS HTTP/1.1" 200 
1026 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/typedefs?supertype=ANDMWWtkWxQ&type=CLASS¬supertype=BdraBVKbFSf
 HTTP/1.1" 200 553 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "POST /api/atlas/v2/types/typedefs 
HTTP/1.1" 200 535 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "PUT /api/atlas/v2/types/typedefs 
HTTP/1.1" 200 711 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:14 +] "GET 
/api/atlas/v2/types/typedefs?type=ENTITY HTTP/1.1" 200 5087 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:15 +] "GET 
/api/atlas/v2/types/typedef/name/tableType HTTP/1.1" 404 86 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:15 +] "GET 
/api/atlas/v2/types/typedef/name/serdeType HTTP/1.1" 404 86 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:15 +] "GET 
/api/atlas/v2/types/typedef/name/classification HTTP/1.1" 404 91 "-" 
"Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:15 +] "GET 
/api/atlas/v2/types/typedef/name/pii HTTP/1.1" 404 80 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:15 +] "GET 
/api/atlas/v2/types/typedef/name/phi HTTP/1.1" 404 80 "-" "Java/1.8.0_144"
127.0.0.1 - - [16/Oct/2017:16:43:15 +] "GET 
/api/atlas/v2

Re: Review Request 63029: ATLAS-2212 : Regression : Unable to provide negative values directly for tag attributes of data type int.

2017-10-16 Thread Madhan Neethiraj

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


Ship it!




Ship It!

- Madhan Neethiraj


On Oct. 16, 2017, 1:29 p.m., pratik pandey wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63029/
> ---
> 
> (Updated Oct. 16, 2017, 1:29 p.m.)
> 
> 
> Review request for atlas, keval bhatt, Madhan Neethiraj, Nixon Rodrigues, and 
> Sharmadha Sainath.
> 
> 
> Bugs: ATLAS-2212
> https://issues.apache.org/jira/browse/ATLAS-2212
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 1. Created a tag with int attribute.
> 2. Tried to associate the tag to an entity with tag attribute value as -1. 
> Unable to provide negative value.(i.e) minus sign is not accepted. 
> 3. Able to set negative value for int if value is changed using Up and Down 
> Arrow .
> 4. This behavior is not observed for short,byte,float,double attribute 
> values. Able to provide negative value directly for datatypes other than int.
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/js/utils/Overrides.js 4ffda57 
>   dashboardv2/public/js/views/tag/addTagModalView.js 423a92e 
> 
> 
> Diff: https://reviews.apache.org/r/63029/diff/1/
> 
> 
> Testing
> ---
> 
> I have tested with negative value is working as expected.
> 
> 
> Thanks,
> 
> pratik pandey
> 
>



[jira] [Updated] (ATLAS-2212) Regression : Unable to provide negative values directly for tag attributes of data type int.

2017-10-16 Thread pratik pandey (JIRA)

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

pratik pandey updated ATLAS-2212:
-
Attachment: ATLAS-2212.patch

> Regression : Unable to provide negative values directly for tag attributes of 
> data type int.
> 
>
> Key: ATLAS-2212
> URL: https://issues.apache.org/jira/browse/ATLAS-2212
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: pratik pandey
> Fix For: 1.0.0, 0.8.2
>
> Attachments: ATLAS-2212.patch
>
>
> 1. Created a tag with int attribute.
> 2. Tried to associate the tag to an entity with tag attribute value as -1. 
> Unable to provide negative value.(i.e) minus sign is not accepted. 
> 3. Able to set negative value for int if value is changed using Up and Down 
> Arrow .
> 4. This behavior is not observed for short,byte,float,double attribute 
> values. Able to provide negative value directly for datatypes other than int.



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


[jira] [Updated] (ATLAS-2212) Regression : Unable to provide negative values directly for tag attributes of data type int.

2017-10-16 Thread pratik pandey (JIRA)

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

pratik pandey updated ATLAS-2212:
-
Fix Version/s: 0.8.2
   1.0.0

> Regression : Unable to provide negative values directly for tag attributes of 
> data type int.
> 
>
> Key: ATLAS-2212
> URL: https://issues.apache.org/jira/browse/ATLAS-2212
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: pratik pandey
> Fix For: 1.0.0, 0.8.2
>
> Attachments: ATLAS-2212.patch
>
>
> 1. Created a tag with int attribute.
> 2. Tried to associate the tag to an entity with tag attribute value as -1. 
> Unable to provide negative value.(i.e) minus sign is not accepted. 
> 3. Able to set negative value for int if value is changed using Up and Down 
> Arrow .
> 4. This behavior is not observed for short,byte,float,double attribute 
> values. Able to provide negative value directly for datatypes other than int.



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


Review Request 63029: ATLAS-2212 : Regression : Unable to provide negative values directly for tag attributes of data type int.

2017-10-16 Thread pratik pandey

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

Review request for atlas, keval bhatt, Madhan Neethiraj, Nixon Rodrigues, and 
Sharmadha Sainath.


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


Repository: atlas


Description
---

1. Created a tag with int attribute.
2. Tried to associate the tag to an entity with tag attribute value as -1. 
Unable to provide negative value.(i.e) minus sign is not accepted. 
3. Able to set negative value for int if value is changed using Up and Down 
Arrow .
4. This behavior is not observed for short,byte,float,double attribute values. 
Able to provide negative value directly for datatypes other than int.


Diffs
-

  dashboardv2/public/js/utils/Overrides.js 4ffda57 
  dashboardv2/public/js/views/tag/addTagModalView.js 423a92e 


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


Testing
---

I have tested with negative value is working as expected.


Thanks,

pratik pandey



[jira] [Updated] (ATLAS-1095) Open connector framework

2017-10-16 Thread Mandy Chessell (JIRA)

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

Mandy Chessell updated ATLAS-1095:
--
Attachment: (was: OCF - 15th October 2017.patch)

> Open connector framework
> 
>
> Key: ATLAS-1095
> URL: https://issues.apache.org/jira/browse/ATLAS-1095
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 1.0.0
>Reporter: Stephanie Hazlewood
>Assignee: Mandy Chessell
>  Labels: VirtualDataConnector
> Attachments: OCF Javadoc.zip, Open Connector Framework - 20th June 
> 2017.doc, Open Connector Framework - 9th May 2017.doc
>
>
> Atlas provides a common approach to metadata management and governance across 
> all systems and data within an organization.  Today Atlas provides access to 
> metadata.   A connector provides access to a data source.  As connectors are 
> the proxy of all data, they can also be explicit providers of metadata.   
> This JIRA proposes an open connector framework to manage connectors that 
> provide access to both data and the metadata Atlas provides together through 
> a single connector interface.  
> This will help data tools to to better the exchange of information between 
> platforms. It also offers new opportunities for the consistent enforcement of 
> the governance policies and rules (e.g., rules of visibility).  Source 
> connector/connection metadata provides the nucleus around which all other 
> metadata describing the data builds.  



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


[jira] [Updated] (ATLAS-1095) Open connector framework

2017-10-16 Thread Mandy Chessell (JIRA)

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

Mandy Chessell updated ATLAS-1095:
--
Attachment: ATLAS-1095.patch

Regenerated patch from the command line rather than using intelliJ

> Open connector framework
> 
>
> Key: ATLAS-1095
> URL: https://issues.apache.org/jira/browse/ATLAS-1095
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 1.0.0
>Reporter: Stephanie Hazlewood
>Assignee: Mandy Chessell
>  Labels: VirtualDataConnector
> Attachments: ATLAS-1095.patch, OCF Javadoc.zip, Open Connector 
> Framework - 20th June 2017.doc, Open Connector Framework - 9th May 2017.doc
>
>
> Atlas provides a common approach to metadata management and governance across 
> all systems and data within an organization.  Today Atlas provides access to 
> metadata.   A connector provides access to a data source.  As connectors are 
> the proxy of all data, they can also be explicit providers of metadata.   
> This JIRA proposes an open connector framework to manage connectors that 
> provide access to both data and the metadata Atlas provides together through 
> a single connector interface.  
> This will help data tools to to better the exchange of information between 
> platforms. It also offers new opportunities for the consistent enforcement of 
> the governance policies and rules (e.g., rules of visibility).  Source 
> connector/connection metadata provides the nucleus around which all other 
> metadata describing the data builds.  



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


[jira] [Updated] (ATLAS-2212) Regression : Unable to provide negative values directly for tag attributes of data type int.

2017-10-16 Thread Sharmadha Sainath (JIRA)

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

Sharmadha Sainath updated ATLAS-2212:
-
Summary: Regression : Unable to provide negative values directly for tag 
attributes of data type int.  (was: Unable to provide negative values directly 
for tag attributes of data type int.)

> Regression : Unable to provide negative values directly for tag attributes of 
> data type int.
> 
>
> Key: ATLAS-2212
> URL: https://issues.apache.org/jira/browse/ATLAS-2212
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: pratik pandey
>
> 1. Created a tag with int attribute.
> 2. Tried to associate the tag to an entity with tag attribute value as -1. 
> Unable to provide negative value.(i.e) minus sign is not accepted. 
> 3. Able to set negative value for int if value is changed using Up and Down 
> Arrow .
> 4. This behavior is not observed for short,byte,float,double attribute 
> values. Able to provide negative value directly for datatypes other than int.



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


[jira] [Assigned] (ATLAS-2212) Unable to provide negative values directly for tag attributes of data type int.

2017-10-16 Thread pratik pandey (JIRA)

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

pratik pandey reassigned ATLAS-2212:


Assignee: pratik pandey  (was: Keval Bhatt)

> Unable to provide negative values directly for tag attributes of data type 
> int.
> ---
>
> Key: ATLAS-2212
> URL: https://issues.apache.org/jira/browse/ATLAS-2212
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: pratik pandey
>
> 1. Created a tag with int attribute.
> 2. Tried to associate the tag to an entity with tag attribute value as -1. 
> Unable to provide negative value.(i.e) minus sign is not accepted. 
> 3. Able to set negative value for int if value is changed using Up and Down 
> Arrow .
> 4. This behavior is not observed for short,byte,float,double attribute 
> values. Able to provide negative value directly for datatypes other than int.



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


[jira] [Created] (ATLAS-2212) Unable to provide negative values directly for tag attributes of data type int.

2017-10-16 Thread Sharmadha Sainath (JIRA)
Sharmadha Sainath created ATLAS-2212:


 Summary: Unable to provide negative values directly for tag 
attributes of data type int.
 Key: ATLAS-2212
 URL: https://issues.apache.org/jira/browse/ATLAS-2212
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


1. Created a tag with int attribute.
2. Tried to associate the tag to an entity with tag attribute value as -1. 
Unable to provide negative value.(i.e) minus sign is not accepted. 
3. Able to set negative value for int if value is changed using Up and Down 
Arrow .
4. This behavior is not observed for short,byte,float,double attribute values. 
Able to provide negative value directly for datatypes other than int.



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


[jira] [Assigned] (ATLAS-2212) Unable to provide negative values directly for tag attributes of data type int.

2017-10-16 Thread Sharmadha Sainath (JIRA)

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

Sharmadha Sainath reassigned ATLAS-2212:


Assignee: Keval Bhatt

> Unable to provide negative values directly for tag attributes of data type 
> int.
> ---
>
> Key: ATLAS-2212
> URL: https://issues.apache.org/jira/browse/ATLAS-2212
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>
> 1. Created a tag with int attribute.
> 2. Tried to associate the tag to an entity with tag attribute value as -1. 
> Unable to provide negative value.(i.e) minus sign is not accepted. 
> 3. Able to set negative value for int if value is changed using Up and Down 
> Arrow .
> 4. This behavior is not observed for short,byte,float,double attribute 
> values. Able to provide negative value directly for datatypes other than int.



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