date:20161216

[jira] [Created] (ATLAS-1396) [V2 API] GET v2/types/enumdef/guid/{guid} not working as expected

2016-12-16 Thread Vimal Sharma (JIRA)

Vimal Sharma created ATLAS-1396:
---

 Summary: [V2 API] GET v2/types/enumdef/guid/{guid}  not working as 
expected
 Key: ATLAS-1396
 URL: https://issues.apache.org/jira/browse/ATLAS-1396
 Project: Atlas
  Issue Type: Bug
Reporter: Vimal Sharma
Assignee: Vimal Sharma


POST  v2/types/enumdef
{
"name" : "creation_order1",
"typeVersion" : "1.1",
"elementDefs" : [
{
"ordinal" : 1,
"value" : "PRE"
},
{
"ordinal" : 2,
"value" : "POST"
},
{
"ordinal" : 3,
"value" : "UNKNOWN"
}
]
}

returns the response
{
  "category": "ENUM",
  "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
  "createTime": 1481885315377,
  "updateTime": 1481885315377,
  "version": 1,
  "name": "creation_order1",
  "description": "creation_order1",
  "typeVersion": "1.1",
  "elementDefs": [
{
  "value": "PRE",
  "ordinal": 1
},
{
  "value": "POST",
  "ordinal": 2
},
{
  "value": "UNKNOWN",
  "ordinal": 3
}
  ]
}

But GET v2/types/enumdef/guid/c5642d55-9f8e-45b1-b4a9-709c97b46233 returns
{
  "errorCode": "ATLAS4042E",
  "errorMessage": "Given type guid c5642d55-9f8e-45b1-b4a9-709c97b46233 was 
invalid"
}

GET v2/types/enumdef/name/creation_order1  returns
{
  "category": "ENUM",
  "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
  "createTime": 1481885315377,
  "updateTime": 1481885315377,
  "version": 1,
  "name": "creation_order1",
  "typeVersion": "1.1",
  "elementDefs": [
{
  "value": "PRE",
  "ordinal": 1
},
{
  "value": "POST",
  "ordinal": 2
},
{
  "value": "UNKNOWN",
  "ordinal": 3
}
  ]
}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1397) [V2 API] DELETE should return deleted type guid with proper message

2016-12-16 Thread Vimal Sharma (JIRA)

Vimal Sharma created ATLAS-1397:
---

 Summary: [V2 API] DELETE should return deleted type guid with 
proper message
 Key: ATLAS-1397
 URL: https://issues.apache.org/jira/browse/ATLAS-1397
 Project: Atlas
  Issue Type: Improvement
Reporter: Vimal Sharma
Assignee: Vimal Sharma


POST v2/types/enumdef
{
"name" : "creation_order1",
"typeVersion" : "1.1",
"elementDefs" : [
{ "ordinal" : 1, "value" : "PRE" }
,
{ "ordinal" : 2, "value" : "POST" }
,
{ "ordinal" : 3, "value" : "UNKNOWN" }
]
}
returns the response
{
"category": "ENUM",
"guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
"createTime": 1481885315377,
"updateTime": 1481885315377,
"version": 1,
"name": "creation_order1",
"description": "creation_order1",
"typeVersion": "1.1",
"elementDefs": [
{ "value": "PRE", "ordinal": 1 }
,
{ "value": "POST", "ordinal": 2 }
,
{ "value": "UNKNOWN", "ordinal": 3 }
]
}

DELETE v2/types/enumdef/name/creation_order1 is successful but doesn't return 
anything. DELETE request should return some response in the below format:

{
"result" : "SUCCESS/FAIL"
"guid" : "{guid}"
}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1398) POST request for Struct type accepts Enum type in request JSON

2016-12-16 Thread Vimal Sharma (JIRA)

Vimal Sharma created ATLAS-1398:
---

 Summary: POST request for Struct type accepts Enum type in request 
JSON
 Key: ATLAS-1398
 URL: https://issues.apache.org/jira/browse/ATLAS-1398
 Project: Atlas
  Issue Type: Improvement
Reporter: Vimal Sharma


POST  v2/types/structdef
{
"name" : "creation_order2",
"typeVersion" : "1.1",
"elementDefs" : [
{
"ordinal" : 1,
"value" : "PRE"
},
{
"ordinal" : 2,
"value" : "POST"
},
{
"ordinal" : 3,
"value" : "UNKNOWN"
}
]
}

return response
{
  "category": "STRUCT",
  "guid": "63d0755e-8e54-4f5f-9266-fa8d5df20969",
  "createTime": 1481886280574,
  "updateTime": 1481886280574,
  "version": 1,
  "name": "creation_order2",
  "description": "creation_order2",
  "typeVersion": "1.1",
  "attributeDefs": []
}

The response suggests that and empty Struct is created.The POST request should 
not create an empty Struct and should fail with the message "Invalid JSON"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 54806: ATLAS-1395 : Lineage improvement for tooltip

2016-12-16 Thread keval bhatt


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

(Updated Dec. 16, 2016, 11:31 a.m.)


Review request for atlas, Madhan Neethiraj, Mehul Parikh, Suma Shivaprasad, and 
Vimal Sharma.


