[jira] [Updated] (ATLAS-1892) Implement logic to create relationship attributes in AtlasEntityType

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1892:

Affects Version/s: (was: trunk)

> Implement logic to create relationship attributes in AtlasEntityType
> 
>
> Key: ATLAS-1892
> URL: https://issues.apache.org/jira/browse/ATLAS-1892
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1856.4.patch
>
>
> When a new relationshipDef is created, relation attributes needs to be 
> populated in AtlasEntityType during resolveReference stage.
> This JIRA also adds UT and IT and addresses review comments in 
> https://reviews.apache.org/r/59769/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1892) Implement logic to create relationship attributes in AtlasEntityType

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1892:

Fix Version/s: 1.0.0

> Implement logic to create relationship attributes in AtlasEntityType
> 
>
> Key: ATLAS-1892
> URL: https://issues.apache.org/jira/browse/ATLAS-1892
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: trunk, 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1856.4.patch
>
>
> When a new relationshipDef is created, relation attributes needs to be 
> populated in AtlasEntityType during resolveReference stage.
> This JIRA also adds UT and IT and addresses review comments in 
> https://reviews.apache.org/r/59769/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1894) UI : Search using entity and trait attributes

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1894:

Fix Version/s: 0.8.1
   1.0.0
  Component/s: atlas-webui

> UI : Search using entity and trait attributes
> -
>
> Key: ATLAS-1894
> URL: https://issues.apache.org/jira/browse/ATLAS-1894
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-1894.1.patch, ATLAS-1894.2.patch, 
> ATLAS-1894.3.patch, ATLAS-1894.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1897:

Fix Version/s: 0.8.1
   1.0.0
  Component/s: atlas-webui

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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1899) A correction identified during ATLAS-1891 review ended up not getting committed.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1899:

Fix Version/s: 1.0.0
  Component/s:  atlas-core

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/617bc25e

> A correction identified during ATLAS-1891 review ended up not getting 
> committed. 
> -
>
> Key: ATLAS-1899
> URL: https://issues.apache.org/jira/browse/ATLAS-1899
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Fix For: 1.0.0
>
>
> A correction identified during ATLAS-1891 ended up not getting committed. The 
> existing logic is 
> valid but the code could be cleaner. I am submitting the cleaner version of 
> the code as I have tested it



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1788) UI : Wildcard search with "?" throws exception in basic search

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1788:

Fix Version/s: 0.8.1
   1.0.0

> UI : Wildcard search with "?" throws exception in basic search
> --
>
> Key: ATLAS-1788
> URL: https://issues.apache.org/jira/browse/ATLAS-1788
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: trunk, 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: wildcard_search.txt
>
>
> Wildcard search with "?" throws 500 internal error.
> Example :
> Basic search :
> type name : kafka_topic
> query : kakfa_topic_iAEz?
> throws 500 Internal server error .
> The corresponding query fired is
> {code}
> http://172.27.19.74:21000/api/atlas/v2/search?limit=25=kakfa_topic_iAEz
> {code}
> if query is "kafka_topic_?AEzb"
> corresponding query fired is :
> {code}
> http://172.27.19.74:21000/api/atlas/v2/search?limit=25=kafka_topic_
> {code}
> Note : content after "?" is ignored and query is not formed correctly (basic 
> keyword is missed)
> The following curl command runs fine returns 200 Ok with correct results.
> {code}
> curl -u admin:admin -X GET 
> "http://172.27.19.74:21000/api/atlas/v2/search/basic?limit=25=true=kakfa_topic_iAEz?=kafka_topic;
> {code}
> Attached the WebApplication exception thrown while making the query.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1778) Incorrect error code returned in V2 APIs when updating an entity with invalid values using PUT/POST

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1778:

Fix Version/s: (was: trunk)