Changes
---

Tooltip will be shown on hover of label also


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


Repository: atlas


Description
---

This patch containes Lineage tooltip improvement.

Format:

`` 

--
|  |
| |
||
--


``

Both name and typename will be center align inside tooltip


Diffs (updated)
-

  dashboardv2/public/js/views/graph/LineageLayoutView.js d16674e 

Diff: https://reviews.apache.org/r/54806/diff/


Testing
---

Tested with quickstart data


Thanks,

keval bhatt

[jira] [Created] (ATLAS-1399) [V2 API] PUT /v2/types/structdef/guid/{guid} fails while PUT /v2/types/structdef/name/{structGUID} suceeds

2016-12-16 Thread Vimal Sharma (JIRA)

Vimal Sharma created ATLAS-1399:
---

 Summary: [V2 API] PUT /v2/types/structdef/guid/{guid} fails while 
PUT /v2/types/structdef/name/{structGUID} suceeds
 Key: ATLAS-1399
 URL: https://issues.apache.org/jira/browse/ATLAS-1399
 Project: Atlas
  Issue Type: Improvement
Reporter: Vimal Sharma


For the below JSON
{
  "category": "STRUCT",
  "guid": "9527b5c2-49f7-4e25-bab0-a352d58fc2bf",
  "createTime": 1481887151201,
  "updateTime": 1481887819834,
  "version": 3,
  "name": "table_creation_order",
  "description": "table_creation_order",
  "typeVersion": "1.0",
  "attributeDefs": [
{
  "name": "order",
  "typeName": "int",
  "isOptional": false,
  "cardinality": "SINGLE",
  "valuesMinCount": 1,
  "valuesMaxCount": 1,
  "isUnique": false,
  "isIndexable": false
},
{
  "name": "tablename",
  "typeName": "string",
  "isOptional": false,
  "cardinality": "SINGLE",
  "valuesMinCount": 1,
  "valuesMaxCount": 1,
  "isUnique": false,
  "isIndexable": false
},
{
  "name": "before_tablename_guid",
  "typeName": "string",
  "isOptional": true,
  "cardinality": "SINGLE",
  "valuesMinCount": 0,
  "valuesMaxCount": 1,
  "isUnique": false,
  "isIndexable": false
},
{
  "name": "before_tablename_guid2",
  "typeName": "string",
  "isOptional": true,
  "cardinality": "SINGLE",
  "valuesMinCount": 0,
  "valuesMaxCount": 1,
  "isUnique": false,
  "isIndexable": false
}
  ]
}

PUT /v2/types/structdef/name/{structGUID} succeeds but 
PUT /v2/types/structdef/guid/9527b5c2-49f7-4e25-bab0-a352d58fc2bf fails with 
the below exception

2016-12-16 11:34:08,381 ERROR - [pool-2-thread-7 - 
2d2851fc-caf8-4460-a11e-facb60eeb223:] ~ graph rollback due to exception  
(GraphTransactionInterceptor:57)
java.lang.NullPointerException
at 
org.apache.atlas.repository.store.graph.v1.AtlasStructDefStoreV1.updateByGuid(AtlasStructDefStoreV1.java:235)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateStructDefByGuid(AtlasTypeDefGraphStore.java:283)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:50)
at 
org.apache.atlas.web.rest.TypesREST.updateStructDefByGuid(TypesREST.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)
at 
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)
at 
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)
at 
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)

[jira] [Updated] (ATLAS-1399) [V2 API] PUT /v2/types/structdef/guid/{guid} fails while PUT /v2/types/structdef/name/{structGUID} suceeds

2016-12-16 Thread Vimal Sharma (JIRA)


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

Vimal Sharma updated ATLAS-1399:

Issue Type: Bug  (was: Improvement)

> [V2 API] PUT /v2/types/structdef/guid/{guid} fails while PUT 
> /v2/types/structdef/name/{structGUID} suceeds
> --
>
> Key: ATLAS-1399
> URL: https://issues.apache.org/jira/browse/ATLAS-1399
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>
> For the below JSON
> {
>   "category": "STRUCT",
>   "guid": "9527b5c2-49f7-4e25-bab0-a352d58fc2bf",
>   "createTime": 1481887151201,
>   "updateTime": 1481887819834,
>   "version": 3,
>   "name": "table_creation_order",
>   "description": "table_creation_order",
>   "typeVersion": "1.0",
>   "attributeDefs": [
> {
>   "name": "order",
>   "typeName": "int",
>   "isOptional": false,
>   "cardinality": "SINGLE",
>   "valuesMinCount": 1,
>   "valuesMaxCount": 1,
>   "isUnique": false,
>   "isIndexable": false
> },
> {
>   "name": "tablename",
>   "typeName": "string",
>   "isOptional": false,
>   "cardinality": "SINGLE",
>   "valuesMinCount": 1,
>   "valuesMaxCount": 1,
>   "isUnique": false,
>   "isIndexable": false
> },
> {
>   "name": "before_tablename_guid",
>   "typeName": "string",
>   "isOptional": true,
>   "cardinality": "SINGLE",
>   "valuesMinCount": 0,
>   "valuesMaxCount": 1,
>   "isUnique": false,
>   "isIndexable": false
> },
> {
>   "name": "before_tablename_guid2",
>   "typeName": "string",
>   "isOptional": true,
>   "cardinality": "SINGLE",
>   "valuesMinCount": 0,
>   "valuesMaxCount": 1,
>   "isUnique": false,
>   "isIndexable": false
> }
>   ]
> }
> PUT /v2/types/structdef/name/{structGUID} succeeds but 
> PUT /v2/types/structdef/guid/9527b5c2-49f7-4e25-bab0-a352d58fc2bf fails with 
> the below exception
> 2016-12-16 11:34:08,381 ERROR - [pool-2-thread-7 - 
> 2d2851fc-caf8-4460-a11e-facb60eeb223:] ~ graph rollback due to exception  
> (GraphTransactionInterceptor:57)
> java.lang.NullPointerException
>   at 
> org.apache.atlas.repository.store.graph.v1.AtlasStructDefStoreV1.updateByGuid(AtlasStructDefStoreV1.java:235)
>   at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateStructDefByGuid(AtlasTypeDefGraphStore.java:283)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:50)
>   at 
> org.apache.atlas.web.rest.TypesREST.updateStructDefByGuid(TypesREST.java:197)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> com.google.inject.servlet.ServletDefinition.doServiceImp

[jira] [Updated] (ATLAS-1395) Lineage improvement for tooltip

2016-12-16 Thread Keval Bhatt (JIRA)


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

Keval Bhatt updated ATLAS-1395:
---
Attachment: ATLAS-1395.1.patch

> Lineage improvement for tooltip
> ---
>
> Key: ATLAS-1395
> URL: https://issues.apache.org/jira/browse/ATLAS-1395
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Attachments: ATLAS-1395.1.patch, ATLAS-1395.patch
>
>
> This patch containes Lineage tooltip improvement.
> Format:
> {noFormat}
> 
> ||
> |   |
> |  |
> 
> {noFormat}
> Both name and typename will be center align inside tooltip



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1193) UI : UI to create entities

2016-12-16 Thread Kalyani Kashikar (JIRA)


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

Kalyani Kashikar updated ATLAS-1193:

Attachment: ATLAS-1193.7.patch

> UI : UI to create entities
> --
>
> Key: ATLAS-1193
> URL: https://issues.apache.org/jira/browse/ATLAS-1193
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1193.1.patch, ATLAS-1193.2.patch, 
> ATLAS-1193.3.patch, ATLAS-1193.4.patch, ATLAS-1193.5.patch, 
> ATLAS-1193.6.patch, ATLAS-1193.7.patch, ATLAS-1193.patch
>
>
> * New UI for create entities of different types. 
>   The  attributes for entiry will be loaded from supertype and type api.
>   The entity will be created by existing *api/atlas/entities*  api



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1193) UI : UI to create entities

2016-12-16 Thread Kalyani Kashikar (JIRA)


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

Kalyani Kashikar commented on ATLAS-1193:
-

I have updated the patch ATLAS-1193.7.patch with fix for the issue of list of 
values getting appended to map datatype,To fix this issue I have 
provided textbox for editing map dataType values.


> UI : UI to create entities
> --
>
> Key: ATLAS-1193
> URL: https://issues.apache.org/jira/browse/ATLAS-1193
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1193.1.patch, ATLAS-1193.2.patch, 
> ATLAS-1193.3.patch, ATLAS-1193.4.patch, ATLAS-1193.5.patch, 
> ATLAS-1193.6.patch, ATLAS-1193.7.patch, ATLAS-1193.patch
>
>
> * New UI for create entities of different types. 
>   The  attributes for entiry will be loaded from supertype and type api.
>   The entity will be created by existing *api/atlas/entities*  api



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1371) ATLAS UI : Allow choosing of data-type for attributes in create/edit tag dialog.

2016-12-16 Thread Kalyani Kashikar (JIRA)


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

Kalyani Kashikar updated ATLAS-1371:

Attachment: ATLAS-1371.patch

This patch is dependent on ATLAS-1193.7.patch


> ATLAS UI : Allow choosing of data-type for attributes in create/edit tag 
> dialog.
> 
>
> Key: ATLAS-1371
> URL: https://issues.apache.org/jira/browse/ATLAS-1371
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1371.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 54166: ALTAS-1193: UI : UI to create entities

2016-12-16 Thread Kalyani Kashikar


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

(Updated Dec. 16, 2016, 1:16 p.m.)


Review request for atlas, keval bhatt, Madhan Neethiraj, and Suma Shivaprasad.


Changes
---

I have updated the patch ATLAS-1193.7.patch with fix for the issue of list of 
values getting appended to map datatype,To fix this issue I have 
provided textbox for editing map dataType values.


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


Repository: atlas


Description
---

* New UI for create/edit entities of different types.
* New UI for create/edit entity is integrated with new v2 api.