> Incorrect error code returned in V2 APIs when updating an entity with invalid 
> values using PUT/POST
> ---
>
> Key: ATLAS-1778
> URL: https://issues.apache.org/jira/browse/ATLAS-1778
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1
>
> Attachments: 
> 0001-ErrorCode-fixes-and-bad-request-when-invalid-attribu.patch
>
>
> Entity Update using PUT /POST with wrong values for attributes throws 404 Not 
> Found exception . Expected is 400 Bad Request .
> {code}
> curl -v -u  admin:admin -H "Content-Type: application/json" -d @entity.json 
> -X POST 
> "http://ctr-e133-1493418528701-6996-01-06.hwx.site:21000/api/atlas/v2/entity;
> *   Trying 172.27.14.75...
> * Connected to ctr-e133-1493418528701-6996-01-06.hwx.site (172.27.14.75) 
> port 21000 (#0)
> * Server auth using Basic with user 'admin'
> > POST /api/atlas/v2/entity HTTP/1.1
> > Host: ctr-e133-1493418528701-6996-01-06.hwx.site:21000
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.43.0
> > Accept: */*
> > Content-Type: application/json
> > Content-Length: 937
> >
> * upload completely sent off: 937 out of 937 bytes
> < HTTP/1.1 404 Not Found
> < Date: Fri, 05 May 2017 06:09:21 GMT
> < Set-Cookie: ATLASSESSIONID=1e65za9f72n3n7dcxp6bsgf2o;Path=/;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < X-Frame-Options: DENY
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host ctr-e133-1493418528701-6996-01-06.hwx.site left 
> intact
> {"errorCode":"ATLAS-404-00-007","errorMessage":"Invalid instance 
> creation/updation parameters passed : entity_type_VNsAA.type_date=str: 
> invalid value for type date"}
> {code}
> *V1 APIs return 400 Bad Request*



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1763) UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS tab

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1763:

Fix Version/s: 0.8.1
   1.0.0

> UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS 
> tab 
> 
>
> Key: ATLAS-1763
> URL: https://issues.apache.org/jira/browse/ATLAS-1763
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Trivial
> Fix For: 0.8.1, 1.0.0
>
>
> 1. Created tag tag1
> 2. Clicked on TAGS tab which landed in 
> http://localhost:21000/index.html#!/tag/tagAttribute/tag1
> 3. Deleted the tag through REST.
> 4. Clicked on the TAGS tab. The TAGS tab listed tag1 . But on disabling cache 
> , tag1 is removed.
> 5.But Atlas lands in 
> http://localhost:21000/index.html#!/tag/tagAttribute/tag1 which throws 404 
> exception while clicking Tags tab .
> On opening Atlas in another incognito window , this issue is not seen . Atlas 
> possibly caches tag1 which lands in /tag/tagAttribute/tag1 and causes issue.
> When there are 1 or more ACTIVE tags , this issue is not seen as it lands in 
> /tag/tagAttribute/.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1734) Import API: Add Support to Update Attributes of Existing Types During Import

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1734:

Affects Version/s: (was: trunk)
Fix Version/s: (was: trunk)
   0.8.1
   1.0.0

Committed to following branches:
 - master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/8101883c
 - branch-0.8: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/f62f077f

> Import API: Add Support to Update Attributes of Existing Types During Import
> 
>
> Key: ATLAS-1734
> URL: https://issues.apache.org/jira/browse/ATLAS-1734
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
>  Labels: patch
> Fix For: 0.8.1, 1.0.0
>
> Attachments: 
> ATLAS-1734-Import-with-additional-attribute-processi.patch
>
>
> *Background*
> Existing version of Import API allows for importing types that are not 
> already present in the system being imported in. This causes import to fail 
> in the cases where the data being imported happens to have the additional 
> attribute.
> *Solution*
> During import, existing types are checked to determine if the types being 
> imported have additional attributes. If additional attributes exist, then the 
> existing type is updated with the new attributes. The import then proceeds.
> *Impact Assessment*
> - Import API: 
>   -- Type import: Additional capability (mentioned above).
>   -- Entity creation and processing: No impact.
> - Export API: No impact.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-1662) New governance action API to support Ranger tags from v2 glossary

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1662.
-
Resolution: Duplicate

> New governance action API to support Ranger tags from v2 glossary
> -
>
> Key: ATLAS-1662
> URL: https://issues.apache.org/jira/browse/ATLAS-1662
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> Today Ranger obtains classification ("tags") from atlas via a tagsync process 
> which
>  - looks at interesting types
>  - going through entities of those types
>  - pulling traits/trait instances to get tags
>  - formulating these into a map
>  - persisting in ranger
> ATLAS-1410 proposes a new enterprise ready glossary which allows for a more 
> sophticated approach to classification.
> To support this we will develop a new consumer-centric ("omas") API to 
> support Ranger or other enforcement engines . The implementation behind the 
> first function of this API will navigate the new glossary structure to 
> present ranger with the simplified entity:classification map it needs rather 
> than the more elaborate structure of the glossary. 
> A new ranger tagsync process will then use this api to push tags into ranger 
> without needing changes 
> More generally this API will support anything an enforcement engine needs
> more detail to follow
> (Note to observers: could you assign this one to me or grant permission)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (ATLAS-1662) New governance action API to support Ranger tags from v2 glossary

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reopened ATLAS-1662:
-

> New governance action API to support Ranger tags from v2 glossary
> -
>
> Key: ATLAS-1662
> URL: https://issues.apache.org/jira/browse/ATLAS-1662
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> Today Ranger obtains classification ("tags") from atlas via a tagsync process 
> which
>  - looks at interesting types
>  - going through entities of those types
>  - pulling traits/trait instances to get tags
>  - formulating these into a map
>  - persisting in ranger
> ATLAS-1410 proposes a new enterprise ready glossary which allows for a more 
> sophticated approach to classification.
> To support this we will develop a new consumer-centric ("omas") API to 
> support Ranger or other enforcement engines . The implementation behind the 
> first function of this API will navigate the new glossary structure to 
> present ranger with the simplified entity:classification map it needs rather 
> than the more elaborate structure of the glossary. 
> A new ranger tagsync process will then use this api to push tags into ranger 
> without needing changes 
> More generally this API will support anything an enforcement engine needs
> more detail to follow
> (Note to observers: could you assign this one to me or grant permission)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1641) UI Regression : Clicking on "Add Tag" button in the Search result table in index.html page doesn't open up the Add Tag window.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1641:

Fix Version/s: 0.8-incubating

> UI Regression : Clicking on "Add Tag" button in the Search result table in 
> index.html page doesn't open up the Add Tag window.
> --
>
> Key: ATLAS-1641
> URL: https://issues.apache.org/jira/browse/ATLAS-1641
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.8-incubating
>
>
> Clicking on "Add Tag" button corresponding to any entity in the Search result 
> table in index.html page doesn't open up the Add Tag window. Network tab in 
> the browser shows no action or query being fired on clicking the button.
> But in the detailsPage of entity , Add tag button is clickable and opens up 
> the Add Tag Window.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1651) Change master version to 0.9-incubating

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1651:

Fix Version/s: (was: trunk)
   1.0.0-alpha

> Change master version to 0.9-incubating
> ---
>
> Key: ATLAS-1651
> URL: https://issues.apache.org/jira/browse/ATLAS-1651
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 1.0.0-alpha
>
> Attachments: ATLAS-1651.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-1612) Regression: DSL search using a non-unique attribute of user-defined types results in empty response

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1612.
-
   Resolution: Not A Problem
Fix Version/s: (was: trunk)

> Regression: DSL search using a non-unique attribute of user-defined types 
> results in empty response
> ---
>
> Key: ATLAS-1612
> URL: https://issues.apache.org/jira/browse/ATLAS-1612
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: 0.8-incubating
>
>
> Steps to repro:
> 1. Create a user defined type like below
> {noformat}
> {
> "enumTypes":[
>   ],
>   "structTypes":[
>   ],
>   "traitTypes":[
>   ],
>   "classTypes":[
> {
>   "superTypes":[
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"sample",
>   "typeDescription":null,
>   "typeVersion":"1.0",
>   "attributeDefinitions":[
> {
>   "name":"name",
>   "dataTypeName":"string",
>   "multiplicity":"required",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> {noformat}
> 2. create an entity of above type
> {noformat}
>   {
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"-16993187400044476",
>   "version":0,
>   "typeName":"sample",
>   "state":"ACTIVE"
> },
> "typeName":"sample",
> "values":{
>   "name":"simple_column"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
>   "createdBy":null,
>   "modifiedBy":null,
>   "createdTime":null,
>   "modifiedTime":null
> }
>   }
> {noformat}
> 3. Now perform a dsl search using below query - "query": "sample where name = 
> \"sample_column\"",



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (ATLAS-1612) Regression: DSL search using a non-unique attribute of user-defined types results in empty response

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reopened ATLAS-1612:
-

> Regression: DSL search using a non-unique attribute of user-defined types 
> results in empty response
> ---
>
> Key: ATLAS-1612
> URL: https://issues.apache.org/jira/browse/ATLAS-1612
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: 0.8-incubating
>
>
> Steps to repro:
> 1. Create a user defined type like below
> {noformat}
> {
> "enumTypes":[
>   ],
>   "structTypes":[
>   ],
>   "traitTypes":[
>   ],
>   "classTypes":[
> {
>   "superTypes":[
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"sample",
>   "typeDescription":null,
>   "typeVersion":"1.0",
>   "attributeDefinitions":[
> {
>   "name":"name",
>   "dataTypeName":"string",
>   "multiplicity":"required",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> {noformat}
> 2. create an entity of above type
> {noformat}
>   {
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"-16993187400044476",
>   "version":0,
>   "typeName":"sample",
>   "state":"ACTIVE"
> },
> "typeName":"sample",
> "values":{
>   "name":"simple_column"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
>   "createdBy":null,
>   "modifiedBy":null,
>   "createdTime":null,
>   "modifiedTime":null
> }
>   }
> {noformat}
> 3. Now perform a dsl search using below query - "query": "sample where name = 
> \"sample_column\"",



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1610) Regression: GUID order in the entity create response is not returned in the expected order(i.e; creation order).

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1610:

Fix Version/s: (was: trunk)

> Regression: GUID order in the entity create response is not returned in the 
> expected order(i.e; creation order).
> 
>
> Key: ATLAS-1610
> URL: https://issues.apache.org/jira/browse/ATLAS-1610
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Sarath Subramanian
>Priority: Blocker
> Fix For: 0.8-incubating
>
>
> Steps to repro:
> 1. create below entity with two reference entities in it using /entities POST 
> rest call
> {noformat}
> {
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-16989787630260306",
> "version":0,
> "typeName":"ComplexEntityTestTable9u3zoazpsj",
> "state":"ACTIVE"
>   },
>   "typeName":"ComplexEntityTestTable9u3zoazpsj",
>   "values":{
> "columns":[
>   {
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"-16989787630260309",
>   "version":0,
>   "typeName":"ComplexEntityTestColumn2iv0d87lrb",
>   "state":"ACTIVE"
> },
> "typeName":"ComplexEntityTestColumn2iv0d87lrb",
> "values":{
>   "name":"column14vqfo3ocvf13"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
>   "createdBy":null,
>   "modifiedBy":null,
>   "createdTime":null,
>   "modifiedTime":null
> }
>   },
>   {
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"-16989787630260308",
>   "version":0,
>   "typeName":"ComplexEntityTestColumn2iv0d87lrb",
>   "state":"ACTIVE"
> },
> "typeName":"ComplexEntityTestColumn2iv0d87lrb",
> "values":{
>   "name":"column2dofzvezzh12123"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
>   "createdBy":null,
>   "modifiedBy":null,
>   "createdTime":null,
>   "modifiedTime":null
> }
>   }
> ],
> "db":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"bad8c2eb-050e-4dbc-b219-92a5fe850fef",
>   "version":0,
>   "typeName":"ComplexEntityTestDB2dnlau6arq",
>   "state":"ACTIVE"
> },
> "name":"createComplexEntityTablebllw6t3u1x123"
>   },
>   "traitNames":[
>   ],
>   "traits":{
>   },
>   "systemAttributes":{
> "createdBy":null,
> "modifiedBy":null,
> "createdTime":null,
> "modifiedTime":null
>   }
> }
> {noformat}
> 2. Check the response for this POST request. Ideally first the reference 
> entity GUID should be present in entities.created[] array.
> For example: 
> IF table1 is created with col1 and col2 then the response object should 
> contain entities.created["col1.GUID", "col2.GUID",  "table1.GUID"] but the 
> actual response contains in reverse order. *This breaks the exisitng behavior 
> and hence regression*
> {noformat}
> {
>   "requestId": "pool-2-thread-10 - c79079a0-db10-4fa1-8eaa-b088993b23b0",
>   "entities": {
> "created": [
>   "6797d3c6-ee99-4d97-8fa8-b11d37fe4801",
>   "9cc65c33-ab3a-4de3-8b27-3684b6580171",
>   "9a29b72c-fb6a-4f54-b4fe-f306da87e383"
> ]
>   },
>   "definition": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id": {
>   "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id": "6797d3c6-ee99-4d97-8fa8-b11d37fe4801",
>   "version": 0,
>   "typeName": "ComplexEntityTestTable9u3zoazpsj",
>   "state": "ACTIVE"
> },
> "typeName": "ComplexEntityTestTable9u3zoazpsj",
> "values": {
>   "columns": [
> {
>   "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "9cc65c33-ab3a-4de3-8b27-3684b6580171",
> "version": 0,
> "typeName": "ComplexEntityTestColumn2iv0d87lrb",
> 

[jira] [Updated] (ATLAS-1605) Edit Entity in UI : Update button is not enabled when updating attribute of type date

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1605:

Fix Version/s: 0.8-incubating

> Edit Entity in UI : Update button is not enabled when updating attribute of 
> type date
> -
>
> Key: ATLAS-1605
> URL: https://issues.apache.org/jira/browse/ATLAS-1605
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1605.1.patch, ATLAS-1605.patch
>
>
> On editing attributes of hdfs_path like CreateTime , ModifiedTime which are 
> of type date , Update button is not enabled. This happens for all entity 
> types which have attributes of type date. Editing other types enables the 
> Update button.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1578) Problem with Firefox UI : While creating/editing entity in UI ,value to be selected from a drop down list gets auto selected.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1578:

Fix Version/s: 1.0.0

> Problem with Firefox UI : While creating/editing entity in UI ,value to be 
> selected from a drop down list gets auto selected.
> -
>
> Key: ATLAS-1578
> URL: https://issues.apache.org/jira/browse/ATLAS-1578
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
> Environment: Firefox 45.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.8.1, 1.0.0
>
>
> When creating hbase_column_family , hbase_table is one of its attributes 
> which is a drop down list of all hbase_tables. Even before providing the 
> hbase_table, an hbase_table entity is pre selected. This preselection doesn't 
> happen on Chrome or Safari. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1578) Problem with Firefox UI : While creating/editing entity in UI ,value to be selected from a drop down list gets auto selected.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1578:

Fix Version/s: 0.8.1

> Problem with Firefox UI : While creating/editing entity in UI ,value to be 
> selected from a drop down list gets auto selected.
> -
>
> Key: ATLAS-1578
> URL: https://issues.apache.org/jira/browse/ATLAS-1578
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
> Environment: Firefox 45.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.8.1, 1.0.0
>
>
> When creating hbase_column_family , hbase_table is one of its attributes 
> which is a drop down list of all hbase_tables. Even before providing the 
> hbase_table, an hbase_table entity is pre selected. This preselection doesn't 
> happen on Chrome or Safari. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1585) Search result page should show the entityType for each result

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1585:

Fix Version/s: 0.8-incubating

> Search result page should show the entityType for each result
> -
>
> Key: ATLAS-1585
> URL: https://issues.apache.org/jira/browse/ATLAS-1585
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Srikanth Venkat
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1585.patch
>
>
> Currently, the search result page shows the following columns:
> {noformat}
> - Name
> - Description
> - Owner
> - Tags
> {noformat}
> In addition, it will be helpful to include the entityType for each entry in 
> the result - given that the result might include entities of different types, 
> especially in full-text search and tag-search.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1564) EntityResource v1 should start routing its calls to v2 EntityREST

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1564:

Fix Version/s: 0.8-incubating

> EntityResource v1 should start routing its calls to v2 EntityREST
> -
>
> Key: ATLAS-1564
> URL: https://issues.apache.org/jira/browse/ATLAS-1564
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1564.3.patch
>
>
> With the v2 implementation of EntityREST ready, we must start routing all v1 
> entity CRUD calls to start using v2 APIs in EntityREST. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1565) Create EntityREST endpoints for delete operations

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1565:

Fix Version/s: 0.8-incubating

> Create EntityREST endpoints for delete operations
> -
>
> Key: ATLAS-1565
> URL: https://issues.apache.org/jira/browse/ATLAS-1565
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1565.1.patch
>
>
> EntityREST delete endpoints need to hook to the v2 delete methods in v2 
> entitiesStore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1562) Not able to delete hbase_column_family once associated to the hbase_table.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1562:

Fix Version/s: 0.8-incubating

> Not able to delete hbase_column_family once associated to the hbase_table.
> --
>
> Key: ATLAS-1562
> URL: https://issues.apache.org/jira/browse/ATLAS-1562
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8-incubating
>
>
> Created 
> 1. hbase_table "table1"
> 2. hbase_column_family "colfam1" wit hbase_table as "table1"
> 3. Edited "table1" and added  "colfam1" . Column family is added. 
> 4. Edited "table1" and removed "colfam1". Column family is not removed and 
> still associated to table1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1555) Move classification endpoint from Entities API to Entity API and remove Entities API

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1555:

Fix Version/s: 0.8-incubating
  Component/s:  atlas-core

> Move classification endpoint from Entities API to Entity API and remove 
> Entities API
> 
>
> Key: ATLAS-1555
> URL: https://issues.apache.org/jira/browse/ATLAS-1555
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1555.patch
>
>
> Entities API has a single method(API endpoint) to associate a classification 
> to multiple entities.
> Move this classification endpoint from Entities API to Entity API and remove 
> Entities API



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1527) Batch entity retrievals in DefaultMetadataService.loadEntities

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1527:

Fix Version/s: 0.8-incubating
  Component/s:  atlas-core

Committed to master: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/1e105174

> Batch entity retrievals in DefaultMetadataService.loadEntities
> --
>
> Key: ATLAS-1527
> URL: https://issues.apache.org/jira/browse/ATLAS-1527
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Wojciech Wojcik
>Assignee: Wojciech Wojcik
>Priority: Minor
> Fix For: 0.8-incubating
>
> Attachments: rb56324.patch
>
>
> DefaultMetadataService.loadEntities() is called at the conclusion of entity 
> creation and update, to load the created/updated entities which are passed to 
> the EntityChangeListener's. The entities are being loaded one at time, 
> because MetadataRepository does not expose a method to retrieve multiple 
> entities by GUID. MetadataRepository can be enhanced to provide a 
> getEntityDefinitions() entrypoint, and the implementation in 
> GraphBackedMetadataRepository can batch the vertex retrievals using 
> GraphHelper.getVerticesForGUIDs(). This will reduce the graph calls to 
> retrieve the vertices.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1523) Implement GET entity by guid and unique attributes in V2 Entity API using AtlasObjectID

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1523:

Fix Version/s: 0.8-incubating

> Implement GET entity by guid and unique attributes in V2 Entity API using 
> AtlasObjectID
> ---
>
> Key: ATLAS-1523
> URL: https://issues.apache.org/jira/browse/ATLAS-1523
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1523.23.patch
>
>
> Current implementation of GET API for entity v2 still routes to V1 entity 
> APIs and does a V1toV2 conversion. We need to directly query the v2 
> entitiesStore to get the required entity.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1510) Consolidate/batch calls to GraphBackedTypeStore.findVertex()

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1510:

Fix Version/s: 0.8-incubating

> Consolidate/batch calls to GraphBackedTypeStore.findVertex()
> 
>
> Key: ATLAS-1510
> URL: https://issues.apache.org/jira/browse/ATLAS-1510
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Jeffrey Hagelberg
>Assignee: Jeffrey Hagelberg
>Priority: Major
> Fix For: 0.8-incubating
>
>
> This showed up as a major hotspot during our profiling of the Atlas 
> initialization.  The idea here is to reduce the number of queries made during 
> type creation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1493) Create Entity in UI : Inputs,Outputs attributes of types make the same DSL query twice.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1493:

Fix Version/s: 0.8-incubating

> Create Entity in UI : Inputs,Outputs attributes of types make the same DSL 
> query twice.
> ---
>
> Key: ATLAS-1493
> URL: https://issues.apache.org/jira/browse/ATLAS-1493
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Trivial
> Fix For: 0.8-incubating
>
>
> Types inheriting Process have Inputs , Outputs field make same DSL query 
> twice, once for Inputs and once for Outputs while Creating /Editing an Entity 
> in UI.
> DSL query : 
> {code}
> /api/atlas/discovery/search/dsl?query=DataSet
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1492) Create Entity in UI : Inputs and Outputs field of types takes forever to list the entities (UI issue)

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1492:

Fix Version/s: 0.8-incubating

> Create Entity in UI : Inputs and Outputs field of types takes forever to list 
> the entities (UI issue)
> -
>
> Key: ATLAS-1492
> URL: https://issues.apache.org/jira/browse/ATLAS-1492
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.8-incubating
>
>
> Types with Process as supertype have Inputs and Outputs field which are of 
> type array . DSL Query :
> {code}
> /api/atlas/discovery/search/dsl?query=DataSet
> {code}
> returns response soon . But in the Edit Entity window, Inputs and Outputs 
> doesn't return the entities in the drop down list box.
> Example :
> In my cluster setup , the above DSL query returned 100 results in less than 3 
> seconds but the UI doesn't list down the entities.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1521) Update UI to eliminate REST calls to obtain schema data

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1521:

Fix Version/s: 0.8-incubating

> Update UI to eliminate REST calls to obtain schema data
> ---
>
> Key: ATLAS-1521
> URL: https://issues.apache.org/jira/browse/ATLAS-1521
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1521.1.patch, ATLAS-1521.2.patch, ATLAS-1521.patch
>
>
> When rendering entity details page, UI makes a REST API call to 
> /schema/{guid} to obtain the schema data. For entity types that don't support 
> the notion of schema, this REST API call returns an error. When such error is 
> returned, UI does not add 'Schema' tab to the details page. When the call 
> returns data, UI renders the data in 'Schema' tab.
> Given that only few entity-types (like hive_table) support schema, most calls 
> to retrieve schema return an error. Having additional schema related 
> information in the type can eliminate the need for unnecessary REST calls. 
> ATLAS-1517 introduces additional data in 'typeDefOptions' attribute of 
> entity-type definition. UI can use the following logic to render the schema 
> tab contents:
> # Does an entity-type support schema?
>   Is {{entityDef.typeDefOptions\[schemaElementsAttribute]}} set and its value 
> non empty? If yes, schema is supported else not-supported. For hive_table 
> type, this will be set to 'columns' - as shown below:
> {code}
>   "typeDefOptions": {
> "schemaElementsAttribute": "columns"
>   }
> {code}
> # How does UI get the data to display in schema tab?
>   Value of {{entityDef.typeDefOptions\[schemaElementsAttribute]}} will be the 
> name of the attribute in the entity being rendered. This attribute should be 
> of type array. The value of this attribute will have the data needed to 
> render the schema tab
> # What are the columns to display in schema tab?
>   Each element of the array attribute value will hold an entity/struct 
> instance.For example, In case of hive_table, columns attribute will have an 
> array of hive_column objects. From each such element, UI should get value of 
> attributes listed in {{elementDef.typeDefOptions\[schemaAttributes]}} to 
> render the schema table. For example, hive_column will have the following:
> {code}
>   "typeDefOptions": {
> "schemaAttributes": "[\"name\", \"description\", \"owner\", \"type\", 
> \"comment\", \"position\"]"
>   }
> {code}
> The value will be a json-ified string array.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1491) UI : Properties tab of detailsPage of all entities has "columns" field.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1491:

Fix Version/s: 0.8-incubating

> UI : Properties tab of detailsPage of all entities has "columns" field.
> ---
>
> Key: ATLAS-1491
> URL: https://issues.apache.org/jira/browse/ATLAS-1491
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.8-incubating
>
>
> Properties tab of all entities has "columns" field. No other entity except 
> hive_table has values for "columns".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1488) Create Entity in UI : FileSize attribute of hdfs_path and fs_path is long. Opens a calendar when clicked.(UI bug)

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1488:

Fix Version/s: 0.8-incubating
  Component/s: atlas-webui

> Create Entity in UI : FileSize attribute of hdfs_path and fs_path is long. 
> Opens a calendar when clicked.(UI bug)
> -
>
> Key: ATLAS-1488
> URL: https://issues.apache.org/jira/browse/ATLAS-1488
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.8-incubating
>
>
> hdfs_path and fs_path have FileSize (long type) as one of its attributes . 
> Clicking on the field when creating /editing  hdfs_path/fs_path , opens up a 
> calendar. Providing a long number (valid input) or date for the same field , 
> it is always updated as 0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 67167: ATLAS-2695: Entity deletion fails if a term was/is associated to it.

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On May 17, 2018, 5:29 a.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67167/
> ---
> 
> (Updated May 17, 2018, 5:29 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2695
> https://issues.apache.org/jira/browse/ATLAS-2695
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 1. create a term and associate to any entity
> 2. Try deleting the entity, it fails.
> 3. Remove term-entity association/
> 4. Try deleting entity, it still fails..
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
>  e62c04107 
> 
> 
> Diff: https://reviews.apache.org/r/67167/diff/2/
> 
> 
> Testing
> ---
> 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/414/console
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

[jira] [Updated] (ATLAS-1914) UI - Search using entity and trait attributes : "Clear" button doesn't clear the filter applied to a type

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1914:

Fix Version/s: 0.8.1
   1.0.0

> UI - Search using entity and trait attributes : "Clear" button doesn't clear 
> the filter applied to a type
> -
>
> Key: ATLAS-1914
> URL: https://issues.apache.org/jira/browse/ATLAS-1914
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-1914.patch
>
>
> 1. Searched type "hive_table" and applied filter "name = table1"
> 2.Clicked Search.
> 3.Clicked Clear button , which cleared the type selected.
> 4.Searched type "hive_table" again. The search had the same "name" filter 
> applied before Clearing.
> Expected that the Clear button would clear the filter too.
> Is this expected ?
> Should there be a Save button instead to explicitly save the queries ?
>  
> CC : [~kevalbhatt] [~apoorvnaik] [~ashutoshm][~madhan.neethiraj]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1997) Search indexer NPE

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1997:

Affects Version/s: (was: trunk)
Fix Version/s: (was: 0.8-incubating)
   (was: trunk)
   0.8.2
   1.0.0
  Component/s:  atlas-core

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/38297a84
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/096917e9

> Search indexer NPE
> --
>
> Key: ATLAS-1997
> URL: https://issues.apache.org/jira/browse/ATLAS-1997
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.2, 1.0.0
>
> Attachments: 
> 0001-ATLAS-1997-Search-Indexer-NPE-on-the-vertex_index.patch
>
>
> Getting the vertex index from the graph management system sometimes runs into 
> an NPE if the graph hasn't been completely initialized. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1999) Use AtlasRelatedObjectId to display relationshipAttribute values during entity retrieval

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1999:

Affects Version/s: (was: trunk)
   1.0.0
Fix Version/s: (was: trunk)
   1.0.0

> Use AtlasRelatedObjectId to display relationshipAttribute values during 
> entity retrieval
> 
>
> Key: ATLAS-1999
> URL: https://issues.apache.org/jira/browse/ATLAS-1999
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1999.1.patch
>
>
> * Currently relationship attribute values during entity retrieval is using 
> AtlasObjectId format. Change this to use AtlasRelatedObjectId to contain 
> additional information for use during search and UI
> * validate and normalize relationship attribute values during entity creation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 67167: ATLAS-2695: Entity deletion fails if a term was/is associated to it.

[Sarath Subramanian]

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

(Updated May 16, 2018, 10:29 p.m.)


Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.


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


Repository: atlas


Description
---

1. create a term and associate to any entity
2. Try deleting the entity, it fails.
3. Remove term-entity association/
4. Try deleting entity, it still fails..


Diffs (updated)
-

  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
 e62c04107 


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

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


Testing
---

https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/414/console


Thanks,

Sarath Subramanian

[jira] [Updated] (ATLAS-1992) UI : Restrict unnecessary API call on selecting columns from drop-down (search table)

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1992:

Fix Version/s: 0.8.1
   1.0.0
  Component/s: atlas-webui

> UI : Restrict unnecessary API call on selecting columns from drop-down 
> (search table)
> -
>
> Key: ATLAS-1992
> URL: https://issues.apache.org/jira/browse/ATLAS-1992
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>
> API call should not hit if data available in the collection.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1984) Use AtlasRelatedObjectId to refer to relationship attributes during entity create/update

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1984:

Affects Version/s: (was: trunk)
Fix Version/s: 1.0.0

> Use AtlasRelatedObjectId to refer to relationship attributes during entity 
> create/update
> 
>
> Key: ATLAS-1984
> URL: https://issues.apache.org/jira/browse/ATLAS-1984
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1984.1.patch
>
>
> AtlasObjectId is used to refer to entity attributes referring to another 
> entity.
> hive_table.columns => List
> hive_table.db => AtlasObjectId
> Change this to use AtlasRelatedObjectId with the following structure:
> class AtlasRelatedObjectId  {
>String relationshipGuid;
>String displayText;
>AtlasStruct relationshipAttributes; 
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1980) Add relationship instance validation to check end point type

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1980:

Fix Version/s: 1.0.0
  Component/s:  atlas-core

> Add relationship instance validation to check end point type
> 
>
> Key: ATLAS-1980
> URL: https://issues.apache.org/jira/browse/ATLAS-1980
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1980.patch
>
>
> Using a model RelationshipDef that is defines
>  {
>  "name": "CategoryAnchor",
>  "typeVersion": "1.0",
>  "endDef1": {
>"name": "categories",
>"type": "Glossary",
>"cardinality":"SET",
> "isContainer":true
>  },
>  "endDef2": {
>"name": "anchor",
>"type": "GlossaryCategory",
>"cardinality":"SINGLE"
>  },
>  "relationshipCategory":"COMPOSITION",
>  "propagateTags":"NONE"
>  },
> - it does not check that the guid of the relationship is actually of the 
> right type. If I create an instance of the above relationships passing 2 
> GlossaryCategory  guids ; it works. This should be rejected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1979) Update storm model relationship category and fix for UT and Coverity scan issues

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1979:

Fix Version/s: 1.0.0
  Component/s:  atlas-core

> Update storm model relationship category and fix for UT and Coverity scan 
> issues
> 
>
> Key: ATLAS-1979
> URL: https://issues.apache.org/jira/browse/ATLAS-1979
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1979.1.patch
>
>
> * Update storm_topology_nodes relationshipCategory from ASSOCIATION to 
> AGGREGATION
> * Fix the following UT failures:
> _Failed tests: 
>   
> AtlasRelationshipStoreHardDeleteV1Test>AtlasRelationshipStoreV1Test.testDepartmentEmployeeEntitiesUsingRelationship:172
>  expected: but was:<[]>
>   
> AtlasRelationshipStoreSoftDeleteV1Test>AtlasRelationshipStoreV1Test.testDepartmentEmployeeEntitiesUsingRelationship:172
>  expected: but was:<[]>_
> * Fix coverity scan issues flagged in last report related to ATLAS-1959



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1959) Enhance relationship attributes to support different cardinality mappings

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1959:

Fix Version/s: 1.0.0

> Enhance relationship attributes to support different cardinality mappings
> -
>
> Key: ATLAS-1959
> URL: https://issues.apache.org/jira/browse/ATLAS-1959
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: trunk, 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1959.1.patch
>
>
> 1. Improve relationship model to support create/update operations and the 
> following cardinalities (previously supported using inverseReference):
> * 1 to 1
> * 1 to many
> * many to 1
> * many to many
> 2. Change legacyLabel flag in AtlasRelationshipEndDef to boolean flag.
> 3. Add unit tests for the above cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1949) Fix coverity scan issues and IT failure due to ATLAS-1907

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1949:

Fix Version/s: 1.0.0

> Fix coverity scan issues and IT failure due to ATLAS-1907
> -
>
> Key: ATLAS-1949
> URL: https://issues.apache.org/jira/browse/ATLAS-1949
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1949.1.patch
>
>
> Fix coverity scan issues and IT failure due to ATLAS-1907



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1943) Fix IT failure, lineage due to incorrect inverse reference check using relationship

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1943:

Fix Version/s: 1.0.0
  Component/s:  atlas-core

> Fix IT failure, lineage due to incorrect inverse reference check using 
> relationship
> ---
>
> Key: ATLAS-1943
> URL: https://issues.apache.org/jira/browse/ATLAS-1943
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: ATLAS-1943.1.patch
>
>
> Fix the following IT failures due to
> Failed tests: 
>   EntityJerseyResourceIT.testCompleteUpdate:952 » AtlasService Metadata 
> service ...
>   EntityJerseyResourceIT.testPartialUpdate:877 » AtlasService Metadata 
> service A...
> After creating a relationship for inverse reference attribute, call is made 
> to create relationship for ownedRef attribute. But relationship for ownedRef 
> has already been created and we see exception in log - “relationship already 
> exists”. 
> For e.g.: after creating a relationship for hive_storagedesc.table, a new 
> relationship to create hive_table.sd is attempted – but fails since 
> relationship already exists (already created).  Added a new method 
> getOrCreate(relationship) - If a relationship already exists between two 
> entities on an attribute retrieve it, if not create one. Validated the patch 
> by creating hive_table, views – lineage are rendered fine.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1938:

Fix Version/s: 0.8.1
   1.0.0
  Component/s: atlas-webui

> UI - Search using entity and trait attributes - Refresh Button fires the 
> search query (Basic/DSL) again.
> 
>
> Key: ATLAS-1938
> URL: https://issues.apache.org/jira/browse/ATLAS-1938
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-1938.1.patch, ATLAS-1938.2.patch
>
>
> On clicking the Refresh Button to refresh types (data-id : refreshBtn) , 
> makes the following 2 queries :
> # /api/atlas/v2/types/typedefs/headers
> # Search query
> Before the new search feature in place , only query no.1 was made.
> In Advanced search tab , when refresh button is clicked without any type or 
> query , following invalid query is made in addition to query no.1
> http://localhost:21000/api/atlas/v2/search?
> which throws 500 Internal server error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1927) UI - changing the look and feel of attribute in details page.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1927:

Fix Version/s: 0.8.1
   1.0.0
  Component/s: atlas-webui

> UI - changing the look and feel of attribute in details page.
> -
>
> Key: ATLAS-1927
> URL: https://issues.apache.org/jira/browse/ATLAS-1927
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-1927.1.patch, ATLAS-1927.2.patch, 
> ATLAS-1927.3.patch, ATLAS-1927.4.patch, ATLAS-1927.patch
>
>
> Show the attributes of entities in tag format instead of showing comma(,) 
> separator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1911) UI / Search using entity and trait attributes : Specifying no value for one of the filters makes the complete filter null.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1911:

Fix Version/s: 0.8.1
   1.0.0

> UI / Search using entity and trait attributes : Specifying no value for one 
> of the filters makes the complete filter null.
> --
>
> Key: ATLAS-1911
> URL: https://issues.apache.org/jira/browse/ATLAS-1911
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>
> 1.Created a kafka_topic with name="kt1" and empty description.
> 2.Searched kafka_topic in typeName , applied filters:
>  1. Name = kt1 
>  2. Description =  (empty Description)
> 3.The body sent to POST request is :
> {code}
> {"entityFilters":null,"tagFilters":null,"query":null,"excludeDeletedEntities":true,"limit":25,"typeName":"kafka_topic","classification":null}
> {code}
> entityFilters is null , and the Name applied filter was not found in UI or in 
> the request body.The search result was similar to typeName='kafka_topic'.
> The same applies to tag filters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1909) Import/Export : Exception while using "transforms" option during import

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1909:

Fix Version/s: 1.0.0

> Import/Export : Exception while using "transforms" option during import
> ---
>
> Key: ATLAS-1909
> URL: https://issues.apache.org/jira/browse/ATLAS-1909
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Blocker
> Fix For: 1.0.0
>
> Attachments: Import_transforms_error.txt
>
>
> 1. Created a table t5 in cluster1.
> 2. Created the export zip file for table t5 on firing export API on cluster1.
> 3. Created the t5transforms.json file 
> {code}
> {
>   "options": {
>"transforms": {
> "hive_table": {
>   "qualifiedName": [
> "replace:@cl1:@cl2"
>   ]
> }
>   }
> }
>   }
> {code}
> 4.Fired import API on cluster2 using curl call :
> {code}
> curl -v -g -X POST -u admin:admin -H "Content-Type: multipart/form-data" -H 
> "Cache-Control: no-cache" -F request=@t5transforms.json -F data=@t5.zip 
> "http://cluster2:21000/api/atlas/admin/import;
> {code}
> Request failed with 500 Internal server error and the following message :
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
>  java.lang.NullPointerException"}
> {code}
> Attached the complete exception stack trace found in cluster2's  application 
> logs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1907) Create RelationshipDefs for all base models and use this definitions when creating edges for entities

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1907:

Affects Version/s: (was: trunk)
Fix Version/s: 1.0.0

> Create RelationshipDefs for all base models and use this definitions when 
> creating edges for entities
> -
>
> Key: ATLAS-1907
> URL: https://issues.apache.org/jira/browse/ATLAS-1907
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.8.1, 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1907.1.patch
>
>
> Create relationshipDefs for all out of the box models. Use relationshipDef 
> information when creating edges for composite attributes in entities.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1905) Search UI is confusing to user

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1905:

Fix Version/s: 0.8.2
   1.0.0

> Search UI is confusing to user
> --
>
> Key: ATLAS-1905
> URL: https://issues.apache.org/jira/browse/ATLAS-1905
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Laura Ngo
>Assignee: pratik pandey
>Priority: Major
> Fix For: 0.8.2, 1.0.0
>
> Attachments: ATLAS-1905.patch
>
>
> As a business user it has taken me days to understand why my UI search 
> queries were 'unstable' - it turns out the UI is unclear!
> The search interface must be clear to business users. What we actually have 
> is:
> Basic search
> * Search By Type
> * Search By Tag
> * Search By Query
> Advanced search
> * Search By Type
> * Search By Query
> So it looks as if the Advanced search has fewer options than the basic!
> ...but worse, the two aren't analogous despite having the same lables. 
> A 'Search By Query' in Basic return many results, but 'Search By Query' in 
> Advanced returns 1 for hive_table where 
> qualifiedName='db_name.table_name@clauster_name'.
> Only by reading JIRA tickets here did I realise that Basic was a full text 
> search whereas Advanced as DSL.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1904) Incorrect validation around composition relationshipDefs

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1904:

Fix Version/s: (was: trunk)
  Component/s:  atlas-core

> Incorrect validation around composition relationshipDefs
> 
>
> Key: ATLAS-1904
> URL: https://issues.apache.org/jira/browse/ATLAS-1904
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Fix For: 1.0.0
>
>
> The validation around relaitonshipDefs was looking to police that there was 
> only one parent. It is ichecks iscontainer=true and cardinality=SET on an 
> endDef as an error. This is incorrect.
> The check should be to error when isContainer=false cardinality -SET. i.e.  
> to check that there is only one parent for compositions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (ATLAS-2081) Test EntityJerseyResourceIT#testPartialUpdate fails consistently

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reopened ATLAS-2081:
-

> Test EntityJerseyResourceIT#testPartialUpdate fails consistently
> 
>
> Key: ATLAS-2081
> URL: https://issues.apache.org/jira/browse/ATLAS-2081
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 1.0.0
> Environment: Ubuntu:14.04
> $java -version
> openjdk version "1.8.0_111"
> OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
> OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
>Reporter: Sneha Kanekar
>Priority: Major
>  Labels: ppc64le, x86
> Attachments: standard_output_log.txt
>
>
> The integration test 
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate 
> fails consistently with java assertion error. The error message is as follows:
> {code:borderStyle=solid}
> java.lang.AssertionError: expected:<1> but was:<3>
>   at 
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate(EntityJerseyResourceIT.java:881)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-2081) Test EntityJerseyResourceIT#testPartialUpdate fails consistently

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-2081.
-
Resolution: Cannot Reproduce

> Test EntityJerseyResourceIT#testPartialUpdate fails consistently
> 
>
> Key: ATLAS-2081
> URL: https://issues.apache.org/jira/browse/ATLAS-2081
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 1.0.0
> Environment: Ubuntu:14.04
> $java -version
> openjdk version "1.8.0_111"
> OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
> OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
>Reporter: Sneha Kanekar
>Priority: Major
>  Labels: ppc64le, x86
> Attachments: standard_output_log.txt
>
>
> The integration test 
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate 
> fails consistently with java assertion error. The error message is as follows:
> {code:borderStyle=solid}
> java.lang.AssertionError: expected:<1> but was:<3>
>   at 
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate(EntityJerseyResourceIT.java:881)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2064) Compress Hook Messages Posted to Kafka Atlas Topic

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2064:

Fix Version/s: (was: trunk)

> Compress Hook Messages Posted to Kafka Atlas Topic
> --
>
> Key: ATLAS-2064
> URL: https://issues.apache.org/jira/browse/ATLAS-2064
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-2064-compressed-hook-message-envelope.patch
>
>
> *Background*
> Messages posted by hooks to Atlas Kafka topics are JSON format. 
> Kafka imposes a 1MB limit on the message size.
> Occasionally, depending on operations performed, this threshold is reached. 
> This results in messages being dropped.
> The entities are thus not reflected in Atlas.
> *Solution*
> Applying compression to these message will alleviate the problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-2064) Compress Hook Messages Posted to Kafka Atlas Topic

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-2064.
-
Resolution: Duplicate

> Compress Hook Messages Posted to Kafka Atlas Topic
> --
>
> Key: ATLAS-2064
> URL: https://issues.apache.org/jira/browse/ATLAS-2064
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-2064-compressed-hook-message-envelope.patch
>
>
> *Background*
> Messages posted by hooks to Atlas Kafka topics are JSON format. 
> Kafka imposes a 1MB limit on the message size.
> Occasionally, depending on operations performed, this threshold is reached. 
> This results in messages being dropped.
> The entities are thus not reflected in Atlas.
> *Solution*
> Applying compression to these message will alleviate the problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (ATLAS-2064) Compress Hook Messages Posted to Kafka Atlas Topic

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reopened ATLAS-2064:
-

> Compress Hook Messages Posted to Kafka Atlas Topic
> --
>
> Key: ATLAS-2064
> URL: https://issues.apache.org/jira/browse/ATLAS-2064
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-2064-compressed-hook-message-envelope.patch
>
>
> *Background*
> Messages posted by hooks to Atlas Kafka topics are JSON format. 
> Kafka imposes a 1MB limit on the message size.
> Occasionally, depending on operations performed, this threshold is reached. 
> This results in messages being dropped.
> The entities are thus not reflected in Atlas.
> *Solution*
> Applying compression to these message will alleviate the problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2054) Add flag to exclude attribute mapping in FullTextMapper

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2054:

Fix Version/s: (was: 0.8-incubating)
   (was: trunk)
   0.8.3
   1.0.0

> Add flag to exclude attribute mapping in FullTextMapper
> ---
>
> Key: ATLAS-2054
> URL: https://issues.apache.org/jira/browse/ATLAS-2054
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Critical
> Fix For: 1.0.0, 0.8.3
>
> Attachments: ATLAS-2054.1.patch
>
>
> Add property in atlas-application.properties to exclude listed attributes to 
> be excluded when mapping fulltext
> e.g.
> atlas.search.fulltext.followReferences=false
> atlas.search.fulltext.type.hive_table.attributes.exclude=profileData
> atlas.search.fulltext.type.hive_column.attributes.exclude=profileData



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2051) Provide a utility to Import HBase entities into Atlas

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2051:

Affects Version/s: (was: trunk)
Fix Version/s: (was: trunk)
   0.8.3
   1.0.0

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/d1e79fa0
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/d6e69c6d, 
http://git-wip-us.apache.org/repos/asf/atlas/commit/239fa807

> Provide a utility to Import HBase entities into Atlas
> -
>
> Key: ATLAS-2051
> URL: https://issues.apache.org/jira/browse/ATLAS-2051
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 1.0.0, 0.8.3
>
> Attachments: 
> 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie.patch, 
> 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie_002.patch, 
> 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie_003.patch, 
> 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie_004.patch, 
> 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie_005.patch
>
>
> Provide a utility to do Import HBase entities into Atlas



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2050) Add helper method in relationship store to check if entity has relationship associated

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2050:

Fix Version/s: (was: trunk)

> Add helper method in relationship store to check if entity has relationship 
> associated
> --
>
> Key: ATLAS-2050
> URL: https://issues.apache.org/jira/browse/ATLAS-2050
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: ATLAS-2050.2.patch
>
>
> Add helper method in AtlasRelationshipStoreV1 to check whether entity vertex 
> has a relationship associated with a relationship type.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2050) Add helper method in relationship store to check if entity has relationship associated

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2050:

Affects Version/s: (was: trunk)

> Add helper method in relationship store to check if entity has relationship 
> associated
> --
>
> Key: ATLAS-2050
> URL: https://issues.apache.org/jira/browse/ATLAS-2050
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: ATLAS-2050.2.patch
>
>
> Add helper method in AtlasRelationshipStoreV1 to check whether entity vertex 
> has a relationship associated with a relationship type.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2047) NotificationHookConsumer: Exception Thrown by Kafka Consumer Ends up Filling Logs Due to Incorrect Handling

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2047:

Affects Version/s: (was: trunk)
Fix Version/s: (was: trunk)
   0.8.2
   1.0.0

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/b837c0ee
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/cb151bdc

> NotificationHookConsumer: Exception Thrown by Kafka Consumer Ends up Filling 
> Logs Due to Incorrect Handling 
> 
>
> Key: ATLAS-2047
> URL: https://issues.apache.org/jira/browse/ATLAS-2047
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.2, 1.0.0
>
> Attachments: ATLAS-2047-HookConsumer-ExceptionHandling.patch
>
>
> *Background*
> _KafkaConsumer_ is abstracted by _AtlasKafkaConsumer_. This is run using 
> _HookConsumer_ which is derived from _kafka.utils.ShutdownableThread_.
> The _ShutdownableThread_ manages the thread. It handles exceptions thrown in 
> the _doWork_ method and logs them.
> *Problem*
> Exception reported in the bug is thrown by _KafkaConsumer_ is handed by 
> _HookConsumer_. Exception is logged but the thread keeps running. In cases 
> where Kafa is in irrecoverable state, this behavior ends up filling up logs 
> and providing no value in return.
> *Solution*
> Let _ShutdownableThread_ hand exceptions thrown by _KafkaConsumer_. Stop the 
> thread if _KafkaConsumer_ suffers from irrecoverable error. This will avoid 
> the situation described in the problem section.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2045) rename the shipped Atlas model files

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2045:

Fix Version/s: 1.0.0
  Component/s:  atlas-core

Committed to master: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/63ed2a5d

> rename the shipped Atlas model files
> 
>
> Key: ATLAS-2045
> URL: https://issues.apache.org/jira/browse/ATLAS-2045
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2045.patch
>
>
> This change is to rename the shipped Atlas model files. The currently start 
> 0010,0020,0030.
> We will not rename the file 0010 base model file. 
> We will rename 0020... -> 1020... , 0030 -> 1030 etc. 
> This renumbering will create space for new models - for example those in 
> ATLAS_1836 to be added. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2040) Relationship with many-to-many cardinality gives incorrect relationship attribute value

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2040:

Fix Version/s: 1.0.0

> Relationship with many-to-many cardinality gives incorrect relationship 
> attribute value
> ---
>
> Key: ATLAS-2040
> URL: https://issues.apache.org/jira/browse/ATLAS-2040
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2040.1.patch
>
>
> Relationship with many-to-many cardinality gives incorrect relationship 
> attribute value when same attribute name and same type specified at both ends
> When same attribute name and same type is mentioned in both ends of 
> relationship definition. Creating new relationships fails to retireve the 
> right value.
> For e.g.  employee-friends type: same attribute name 'friends' in type 
> 'Employee' specified at both ends
> Add more unit tests to test these cases



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2039) Unable to edit date value from UI when entity definition is POSTed without value for date attribute.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2039:

Fix Version/s: 0.8.2

> Unable to edit date value from UI when entity definition is POSTed without 
> value for date attribute.
> 
>
> Key: ATLAS-2039
> URL: https://issues.apache.org/jira/browse/ATLAS-2039
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating, 0.8.1, 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: pratik pandey
>Priority: Major
> Fix For: 0.8.2
>
> Attachments: ATLAS-2039.patch, Invalid date picker.png
>
>
> 1. Created hdfs_path entity by POSTing the following definition to 
> /api/atlas/v2/entity
> {code}
> {
>"referredEntities":{  },
>"entity":{
>   "typeName":"hdfs_path",
>   "attributes":{
>  "qualifiedName":"dir2",
>  "path":"/user2/dir2",
>  "name":"dir2",
>  "createTime":1502087347000
>   },
>   "guid":"-1",
>   "status":"ACTIVE",
>   "createdBy":"admin",
>   "updatedBy":"admin",
>   "createTime":1502365775921,
>   "updateTime":1502365834237,
>   "version":0
>}
> }
> {code}
> Atlas' hdfs model has createTime and modifiedTime attributes of type date.
> In the definition above , createTime is specified while POSTing whereas 
> modifiedTime is not specified.
> After POSTing the definition , UI shows "Thu Jan 01 1970 05:30:00 GMT+0530 
> (IST)" for modifiedTime. When trying to edit the modifiedTime via UI , it 
> shows "Invalid Date". All the entries in the date picker are "NaN". Whereas 
> ,createTime is editable.
> Attached the screenshot.
> GET entity definition of the POSTed hdfs_path entity :
> {code}
> {
> referredEntities: { },
> entity: {
> typeName: "hdfs_path",
> attributes: {
> owner: null,
> modifiedTime: 0,
> isFile: false,
> numberOfReplicas: 0,
> qualifiedName: "dir2",
> description: null,
> extendedAttributes: null,
> path: "/user2/dir2",
> posixPermissions: null,
> createTime: 1502087347000,
> fileSize: 0,
> clusterName: null,
> name: "dir2",
> isSymlink: false,
> group: null
> },
> guid: "1e684adf-60a6-4008-80b6-d2b0b1897403",
> status: "ACTIVE",
> createdBy: "admin",
> updatedBy: "admin",
> createTime: 1502366891151,
> updateTime: 1502366891151,
> version: 0,
> classifications: [ ]
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2037) Unit Test Failure: NotificationHookConsumerTest.testConsumersAreStoppedWhenInstanceBecomesPassive

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2037:

Fix Version/s: (was: trunk)

> Unit Test Failure: 
> NotificationHookConsumerTest.testConsumersAreStoppedWhenInstanceBecomesPassive
> -
>
> Key: ATLAS-2037
> URL: https://issues.apache.org/jira/browse/ATLAS-2037
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
> Fix For: 0.8.1
>
> Attachments: ATLAS-2037-HookConsumer.patch
>
>
> *Analysis*
> - The test has few mocks, but we don’t mock _HookConsumer_ (derived from 
> _ShutdownableThread_). Hence, the object needs be in line with its usage 
> pattern.
> - The _ShutdownableThread_ has a _CountdownLatch_ that is checked during 
> shutdown.
> In the test, the _HookConsumer_ was not being started at all. This caused 
> _shutdownLatch_ (of type _CountdownLatch_) not to decrement, since no work 
> was performed, but anticipating work is going to be done. The test thus ended 
> up not getting completed, since the thread was in perpetual wait.
> *Solution*
> The _HookConsumer_ should be used such that it is started and shutdown. So 
> the test passes.
> _HookConsumer_ should check for _shouldRun_ in _shutdown_ method, so that the 
> case where _shutdown_ is called without _start_ is handled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2036) Search using entity and trait attributes - Issue with Boolean attributes of tag and case insensitive search

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2036:

Fix Version/s: 0.8.1
   1.0.0

> Search using entity and trait attributes - Issue with Boolean attributes of 
> tag and case insensitive search
> ---
>
> Key: ATLAS-2036
> URL: https://issues.apache.org/jira/browse/ATLAS-2036
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>
> 1. Created a tag tag1 with attributes 
>   strAttr of type string ,
>   boolAttr  of type boolean , 
>   intAttr of type integer
> 2. Associated an entity to the tag with values  =  
> strAttr : value 
> boolAttr : false 
> intAttr : 5
> 3. In Basic search :
>  a)  tag = tag1 ,
>tagfilters :
>  strAttr = valuefetched the entity
>  b)  tag = tag1 ,
>   tagfilters : 
>  strAttr= VALUE  fetched the entity 
>  c)  tag = tag1 ,
>   tagfilters : 
>   strAttr = value , 
>   boolAttr = false ,
>   intAttr = 5 fetched the entity
>  d)  tag = tag1 , 
>   tagfilters : 
>   strAttr = VALUE , 
>   intAttr = 5 fetched any entity
>  e) tag = tag1 , 
>   tagfilters : 
>   boolAttr = falsefetched any entity
>  e) But tag = tag1 ,
>   tagfilters: 
>  strAttr = VALUE ,
>  boolAttr = false didn't fetch any entity . (to be noted : strAttr's 
> value is in CAPS)
> Logs when searching for tag filters : strAttr : VALUE , intAttr:5
> {code}
> 2017-08-09 13:47:55,474 INFO  - [pool-2-thread-9 - 
> 5b8ea24d-0708-4571-b55d-a345d2997ed4:] ~ Converted query string with 3 
> replacements: [v."__typeName":(tag1) AND v."tag1.intAttr": 5 AND 
> v."tag1.strAttr": VALUE] => [iyt_t:(tag1) AND 870ud_i: 5 AND 86rd1_t: VALUE] 
> (IndexSerializer:648)
> 2017-08-09 13:47:55,484 INFO  - [pool-2-thread-9 - 
> 5b8ea24d-0708-4571-b55d-a345d2997ed4:] ~ Converted query string with 3 
> replacements: [v."__typeName":(tag1) AND v."tag1.intAttr": 5 AND 
> v."tag1.strAttr": VALUE] => [iyt_t:(tag1) AND 870ud_i: 5 AND 86rd1_t: VALUE] 
> (IndexSerializer:648)
> {code}
> Logs when searching for tag filters : strAttr : VALUE , boolAttr : false 
> (Note : no INFO logs from IndexSerializer regrading query conversion are 
> found in this search )
> {code}
>  WARN  - [pool-2-thread-9 - 4c272ca0-4853-4d24-b2d0-f10934516889:] ~ search 
> includes non-indexed attribute 'tag1.boolAttr'; might cause poor performance 
> (SearchProcessor:120)
> {code}
> Thus , any case insensitive string search with boolean attribute in tag 
> search fails to fetch the entity. Other datatypes (including enum) when 
> combined with case insensitive search fetches the expected entity.
> Also , this behavior is not observed on entity filters.
> For example , an  hdfs_path entity with description - hdfs_path , isSymLink = 
> false ,
> both the following search fetch the entity :
> 1. description = hdfs_path ,  isSymLink = false 
> 2.  description = Hdfs_path ,  isSymLink = false



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2035) Search using entity and trait attributes - Issue with Case insensitive search in entity attributes and tag

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2035:

Fix Version/s: 0.8.1
   1.0.0

> Search using entity and trait attributes - Issue with Case insensitive search 
> in entity attributes and tag 
> ---
>
> Key: ATLAS-2035
> URL: https://issues.apache.org/jira/browse/ATLAS-2035
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.8.1, 1.0.0
>
>
> 1. Created an hdfs_path entity with description "hdfs_path"
> 2. Created a tag "tag1" and associated the tag to hdfs_path entity
> 3. In Basic Search
> a) Typename = hdfs_path , filter : description = hdfs_path returned the 
> hdfs_path entity
> b) Typename = hdfs_path , filter : description = HDFS_PATH returned the 
> hdfs_path entity (to verify case insensitivity)
>c) Typename = hdfs_path , filter : description = hdfs_path , tag = tag1 
> returned the hdfs_path entity.
>   d) But , Typename = hdfs_path , filter : description = HDFS_PATH , tag = 
> tag1 did not fetch the entity.
> Therefore , any search with tag and case insensitive search in entityFilters 
> does not fetch expected results.
> Logs from EntitySearchProcessor:
> {code}
> 2017-08-09 12:30:06,761 DEBUG - [pool-2-thread-10 - 
> 56d0fb40-683d-48bb-8cf7-8d2dee690379:] ~ ==> 
> EntitySearchProcessor.execute(searchParameters={query='null', 
> typeName='hdfs_path', classification='tag1', excludeDeletedEntities=true, 
> limit=25, offset=0, entityFilters={attributeName='null', operator=null, 
> attributeValue='null', condition=AND, 
> criterion=[{attributeName='description', operator=eq, 
> attributeValue='HDFS_PATH', condition=null, criterion=null}]}, 
> tagFilters=null, attributes=null}) (EntitySearchProcessor:129)
> 2017-08-09 12:30:06,788 DEBUG - [pool-2-thread-10 - 
> 56d0fb40-683d-48bb-8cf7-8d2dee690379:] ~ <== 
> EntitySearchProcessor.execute(searchParameters={query='null', 
> typeName='hdfs_path', classification='tag1', excludeDeletedEntities=true, 
> limit=25, offset=0, entityFilters={attributeName='null', operator=null, 
> attributeValue='null', condition=AND, 
> criterion=[{attributeName='description', operator=eq, 
> attributeValue='HDFS_PATH', condition=null, criterion=null}]}, 
> tagFilters=null, attributes=null}): ret.size()=0 (EntitySearchProcessor:213)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-1925) Bugfixes

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1925.
-
   Resolution: Fixed
Fix Version/s: 0.8.1
   1.0.0

Committed to following branches:
 - master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/abc4856e
 - branch-0.8: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/35fbd58e

> Bugfixes
> 
>
> Key: ATLAS-1925
> URL: https://issues.apache.org/jira/browse/ATLAS-1925
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0, 0.8.1
>
>
> This is a placeholder for all the bugs related to ATLAS-1880



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2029) Enhance classificationDef create to include a list of entities it supports

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2029:

Fix Version/s: 1.0.0
  Description: Committed to master: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/586b5eb2
  Component/s:  atlas-core

> Enhance classificationDef create to include a list of entities it supports
> --
>
> Key: ATLAS-2029
> URL: https://issues.apache.org/jira/browse/ATLAS-2029
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
>  Labels: VirtualDataConnector
> Fix For: 1.0.0
>
> Attachments: ATLAS-2029-1.patch, ATLAS-2029-2.patch, 
> ATLAS-2029-3.patch, ATLAS-2029.patch, ATLAS2029-4.patch, ATLAS2029-5.patch
>
>
> Committed to master: 
> http://git-wip-us.apache.org/repos/asf/atlas/commit/586b5eb2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2020) Result Table Column Filter : Filtering using Columns in Result table always sets excludeDeletedEntities to True

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2020:

Fix Version/s: 0.8.1
   1.0.0

> Result Table Column Filter : Filtering using Columns in Result table always 
> sets excludeDeletedEntities to True
> ---
>
> Key: ATLAS-2020
> URL: https://issues.apache.org/jira/browse/ATLAS-2020
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-2020.1.patch, ATLAS-2020.patch
>
>
> 1. Searched hive_table in basic search.
> 2. Checked "Include historical entities" check box - Result table had DELETED 
> entities.
> 3. Added Columns filter "columns" - This fired a new query with 
> excludeDeletedEntities set to True and fetched only the ACTIVE entities and 
> reset (unchecked)  "Include historical entities" .
> Expected that the current value of excludeDeletedEntities would be used when 
> Column filtering.
> After Column filtering , explicitly had to check "Include historical 
> entities" to list the DELETED entities.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2028) Basic query with entity and tag filters : Invalid filter keys for type and tags attributes are ignored and fetches all entities of the type / associated to the tag

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2028:

Fix Version/s: 0.8.1
   1.0.0

> Basic query with entity and tag filters : Invalid filter keys for type and 
> tags attributes are ignored and fetches all entities of the type / associated 
> to the tag
> ---
>
> Key: ATLAS-2028
> URL: https://issues.apache.org/jira/browse/ATLAS-2028
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: 
> 0001-ATLAS-2028-Invalid-attributes-in-Basic-search-reques.patch
>
>
> Basic search request with POST body fired using curl:
> {code}
> {
>   
> "entityFilters":{"condition":"AND","criterion":[{"attributeName":"invalid_attr","operator":"=","attributeValue":"userdir"}]},
>   "tagFilters":null,
>   "attributes":null,
>   "query":null,
>   "excludeDeletedEntities":true,
>   "limit":25,
>   "typeName":"hdfs_path",
>   "classification":null
> }
> {code}
> All the hdfs_path entities are fetched because invalid filter keys are 
> ignored :
> {code}
> Converted query string with 2 replacements: [v."__typeName":(hdfs_path) AND 
> v."__state":ACTIVE] => [iyt_t:(hdfs_path) AND b2d_t:ACTIVE] 
> (IndexSerializer:648)
> {code}
> Same happens with invalid tag attribute filters also.
> This gives a delusion that all returned hdfs_path entities are satisfied by 
> the filter condition.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2697) V2 Notifications : "Propagated classification added" audit message is present instead of "classification added"

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2697:


 Summary: V2 Notifications : "Propagated classification added" 
audit message is present instead of "classification added"
 Key: ATLAS-2697
 URL: https://issues.apache.org/jira/browse/ATLAS-2697
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


With V2 notifications ,when tag is added to an entity , instead of 
"classification added" audit  , "Propagated classification added" audit message 
is present.

CC : [~sarath.ku...@gmail.com] [~nixonrodrigues]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity

[Keval Bhatt (JIRA)]

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

Keval Bhatt commented on ATLAS-1781:


[~Xinzhi,Luo] this issue is fixed, can you please try latest atlas build 

> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the 
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating, 
> 1.0.0
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
>Priority: Major
>  Labels: atlas
> Fix For: 1.0.0, 0.8.3
>
> Attachments: 0001-fix-not-working-with-more-than-2-nodes.patch, 
> Linage fix not working with more than 2 nodes with ATLAS-1781.png, 
> Lineage_Create_Successfully_when_inputs_outputs_different.png, 
> Lineage_keep_loading.png, Process_Type_Not_Blue.png, 
> Starting_point_is_Impact_than_icon_colour_is_wrong(KEVAL_2_review).jpg, 
> after_test-wrong_op.png, browser_error.png, expected.png, fixed.png, 
> pic1.png, pic2.png
>
>
> I was working with the lineage for hbase, when I added a column family in a 
> hbase table, I want to create a lineage for the table to show there is a 
> change within the table schema, yet when I create a process using the atlas 
> api, I found that the process entity is successfully created, but the lineage 
> is not shown on the atlas web page.
> Steps to Reproduce this issue is: 
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 = 
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME, 
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 = 
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME, 
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name, 
> when I set them different values, the lineage pic can be shown for table1 and 
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI 
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the 
> lineage to different entities.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Jenkins build is back to normal : Atlas-master-IntegrationTests #1361

[Apache Jenkins Server]

See 

Jenkins build is back to normal : PreCommit-ATLAS-Build-Test #416-master-ATLAS-2637-Data-Migration-Infer-types-that-store-edg.patch

[Apache Jenkins Server]

See 

[jira] [Updated] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-1877:
---
Fix Version/s: (was: trunk)
   0.8.3

> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
>Priority: Major
>  Labels: atlas
> Fix For: 1.0.0, 0.8.3
>
> Attachments: 0001-Fix-ATLAS-1877-check-nested-supertype.patch, 
> 0001-fix-ATLAS-1877.patch, Process_Icon_Fixed.png, 
> grand_child_load_process.png, wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its 
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim 
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please 
> find attached screenshot )



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2297) UI : Support to resize columns in Search table

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-2297:
---
Fix Version/s: (was: 1.0.0)

> UI : Support to resize columns in Search table
> --
>
> Key: ATLAS-2297
> URL: https://issues.apache.org/jira/browse/ATLAS-2297
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: pratik pandey
>Assignee: Keval Bhatt
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2645) UI - Continuous loader appears if user goes to Sub-Category of glossary and hit refresh button

[Keval Bhatt (JIRA)]

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

Keval Bhatt reassigned ATLAS-2645:
--

Assignee: Keval Bhatt

> UI - Continuous loader appears if user goes to Sub-Category of glossary and 
> hit refresh button
> --
>
> Key: ATLAS-2645
> URL: https://issues.apache.org/jira/browse/ATLAS-2645
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: SSS20.png
>
>
> Steps to reproduce:-
> 1.Go to glossary tab and create 1 glossary
> 2.Now create one category
> 3.Now create a sub-category under the created category
> 4.Click on the refresh button
>  
> Error:-
> "expected type __AtlasGlossaryCategory; found __AtlasGlossary" error appears 
> and a continuous loader is displayed
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2476) UI - In Audits Tab if Tag is updated then the updated data details is not reflected

[Keval Bhatt (JIRA)]

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

Keval Bhatt reassigned ATLAS-2476:
--

Assignee: Keval Bhatt

> UI - In Audits Tab if Tag is updated then the updated data details is not 
> reflected
> ---
>
> Key: ATLAS-2476
> URL: https://issues.apache.org/jira/browse/ATLAS-2476
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: SS28.png
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-1874) V2 DSL search query does not support for count() but v1 do.

[Apoorv Naik (JIRA)]

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

Apoorv Naik resolved ATLAS-1874.

Resolution: Fixed

> V2 DSL search query does not support for count() but v1 do.
> ---
>
> Key: ATLAS-1874
> URL: https://issues.apache.org/jira/browse/ATLAS-1874
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.1
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0, 0.8.1
>
>
> v1 DSL query supports count()
> {noformat}
> curl -u admin:admin 
> 'http://ctr-e133-1493418528701-113468-01-02.hwx.site:21000/api/atlas/discovery/search/dsl?query=hive_table%20where%20db.name%3D%22default%22%20select%20count()%20as%20%27count%27'
>  | python -m json.tool
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100   5370   5370 0339  0 --:--:--  0:00:01 --:--:--   339
> {
> "count": 1,
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "long",
> "isComposite": false,
> "isIndexable": false,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "count",
> "reverseAttributeName": null
> }
> ],
> "typeDescription": null,
> "typeName": "__tempQueryResultStruct286",
> "typeVersion": "1.0"
> },
> "query": "hive_table where db.name=\"default\" select count() as 'count'",
> "queryType": "dsl",
> "requestId": "pool-2-thread-9 - 47389e3f-bbf1-4209-8e50-8a3235a7e5a9",
> "results": [
> {
> "$typeName$": "__tempQueryResultStruct286",
> "count": 68
> }
> ]
> }
> {noformat}
> v2 DSL search query does not
> {noformat}
> curl -u admin:admin 
> 'http://ctr-e133-1493418528701-113468-01-02.hwx.site:21000/api/atlas/v2/search/dsl?limit=25=true=where+db.name%3D%22default%22+select+count()+as+%27count%27=hive_table&_=1497434602692'
>  | python -m json.tool
> {
> "queryText": "`hive_table` where db.name=\"default\" select count() as 
> 'count'",
> "queryType": "DSL"
> }
> {noformat}
> *From the initial analysis, it seems like, V2 API response does not have the 
> count attribute which is cause for this failure.* might want to consider 
> adding the count in V2?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2658) UI - gId undefined error appears if user toggles to category when there are no terms and category

[Keval Bhatt (JIRA)]

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

Keval Bhatt reassigned ATLAS-2658:
--

Assignee: Keval Bhatt

> UI - gId undefined error appears if user toggles to category when there are 
> no terms and category
> -
>
> Key: ATLAS-2658
> URL: https://issues.apache.org/jira/browse/ATLAS-2658
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: SSS21.png
>
>
> Steps to Reproduce:-
> 1.Go to category tab
> 2.Now switch to category when the category list is empty
>  
> Error:-
> gId undefined error appears in console



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2684) UI - User can not create more than 20 sub-categories within category which is incorrect

[Keval Bhatt (JIRA)]

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

Keval Bhatt reassigned ATLAS-2684:
--

Assignee: Keval Bhatt

> UI - User can not create more than 20 sub-categories within category which is 
> incorrect
> ---
>
> Key: ATLAS-2684
> URL: https://issues.apache.org/jira/browse/ATLAS-2684
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: SS3.png
>
>
> If the sub categories start point reaches till 500 in left menu then this 
> issue occurs. To reproduce this issue keep on creating Sub category within 
> its Sub category and at some point of time user doesn't gets option to add 
> more sub category.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-2683) UI - Delete term option appears for glossary which is incorrect

[Keval Bhatt (JIRA)]

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

Keval Bhatt reassigned ATLAS-2683:
--

Assignee: Keval Bhatt

> UI - Delete term option appears for glossary which is incorrect
> ---
>
> Key: ATLAS-2683
> URL: https://issues.apache.org/jira/browse/ATLAS-2683
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: SS4.png
>
>
> Steps to reproduce:-
> 1.Go to glossary tab
> 2.Now update any glossary
> 3.Now click on its options (3 dots)
>  
> Error:-
> *Delete Term* option appears instead of *Create Term* and *Delete Glossary* 
> which is incorrect



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-1874) V2 DSL search query does not support for count() but v1 do.

[Apoorv Naik (JIRA)]

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

Apoorv Naik reassigned ATLAS-1874:
--

Assignee: Apoorv Naik

> V2 DSL search query does not support for count() but v1 do.
> ---
>
> Key: ATLAS-1874
> URL: https://issues.apache.org/jira/browse/ATLAS-1874
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.1
>Reporter: Ayub Pathan
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>
> v1 DSL query supports count()
> {noformat}
> curl -u admin:admin 
> 'http://ctr-e133-1493418528701-113468-01-02.hwx.site:21000/api/atlas/discovery/search/dsl?query=hive_table%20where%20db.name%3D%22default%22%20select%20count()%20as%20%27count%27'
>  | python -m json.tool
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100   5370   5370 0339  0 --:--:--  0:00:01 --:--:--   339
> {
> "count": 1,
> "dataType": {
> "attributeDefinitions": [
> {
> "dataTypeName": "long",
> "isComposite": false,
> "isIndexable": false,
> "isUnique": false,
> "multiplicity": {
> "isUnique": false,
> "lower": 0,
> "upper": 1
> },
> "name": "count",
> "reverseAttributeName": null
> }
> ],
> "typeDescription": null,
> "typeName": "__tempQueryResultStruct286",
> "typeVersion": "1.0"
> },
> "query": "hive_table where db.name=\"default\" select count() as 'count'",
> "queryType": "dsl",
> "requestId": "pool-2-thread-9 - 47389e3f-bbf1-4209-8e50-8a3235a7e5a9",
> "results": [
> {
> "$typeName$": "__tempQueryResultStruct286",
> "count": 68
> }
> ]
> }
> {noformat}
> v2 DSL search query does not
> {noformat}
> curl -u admin:admin 
> 'http://ctr-e133-1493418528701-113468-01-02.hwx.site:21000/api/atlas/v2/search/dsl?limit=25=true=where+db.name%3D%22default%22+select+count()+as+%27count%27=hive_table&_=1497434602692'
>  | python -m json.tool
> {
> "queryText": "`hive_table` where db.name=\"default\" select count() as 
> 'count'",
> "queryType": "DSL"
> }
> {noformat}
> *From the initial analysis, it seems like, V2 API response does not have the 
> count attribute which is cause for this failure.* might want to consider 
> adding the count in V2?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2019) Search using entity and trait attributes - Equals comparison using filter key when filter key is present between special characters

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2019:

Fix Version/s: (was: 0.8-incubating)
   (was: trunk)
   0.8.1
   1.0.0

> Search using entity and trait attributes - Equals comparison using filter key 
> when filter key is present between special characters
> ---
>
> Key: ATLAS-2019
> URL: https://issues.apache.org/jira/browse/ATLAS-2019
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>
> 1. Created  hdfs_path entity with name = "user" , path = "/user"
> 2. Created another hdfs_path with name="dir1" , path = "/user/dir1"
> 3. Searched for hdfs_path , filter  Path = /user
> 4. The search listed down both the hdfs_path entities - user and dir1. 
> Expected that only "user" entity would be returned.
> Here, the filter key is "/user" and if the filter key is present between 
> special characters in the attribute values ( "/" in this case) , all those 
> entities are returned. 
> Please note that , filter applied is "=" and not "contains"
> Created few random hdfs_path entities for testing :
> For the query type ="hdfs_path" and path = "/user" ,  entities with following 
> path attribute values are returned :
> * user
> * /user
> * user/
> * /user/dir1
> * @user@dir1
> * /user@dir1
> Entities with following path values are *NOT* returned
> * /userdir1
> * rootuser/dir2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2017) Import API: Make Request Parameter Optional

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2017:

Fix Version/s: (was: trunk)
   0.8.1
   1.0.0

Committed to master:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/dd00c859, 
http://git-wip-us.apache.org/repos/asf/atlas/commit/ecd05368
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/a88c7dc2, 
http://git-wip-us.apache.org/repos/asf/atlas/commit/122b5567

> Import API: Make Request Parameter Optional
> ---
>
> Key: ATLAS-2017
> URL: https://issues.apache.org/jira/browse/ATLAS-2017
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-2017.patch
>
>
> Existing Import API needs _request_ parameter, which is empty JSON most of 
> the time. It would help usability if this parameter is made optional.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2010) Atlas Hook consumer runs into type not found

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2010:

Affects Version/s: (was: 0.8.1)
   (was: 0.8-incubating)
   (was: trunk)
Fix Version/s: (was: 0.8.1)

> Atlas Hook consumer runs into type not found
> 
>
> Key: ATLAS-2010
> URL: https://issues.apache.org/jira/browse/ATLAS-2010
> Project: Atlas
>  Issue Type: Bug
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 
> 0001-ATLAS-2010-Hook-should-start-consuming-messages-only.patch
>
>
> Sometimes the Hook consumer bean gets created before the type registry has 
> been fully initialized and when it's trying to create the entity, the type 
> name is missing from the registry.
> Add depends on the HookConsumer class to make sure that the creation only 
> happens after type registry is completely bootstrapped.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2010) Atlas Hook consumer runs into type not found

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-2010:
-

Committed to master: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/eb5d6fcd


> Atlas Hook consumer runs into type not found
> 
>
> Key: ATLAS-2010
> URL: https://issues.apache.org/jira/browse/ATLAS-2010
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.8-incubating, 0.8.1
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: 
> 0001-ATLAS-2010-Hook-should-start-consuming-messages-only.patch
>
>
> Sometimes the Hook consumer bean gets created before the type registry has 
> been fully initialized and when it's trying to create the entity, the type 
> name is missing from the registry.
> Add depends on the HookConsumer class to make sure that the creation only 
> happens after type registry is completely bootstrapped.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2010) Atlas Hook consumer runs into type not found

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2010:

Fix Version/s: (was: 0.8-incubating)
   (was: trunk)
   1.0.0

> Atlas Hook consumer runs into type not found
> 
>
> Key: ATLAS-2010
> URL: https://issues.apache.org/jira/browse/ATLAS-2010
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.8-incubating, 0.8.1
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: 
> 0001-ATLAS-2010-Hook-should-start-consuming-messages-only.patch
>
>
> Sometimes the Hook consumer bean gets created before the type registry has 
> been fully initialized and when it's trying to create the entity, the type 
> name is missing from the registry.
> Add depends on the HookConsumer class to make sure that the creation only 
> happens after type registry is completely bootstrapped.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2007) Regression : Storm model not registered in Atlas due to recent changes

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2007:

Fix Version/s: (was: trunk)

> Regression : Storm model not registered in Atlas due to recent changes
> --
>
> Key: ATLAS-2007
> URL: https://issues.apache.org/jira/browse/ATLAS-2007
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Sarath Subramanian
>Priority: Blocker
> Fix For: 1.0.0
>
> Attachments: ATLAS-2007.1.patch, 
> Storm_model_registration_exception.txt
>
>
> Atlas on startup throws following exception while registering Storm model.
> {code}
> org.apache.atlas.exception.AtlasBaseException: AGGREGATION relationshipDef 
> storm_topology_nodes creation attempted without an end specifying isContainer
> {code}
> This issue is a regression possibly caused by 
> [ATLAS-1979|https://issues.apache.org/jira/browse/ATLAS-1979]
> Attached the complete exception stack trace .
> CC : [~sarath.ku...@gmail.com]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2022) Regression : Empty results fetched from GET Basic search query

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2022:

Fix Version/s: (was: trunk)

> Regression : Empty results fetched from GET Basic search query
> --
>
> Key: ATLAS-2022
> URL: https://issues.apache.org/jira/browse/ATLAS-2022
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Sharmadha Sainath
>Priority: Blocker
> Fix For: 0.8.1, 1.0.0
>
> Attachments: ATLAS-2022.patch
>
>
> Basic search query fired as a POST request with attribute , tag filters 
> fetches correct results.
> But Basic query fired as a GET request with query params encoded in the URL , 
> returns empty results.
> For example : Basic query : typeName = "hive_table" query =  hive_table in Atlas"
> http://localhost:21000/api/atlas/v2/search/basic?typeName=hive_table=employee
> returns 
> {code}
> {
> queryType: "BASIC",
> searchParameters: {
> query: "employee",
> typeName: "hive_table",
> excludeDeletedEntities: false,
> limit: 0,
> offset: 0
> },
> queryText: "employee"
> }
> {code}
> Few commits back , following was the response :
> {code}
> {
> queryType: "BASIC",
> type: "hive_table",
> entities: [
> {
> typeName: "hive_table",
> attributes: {
> owner: "admin",
> qualifiedName: "default.employee@cl1",
> name: "employee",
> description: null
> },
> guid: "253aa208-0415-4e86-8611-3858fad78ede",
> status: "ACTIVE",
> displayText: "employee",
> classificationNames: [ ]
> }
> ]
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1994) Search API: Work with Tag attributes when query and entity filters are specified

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1994:

Fix Version/s: 0.8.1
   1.0.0

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/9b72de98
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/4f6bb7ae

> Search API: Work with Tag attributes when query and entity filters are 
> specified
> 
>
> Key: ATLAS-1994
> URL: https://issues.apache.org/jira/browse/ATLAS-1994
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>
> Currently when the entity text query is specified with the entity and it's 
> filters none of the tag attributes are considered during filtering (search). 
> This change honors the tag attributes during search even under the above 
> scenario



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Jenkins build is back to normal : Atlas-master-UnitTests #1389

[Apache Jenkins Server]

See 

[jira] [Updated] (ATLAS-2091) Search using entity and trait attributes - "#" in string attribute filter doesn't fetch results

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2091:

Fix Version/s: 0.8.2
   1.0.0

> Search using entity and trait attributes - "#" in string attribute filter 
> doesn't fetch results
> ---
>
> Key: ATLAS-2091
> URL: https://issues.apache.org/jira/browse/ATLAS-2091
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.2, 1.0.0
>
> Attachments: 
> 0001-ATLAS-2091-Attribute-values-containing-Tokenizer-cha.patch
>
>
> 1. Created an hdfs_path entity with owner name = "user#3"
> 2. Fired basic search with type name = hdfs_path and filter - owner = user#3. 
> hdfs_path entity was returned.
> 3. Fired basic search with type name = hdfs_path and filter - owner contains 
> user#3. No entity is returned.
> Other than "=" , operators like != , contains , ends_with , begins_with are 
> not fetching expected results due to # in search filter key.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2114) Regression : Type Update using V1 APIs

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2114:

Fix Version/s: 0.8.2
   1.0.0

> Regression : Type Update using V1 APIs
> --
>
> Key: ATLAS-2114
> URL: https://issues.apache.org/jira/browse/ATLAS-2114
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.1, 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Sarath Subramanian
>Priority: Blocker
> Fix For: 0.8.2, 1.0.0
>
> Attachments: ATLAS-2114.1.patch, create_type_v1.sh, update_type_v1.sh
>
>
> V1 Type Update using PUT returns 200 OK with no actual update done to the 
> Type Definition. This issue seems to be regression caused due to 
> [ATLAS-2078|https://issues.apache.org/jira/browse/ATLAS-2078].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2127) Import of an entity associated with a tag into backup cluster with updateTypeDefinition options set to false

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2127:

Fix Version/s: 1.0.0

> Import of an entity associated with a tag into backup cluster with 
> updateTypeDefinition options set to false
> 
>
> Key: ATLAS-2127
> URL: https://issues.apache.org/jira/browse/ATLAS-2127
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ImportExceptionWithTag.txt, hdfs_path1.zip
>
>
> 1. On cluster1 , created an entity and associated it to a tag.
> 2. Exported the entity into a zipfile.
> 3. cluster2 is in clean state.(i.e no entity / tag is created)
> 4. Tried to import the entity zip into cluster2 with import option 
> "updateTypeDefinition" set to false.
> 5. Import failed with NPE. 
> Since updateTypeDefinition is set to false , NPE is thrown when the entity is 
> attempted to be associated to the tag in the backup cluster.
> This is the expected behavior , but the cause of the issue is not very 
> explicit to the end user when Atlas throws NPE.
> Attached the exception stack trace.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2130) Call made to fetch tables of a database doesn't have exlcudeDeletedEntities parameter

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2130:

Fix Version/s: 0.8.2
   1.0.0

> Call made to fetch tables of a database doesn't have exlcudeDeletedEntities 
> parameter
> -
>
> Key: ATLAS-2130
> URL: https://issues.apache.org/jira/browse/ATLAS-2130
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.2, 1.0.0
>
> Attachments: ATLAS-2130.patch
>
>
> Following is the query fired to fetch the tables in a db :
> {code}
> http://localhost:21000/api/atlas/v2/search/relationship?limit=25=8b110b04-b5ad-4738-b7f7-576cc85b2fd4=__hive_table.db=name=ASCENDING&_=1505280717115
> {code}
> Since exlcudeDeletedEntities=true is not set in the param , deleted tables 
> are also shown in the Tables tab of a hive_database's detailPage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2131) Issues during navigation from table in Tables tab with Include historical entities checked

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2131:

Fix Version/s: 0.8.2
   1.0.0

> Issues during navigation from table in Tables tab with Include historical 
> entities checked
> --
>
> Key: ATLAS-2131
> URL: https://issues.apache.org/jira/browse/ATLAS-2131
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.2, 1.0.0
>
> Attachments: TablesInDbNavigation.mov
>
>
> Following is one of the scenarios where there is issue when navigating. Not 
> sure what other scenarios can also lead to the issue.
> 1.Created 100 hive_table entities in a database db1.
> 2. Fired basic query hive_db = db1.
> 3. In the Tables tab of db1 , all 100 tables were listed.
> 4.Checked Include historical entities check box. Now , URL changed to
> {code}
> localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
> {code} 
> 5.Clicked on any of the tables in the result which landed in the detailsPage 
> of the table.
> 6.Now , when "Back To Results" button is clicked , URL changed to 
> {code}
> http://localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
> {code}
>  and landed in Atlas home page (ie. Search page) with all search cleared.
> 7. Fired some basic query and clicked Search . Search was not functioning.
> 8.Switched from Basic -  DSL - Basic . Now fired search again . This time 
> search was working . But  Include Historical entities was checked on by 
> default.
> 9. If Include historical entities was not checked in Tables tab and any 
> entity was selected , this issue was not seen.
> Added a screen recording of the scenario explained above.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2134) Code Improvement To Follow Best Practices

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2134:

Fix Version/s: (was: trunk)
   0.8.3
   1.0.0

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/8eb9c956
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/4c7430dd

> Code Improvement To Follow Best Practices
> -
>
> Key: ATLAS-2134
> URL: https://issues.apache.org/jira/browse/ATLAS-2134
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.0.0, 0.8.3
>
>
> Code Improvement To Follow Best Practices



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2145) Errors during build

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2145:

Fix Version/s: 0.8.3
   1.0.0

> Errors during build
> ---
>
> Key: ATLAS-2145
> URL: https://issues.apache.org/jira/browse/ATLAS-2145
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 0.8-incubating, 1.0.0
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: 1.0.0, 0.8.3
>
> Attachments: ATLAS-2145-2.patch, ATLAS-2145-3.patch, ATLAS-2145.patch
>
>
> Compilation error while building atlas-intg
> atlas-intg error:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 8.358 s
> [INFO] Finished at: 2017-09-18T14:38:00+02:00
> [INFO] Final Memory: 70M/888M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project atlas-intg: Compilation failure: Compilation failure:
> [ERROR] 
> /Users/pbarna/Desktop/apache-source/atlas/intg/src/main/java/org/apache/atlas/model/SearchFilter.java:[20,32]
>  package com.sun.jersey.core.util does not exist
> {noformat}
> dashboardv2 npm error:
> {noformat}
> [ERROR] npm ERR! path 
> /Users/pbarna/Desktop/apache-source/atlas/dashboardv2/target/node_modules/js-beautify/js/bin/css-beautify.js
> [ERROR] npm ERR! code ENOENT
> [ERROR] npm ERR! errno -2
> [ERROR] npm ERR! syscall chmod
> [ERROR] 
> [ERROR] npm ERR! enoent ENOENT: no such file or directory, chmod 
> '/Users/pbarna/Desktop/apache-source/atlas/dashboardv2/target/node_modules/js-beautify/js/bin/css-beautify.js'
> [ERROR] npm ERR! enoent ENOENT: no such file or directory, chmod 
> '/Users/pbarna/Desktop/apache-source/atlas/dashboardv2/target/node_modules/js-beautify/js/bin/css-beautify.js'
> [ERROR] npm ERR! enoent This is most likely not a problem with npm itself
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)