Diffs (updated)
-

  dashboardv2/gruntfile.js a252f1d 
  dashboardv2/public/css/scss/form.scss e17b7bb 
  dashboardv2/public/css/scss/override.scss 2db5568 
  dashboardv2/public/css/scss/search.scss 24b2212 
  dashboardv2/public/css/scss/tag.scss fa194fa 
  dashboardv2/public/index.html 04edcee 
  dashboardv2/public/js/collection/VEntityList.js bfcbe99 
  dashboardv2/public/js/collection/VSearchList.js 640be40 
  dashboardv2/public/js/external_lib/datetimepicker/bootstrap-datetimepicker.js 
PRE-CREATION 
  
dashboardv2/public/js/external_lib/datetimepicker/bootstrap-datetimepicker.min.css
 PRE-CREATION 
  dashboardv2/public/js/main.js 772d3d4 
  dashboardv2/public/js/models/VEntity.js 4347b62 
  dashboardv2/public/js/templates/detail_page/DetailPageLayoutView_tmpl.html 
f34bcea 
  dashboardv2/public/js/templates/entity/CreateEntityLayoutView_tmpl.html 
PRE-CREATION 
  dashboardv2/public/js/templates/search/SearchLayoutView_tmpl.html db31046 
  dashboardv2/public/js/utils/UrlLinks.js a5288be 
  dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js b2d2c7b 
  dashboardv2/public/js/views/entity/CreateEntityLayoutView.js PRE-CREATION 
  dashboardv2/public/js/views/search/SearchLayoutView.js d652aa4 
  dashboardv2/public/js/views/search/SearchResultLayoutView.js 0a37834 

Diff: https://reviews.apache.org/r/54166/diff/


Testing
---

* Created entities for all the entity type and also edited with edit UI.
* Verified with new api.


Thanks,

Kalyani Kashikar

Re: Review Request 54806: ATLAS-1395 : Lineage improvement for tooltip

2016-12-16 Thread Madhan Neethiraj


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


Ship it!




Ship It!

- Madhan Neethiraj


On Dec. 16, 2016, 11:31 a.m., keval bhatt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54806/
> ---
> 
> (Updated Dec. 16, 2016, 11:31 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Mehul Parikh, Suma Shivaprasad, 
> and Vimal Sharma.
> 
> 
> Bugs: ATLAS-1395
> https://issues.apache.org/jira/browse/ATLAS-1395
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch containes Lineage tooltip improvement.
> 
> Format:
> 
> `` 
> 
> --
> |  |
> | |
> ||
> --
> 
> 
> ``
> 
> Both name and typename will be center align inside tooltip
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/js/views/graph/LineageLayoutView.js d16674e 
> 
> Diff: https://reviews.apache.org/r/54806/diff/
> 
> 
> Testing
> ---
> 
> Tested with quickstart data
> 
> 
> Thanks,
> 
> keval bhatt
> 
>

Re: Review Request 54166: ALTAS-1193: UI : UI to create entities

2016-12-16 Thread Madhan Neethiraj


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


Ship it!




Ship It!

- Madhan Neethiraj


On Dec. 16, 2016, 1:16 p.m., Kalyani Kashikar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54166/
> ---
> 
> (Updated Dec. 16, 2016, 1:16 p.m.)
> 
> 
> Review request for atlas, keval bhatt, Madhan Neethiraj, and Suma Shivaprasad.
> 
> 
> Bugs: ATLAS-1193
> https://issues.apache.org/jira/browse/ATLAS-1193
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> * New UI for create/edit entities of different types.
> * New UI for create/edit entity is integrated with new v2 api.
> 
> 
> Diffs
> -
> 
>   dashboardv2/gruntfile.js a252f1d 
>   dashboardv2/public/css/scss/form.scss e17b7bb 
>   dashboardv2/public/css/scss/override.scss 2db5568 
>   dashboardv2/public/css/scss/search.scss 24b2212 
>   dashboardv2/public/css/scss/tag.scss fa194fa 
>   dashboardv2/public/index.html 04edcee 
>   dashboardv2/public/js/collection/VEntityList.js bfcbe99 
>   dashboardv2/public/js/collection/VSearchList.js 640be40 
>   
> dashboardv2/public/js/external_lib/datetimepicker/bootstrap-datetimepicker.js 
> PRE-CREATION 
>   
> dashboardv2/public/js/external_lib/datetimepicker/bootstrap-datetimepicker.min.css
>  PRE-CREATION 
>   dashboardv2/public/js/main.js 772d3d4 
>   dashboardv2/public/js/models/VEntity.js 4347b62 
>   dashboardv2/public/js/templates/detail_page/DetailPageLayoutView_tmpl.html 
> f34bcea 
>   dashboardv2/public/js/templates/entity/CreateEntityLayoutView_tmpl.html 
> PRE-CREATION 
>   dashboardv2/public/js/templates/search/SearchLayoutView_tmpl.html db31046 
>   dashboardv2/public/js/utils/UrlLinks.js a5288be 
>   dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js b2d2c7b 
>   dashboardv2/public/js/views/entity/CreateEntityLayoutView.js PRE-CREATION 
>   dashboardv2/public/js/views/search/SearchLayoutView.js d652aa4 
>   dashboardv2/public/js/views/search/SearchResultLayoutView.js 0a37834 
> 
> Diff: https://reviews.apache.org/r/54166/diff/
> 
> 
> Testing
> ---
> 
> * Created entities for all the entity type and also edited with edit UI.
> * Verified with new api.
> 
> 
> Thanks,
> 
> Kalyani Kashikar
> 
>

[jira] [Commented] (ATLAS-1371) ATLAS UI : Allow choosing of data-type for attributes in create/edit tag dialog.

2016-12-16 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj commented on ATLAS-1371:
-

+1 for the patch. Thanks [~Kalyanikashikar].

> ATLAS UI : Allow choosing of data-type for attributes in create/edit tag 
> dialog.
> 
>
> Key: ATLAS-1371
> URL: https://issues.apache.org/jira/browse/ATLAS-1371
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1371.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is back to normal : apache-atlas-nightly #522

2016-12-16 Thread Apache Jenkins Server

See

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

2016-12-16 Thread Apache Jenkins Server

See 

Changes:

[madhan] ATLAS-1371: create/edit tag dialog to allow choosing of data-type for

--
[...truncated 6838 lines...]
127.0.0.1 - - [16/Dec/2016:16:35:56 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=TRUNCATETABLE-%3E:default.table6ybfpky7ri@primary:1481906151000
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:35:56 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=TRUNCATETABLE-%3E:default.table6ybfpky7ri@primary:1481906151000
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:35:56 +] "GET 
/api/atlas/entities/3d1cf48d-76df-4b7a-86c7-cdc7a43c4698 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:35:56 +] "GET 
/api/atlas/entities/d0974b15-ab81-4b85-9aa8-550009f9385a HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:35:56 +] "GET 
/api/atlas/lineage/hive/table/default.table6ybfpky7ri@primary/inputs/graph 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:01 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.table2es0mta2lr@primary:1481906159000-%3E:PATH_WRITE
 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.table2es0mta2lr@primary:1481906159000-%3E:PATH_WRITE
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.table2es0mta2lr@primary:1481906159000-%3E:PATH_WRITE
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities/63b3565d-e111-4623-90b7-dc7b9c46a6c6 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities/64e267ed-6456-4f6e-829b-41d22e13fa72 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities/af469cb1-dfc0-467c-bd65-092e6a1620f9 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities?type=hdfs_path&property=qualifiedName&value=p
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities?type=hdfs_path&property=qualifiedName&value=p
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities/af469cb1-dfc0-467c-bd65-092e6a1620f9 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities?type=hive_table&property=qualifiedName&value=default.table2es0mta2lr@primary
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities?type=hive_table&property=qualifiedName&value=default.table2es0mta2lr@primary
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:06 +] "GET 
/api/atlas/entities/64e267ed-6456-4f6e-829b-41d22e13fa72 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:08 +] "GET 
/api/atlas/entities?type=hive_table&property=qualifiedName&value=default.table2es0mta2lr@primary
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:08 +] "GET 
/api/atlas/entities?type=hive_table&property=qualifiedName&value=default.table2es0mta2lr@primary
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:08 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.table2es0mta2lr@primary:1481906159000-%3E:PATH_WRITE
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:09 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.table2es0mta2lr@primary:1481906159000-%3E:PATH_WRITE
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:09 +] "GET 
/api/atlas/entities/63b3565d-e111-4623-90b7-dc7b9c46a6c6 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:09 +] "GET 
/api/atlas/entities/64e267ed-6456-4f6e-829b-41d22e13fa72 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:09 +] "GET 
/api/atlas/entities/af469cb1-dfc0-467c-bd65-092e6a1620f9 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:09 +] "GET 
/api/atlas/entities?type=hdfs_path&property=qualifiedName&value=p
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [16/Dec/2016:16:36:09 +] "GET 
/api/atlas/entities?type=hdfs_path&property=qualifiedName&value=p

[jira] [Commented] (ATLAS-1384) Can you please upgrade to scala 2.11.7

2016-12-16 Thread John Mattucci (JIRA)


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

John Mattucci commented on ATLAS-1384:
--

Sorry, my bad. I was sure both 0.7 & 0.8 were using scava version 2.10. Any 
plans to have 0.7 use 2.11?

> Can you please upgrade to scala 2.11.7
> --
>
> Key: ATLAS-1384
> URL: https://issues.apache.org/jira/browse/ATLAS-1384
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: John Mattucci
>
> Can you please upgrade to scala version 2.11.7



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-1384) Can you please upgrade to scala 2.11.7

2016-12-16 Thread John Mattucci (JIRA)


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

John Mattucci edited comment on ATLAS-1384 at 12/16/16 6:59 PM:


Sorry, my bad. I was sure both 0.7 & 0.8 were using scala version 2.10. Any 
plans to have 0.7 use 2.11?


was (Author: jmattucci):
Sorry, my bad. I was sure both 0.7 & 0.8 were using scava version 2.10. Any 
plans to have 0.7 use 2.11?

> Can you please upgrade to scala 2.11.7
> --
>
> Key: ATLAS-1384
> URL: https://issues.apache.org/jira/browse/ATLAS-1384
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: John Mattucci
>
> Can you please upgrade to scala version 2.11.7



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1388) Cache entities that are created/updated

2016-12-16 Thread Jeffrey Hagelberg (JIRA)


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

Jeffrey Hagelberg commented on ATLAS-1388:
--

[~apoorva_sharma] - We'll take a look at that when we merge these changes in.  
Based on a quick look, though, it seems that caches types, not entities.  It 
seems like entity caching should be kept separate from type caching.

> Cache entities that are created/updated
> ---
>
> Key: ATLAS-1388
> URL: https://issues.apache.org/jira/browse/ATLAS-1388
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Jeffrey Hagelberg
>
> - Cache created entities in RequestContext when they are created.
> - Update/refactor DefaultMetadataService.loadEntities() to use the cached 
> created entities.
> - Use the cache in the following places:
> ** FullTextMapper
> ** DefaultMetadataService.onEntitiesAdded - check cache before calling 
> DefaultMetadataService.loadEntities
> ** DefaultMetadataService.onEntitiesUpdated - check cache before calling 
> DefaultMetadataService.loadEntities 
> ** EntityResource.getEntityDefinition - check cache before calling 
> DefaultMetadataService.getEntityDefinition
> ** EntityResource.getResponse - check cache before calling 
> DefaultMetadataService.getEntityDefinition



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-1389) Ping REST API entrypoint

2016-12-16 Thread Jeffrey Hagelberg (JIRA)


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

Jeffrey Hagelberg edited comment on ATLAS-1389 at 12/16/16 8:14 PM:


[~yhemanth] - The admin/status API did not exist when we implemented this.  It 
probably makes sense for the logic to become part of that endpoint.  Basically, 
the additional information that it provides is an estimate of the round trip 
time to the backend database.  It also validates that a trivial gremlin query 
can be executed successfully.  It takes a parameter that specifies the number 
of pings to do.  Let's discuss this when we are ready to start working on this 
JIRA.


was (Author: jnhagelb):
[~yhemanth] - The admin/status API did not exist when we implemented this.  It 
probably makes sense for the logic to become part of that endpoint.  Basically, 
the additional information that it provides is an estimate of the round trip 
time to the backend database.  It takes a parameter that specifies the number 
of pings to do.  Let's discuss this when we are ready to start working on this 
JIRA.

> Ping REST API entrypoint
> 
>
> Key: ATLAS-1389
> URL: https://issues.apache.org/jira/browse/ATLAS-1389
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: Jeffrey Hagelberg
>
> Provide a lightweight ping API to allow clients to check status of Atlas 
> server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1389) Ping REST API entrypoint

2016-12-16 Thread Jeffrey Hagelberg (JIRA)


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

Jeffrey Hagelberg commented on ATLAS-1389:
--

[~yhemanth] - The admin/status API did not exist when we implemented this.  It 
probably makes sense for the logic to become part of that endpoint.  Basically, 
the additional information that it provides is an estimate of the round trip 
time to the backend database.  It takes a parameter that specifies the number 
of pings to do.  Let's discuss this when we are ready to start working on this 
JIRA.

> Ping REST API entrypoint
> 
>
> Key: ATLAS-1389
> URL: https://issues.apache.org/jira/browse/ATLAS-1389
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: Jeffrey Hagelberg
>
> Provide a lightweight ping API to allow clients to check status of Atlas 
> server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1298) UI never finishes loading

2016-12-16 Thread Russell Anderson (JIRA)


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

Russell Anderson commented on ATLAS-1298:
-



*** THIS IS EXACTLY THE BEHAVIOR I AM SEEING *** I have Apache Atlas .7rc2

Question : In order to fix my Atlas .7rc2 build - Am i required to pull the
changes myself and rebuild ?

Thank you in advance,

Russ.


- Forwarded by Russell Anderson/Worcester/IBM on 12/16/2016 03:33 PM
-

From:   "Keval Bhatt (JIRA)" 
To: dev@atlas.incubator.apache.org
Date:   11/17/2016 01:57 AM
Subject:[jira] [Commented] (ATLAS-1298) UI never finishes loading




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

Keval Bhatt commented on ATLAS-1298:


Hi [~vanaepi]
Recently Atlas UI was not loading after fresh build due to
jquery-asBreadcrumbs plugin changes and this is fixed on master
( [ATLAS-1199 | https://issues.apache.org/jira/browse/ATLAS-1199] ) but the
issue is open for 0.7.

[Please checkout the latest code from master |
https://github.com/apache/incubator-atlas ]


script but when I go to the UI, I only get the login screen, followed by
the two-tone background and a "loading circle" which never completes
loading. There are no errors in application.log.
the host. I am querying the API from my browser on the host machine, so not
from inside the docker container. It works with both localhost and the
internal docker ip.
works just fine but "localhost:21000" suffers from the same issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)




> UI never finishes loading
> -
>
> Key: ATLAS-1298
> URL: https://issues.apache.org/jira/browse/ATLAS-1298
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
> Environment: Atlas 0.7 - Profile Berkeley/ElasticSearch
>Reporter: PJ Van Aeken
>
> The REST API  works fine, and I can see the data from the quickstart script 
> but when I go to the UI, I only get the login screen, followed by the 
> two-tone background and a "loading circle" which never completes loading. 
> There are no errors in application.log.
> Note: I am running inside a docker container but port 21000 is exposed to the 
> host. I am querying the API from my browser on the host machine, so not from 
> inside the docker container. It works with both localhost and the internal 
> docker ip.
> Any help debugging/fixing this would be greatly appreciated.
> *EDIT:* Running the master branch outside of docker, "mylaptopname:21000" 
> works just fine but "localhost:21000" suffers from the same issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1400) Fix Broken Link on Introduction Page for User Docs

2016-12-16 Thread Michael Aro (JIRA)

Michael Aro created ATLAS-1400:
--

 Summary: Fix Broken Link on Introduction Page for User Docs
 Key: ATLAS-1400
 URL: https://issues.apache.org/jira/browse/ATLAS-1400
 Project: Atlas
  Issue Type: Bug
Reporter: Michael Aro






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ATLAS-1367) High Availability Regression : After adding another instance of Atlas server, Atlas servers on both the hosts are PASSIVE

2016-12-16 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj reassigned ATLAS-1367:
---

Assignee: Madhan Neethiraj

> High Availability Regression : After adding another instance of Atlas server, 
> Atlas servers on both the hosts are PASSIVE
> -
>
> Key: ATLAS-1367
> URL: https://issues.apache.org/jira/browse/ATLAS-1367
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
>Priority: Blocker
>
> Atlas running on host1:21000 had ACTIVE status.
> Stopped Atlas and added another host host2. 
> Started both the hosts. Both the hosts /api/atlas/admin/status are in PASSIVE 
> state. 
> Follwing stack trace is found in logs pf both the hosts :
> Error getting active server address (ActiveInstanceState:122)
> org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = 
> NoNode for /apache_atlas/active_server_info
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:111)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1155)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$4.call(GetDataBuilderImpl.java:310)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$4.call(GetDataBuilderImpl.java:299)
>   at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl.pathInForeground(GetDataBuilderImpl.java:295)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl.forPath(GetDataBuilderImpl.java:287)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl.forPath(GetDataBuilderImpl.java:34)
>   at 
> org.apache.atlas.web.service.ActiveInstanceState.getActiveServerAddress(ActiveInstanceState.java:119)
>   at 
> org.apache.atlas.web.filters.ActiveServerFilter.doFilter(ActiveServerFilter.java:93)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)
>   at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>   at 
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:186)
>   at 
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
>   at 
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
>   at 
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
>   at org.eclipse.jetty.server.Server.handle(Server.java:499)
>   at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
>   at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
>   at 
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> 2016-12-12 09:02:12,908 ERROR - [pool-2-thread-9 - 
> a4f7401a-d568-4ff0-9be3-f511ed80822e:] ~ Could not retrieve active server 
> address as it is null.

Review Request 54824: ATLAS-1367: fix to use correct version of curator-client library

2016-12-16 Thread Madhan Neethiraj


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

Review request for atlas.


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


Repository: atlas


Description
---

Out of 3 curator libraries, curator-client was from 2.7.1, while 
curator-recipes & curator-framework were from 2.11.0. This caused Atlas server 
to fail in creating znode /apache_atlas - which resulted in all Atlas 
instances, in HA mode, to remain in PASSIVE mode.


Diffs
-

  pom.xml bdfd785 
  webapp/pom.xml 09701e1 
  webapp/src/main/java/org/apache/atlas/web/setup/SetupSteps.java 65c88fe 

Diff: https://reviews.apache.org/r/54824/diff/


Testing
---

Verified that with use of curator-client 2.11.0 version, Atlas was able to 
create znode /apache_atlas and move to ACTIVE mode.


Thanks,

Madhan Neethiraj

[jira] [Updated] (ATLAS-1367) High Availability Regression : After adding another instance of Atlas server, Atlas servers on both the hosts are PASSIVE

2016-12-16 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-1367:

Attachment: ATLAS-1367.patch

Patch in review board: https://reviews.apache.org/r/54824/

> High Availability Regression : After adding another instance of Atlas server, 
> Atlas servers on both the hosts are PASSIVE
> -
>
> Key: ATLAS-1367
> URL: https://issues.apache.org/jira/browse/ATLAS-1367
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
>Priority: Blocker
> Attachments: ATLAS-1367.patch
>
>
> Atlas running on host1:21000 had ACTIVE status.
> Stopped Atlas and added another host host2. 
> Started both the hosts. Both the hosts /api/atlas/admin/status are in PASSIVE 
> state. 
> Follwing stack trace is found in logs pf both the hosts :
> Error getting active server address (ActiveInstanceState:122)
> org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = 
> NoNode for /apache_atlas/active_server_info
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:111)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1155)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$4.call(GetDataBuilderImpl.java:310)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$4.call(GetDataBuilderImpl.java:299)
>   at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl.pathInForeground(GetDataBuilderImpl.java:295)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl.forPath(GetDataBuilderImpl.java:287)
>   at 
> org.apache.curator.framework.imps.GetDataBuilderImpl.forPath(GetDataBuilderImpl.java:34)
>   at 
> org.apache.atlas.web.service.ActiveInstanceState.getActiveServerAddress(ActiveInstanceState.java:119)
>   at 
> org.apache.atlas.web.filters.ActiveServerFilter.doFilter(ActiveServerFilter.java:93)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)
>   at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>   at 
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:186)
>   at 
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
>   at 
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
>   at 
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
>   at org.eclipse.jetty.server.Server.handle(Server.java:499)
>   at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
>   at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
>   at 
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> 2016-12-12 09:02:12,908 ERROR - [pool-2-thread-9 - 
> a4

Re: Review Request 54824: ATLAS-1367: fix to use correct version of curator-client library

2016-12-16 Thread Suma Shivaprasad


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


Ship it!




Ship It!

- Suma Shivaprasad


On Dec. 16, 2016, 10:56 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54824/
> ---
> 
> (Updated Dec. 16, 2016, 10:56 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-1367
> https://issues.apache.org/jira/browse/ATLAS-1367
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Out of 3 curator libraries, curator-client was from 2.7.1, while 
> curator-recipes & curator-framework were from 2.11.0. This caused Atlas 
> server to fail in creating znode /apache_atlas - which resulted in all Atlas 
> instances, in HA mode, to remain in PASSIVE mode.
> 
> 
> Diffs
> -
> 
>   pom.xml bdfd785 
>   webapp/pom.xml 09701e1 
>   webapp/src/main/java/org/apache/atlas/web/setup/SetupSteps.java 65c88fe 
> 
> Diff: https://reviews.apache.org/r/54824/diff/
> 
> 
> Testing
> ---
> 
> Verified that with use of curator-client 2.11.0 version, Atlas was able to 
> create znode /apache_atlas and move to ACTIVE mode.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Jenkins build is back to normal : apache-atlas-nightly #524

2016-12-16 Thread Apache Jenkins Server

See

[jira] [Commented] (ATLAS-1277) Add feather use 'order by ' in the DSL search

2016-12-16 Thread Qiang Zhang (JIRA)


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

Qiang Zhang commented on ATLAS-1277:


I have removed The tab space and ATLAS-1277-2.patch is the new patch

> Add  feather use 'order by ' in the DSL search 
> ---
>
> Key: ATLAS-1277
> URL: https://issues.apache.org/jira/browse/ATLAS-1277
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.8-incubating
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1277-2.patch
>
>
> in the Search using DSL,sort with 'orderby' ,but with :'order by ' is  a more 
> customary way ,so consider add the 'order by '  is more desirable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1396) [V2 API] GET v2/types/enumdef/guid/{guid} not working as expected

[jira] [Created] (ATLAS-1397) [V2 API] DELETE should return deleted type guid with proper message

[jira] [Created] (ATLAS-1398) POST request for Struct type accepts Enum type in request JSON

Re: Review Request 54806: ATLAS-1395 : Lineage improvement for tooltip

[jira] [Created] (ATLAS-1399) [V2 API] PUT /v2/types/structdef/guid/{guid} fails while PUT /v2/types/structdef/name/{structGUID} suceeds

[jira] [Updated] (ATLAS-1399) [V2 API] PUT /v2/types/structdef/guid/{guid} fails while PUT /v2/types/structdef/name/{structGUID} suceeds

[jira] [Updated] (ATLAS-1395) Lineage improvement for tooltip

[jira] [Updated] (ATLAS-1193) UI : UI to create entities

[jira] [Commented] (ATLAS-1193) UI : UI to create entities

[jira] [Updated] (ATLAS-1371) ATLAS UI : Allow choosing of data-type for attributes in create/edit tag dialog.

Re: Review Request 54166: ALTAS-1193: UI : UI to create entities

Re: Review Request 54806: ATLAS-1395 : Lineage improvement for tooltip

Re: Review Request 54166: ALTAS-1193: UI : UI to create entities

[jira] [Commented] (ATLAS-1371) ATLAS UI : Allow choosing of data-type for attributes in create/edit tag dialog.

Jenkins build is back to normal : apache-atlas-nightly #522

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

[jira] [Commented] (ATLAS-1384) Can you please upgrade to scala 2.11.7

[jira] [Comment Edited] (ATLAS-1384) Can you please upgrade to scala 2.11.7

[jira] [Commented] (ATLAS-1388) Cache entities that are created/updated

[jira] [Comment Edited] (ATLAS-1389) Ping REST API entrypoint

[jira] [Commented] (ATLAS-1389) Ping REST API entrypoint

[jira] [Commented] (ATLAS-1298) UI never finishes loading

[jira] [Created] (ATLAS-1400) Fix Broken Link on Introduction Page for User Docs

[jira] [Assigned] (ATLAS-1367) High Availability Regression : After adding another instance of Atlas server, Atlas servers on both the hosts are PASSIVE

Review Request 54824: ATLAS-1367: fix to use correct version of curator-client library

[jira] [Updated] (ATLAS-1367) High Availability Regression : After adding another instance of Atlas server, Atlas servers on both the hosts are PASSIVE

Re: Review Request 54824: ATLAS-1367: fix to use correct version of curator-client library

Jenkins build is back to normal : apache-atlas-nightly #524

[jira] [Commented] (ATLAS-1277) Add feather use 'order by ' in the DSL search

29 matches

Site Navigation

Mail list logo

Footer information