[jira] [Commented] (ATLAS-1879) Updating classification removes some properties

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1879:
-

[~bpgergo] - type renaming should not be allowed. Can you add details of REST 
calls that resulted in above error?

> Updating classification removes some properties
> ---
>
> Key: ATLAS-1879
> URL: https://issues.apache.org/jira/browse/ATLAS-1879
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Laura Ngo
> Attachments: Atlas-1789.postman_collection.json
>
>
> * Created classification via POST. 
> * Updated via PUT
> * Lost properties
> POST http://127.0.0.1:21000/api/atlas/v2/types/typedefs
> {code}
> {
>  "classificationDefs": [{
>   "name": "test_classification_11",
>   "description": "",
>   "createdBy" : "admin",
>   "superTypes": [],
>   "attributeDefs": [{
> "name" : "test_class_11",
> "typeName" : "string",
> "isOptional" : true,
> "isUnique" : true,
> "isIndexable" : true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1
> }]
>  }],
>  "entityDefs": [],
>  "enumDefs": [],
>  "structDefs": []
> }
> {code}
> GET 
> http://127.0.0.1:21000/api/atlas/v2/types/classification/name/test_classification_11
> {code}
> {
> "category": "CLASSIFICATION",
> "guid": "83162fe1-4bb4-4a87-b2b8-364e751a1265",
> "createdBy": "admin",
> "createTime": 1497485890857,
> "updateTime": 1497485890857,
> "version": 1,
> "name": "test_classification_11",
> "description": "",
> "typeVersion": "1.0",
> "attributeDefs": [
>   {
> "name": "test_class_11",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": true,
> "isIndexable": true
> }
> ],
> "superTypes": [],
> }
> {code}
> PUT http://127.0.0.1:21000/api/atlas/v2/types/typedefs
> Update attribute.
> GET 
> http://127.0.0.1:21000/api/atlas/v2/types/classification/name/test_classification_11
> {code}
> {
> "category": "CLASSIFICATION",
> "createdBy": "admin",
> "name": "test_classification_11",
> "description": "",
> "attributeDefs": [
>   {
> "name": "test_class_11",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": true,
> "isIndexable": false
> }
> ],
> "superTypes": [],
> }
> {code}
> Some properties are missing after PUT update of attribute "isIndexable"



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

[jira] [Updated] (ATLAS-1886) DSL queries with LIKE fail for composite searches

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1886:

Attachment: ATLAS-1866.patch

> DSL queries with LIKE fail for composite searches
> -
>
> Key: ATLAS-1886
> URL: https://issues.apache.org/jira/browse/ATLAS-1886
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Hemanth Yamijala
>Assignee: Madhan Neethiraj
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1866.patch
>
>
> Search DSL was enhanced to support the LIKE query in ATLAS-1807. This was a 
> great enhancement from a usability point of view and works as expected for 
> String attributes of a type - like hive_table.name, hive_table.owner etc.
> Another type of query that is useful is composite searches - for e.g. 
> hive_tables in a DB (given a DB name). This query currently works - 
> hive_table where db.name='xyz'.
> However, when we try a 'like' operator here, it fails - i.e. hive_table where 
> db.name LIKE '*xyz*' - this returns an error: Discovery query failed 
> `hive_table` db.name LIKE '*financ*'
> Can this be looked into if its an easy fix?



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

[jira] [Assigned] (ATLAS-1886) DSL queries with LIKE fail for composite searches

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reassigned ATLAS-1886:
---

Assignee: Madhan Neethiraj

> DSL queries with LIKE fail for composite searches
> -
>
> Key: ATLAS-1886
> URL: https://issues.apache.org/jira/browse/ATLAS-1886
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Hemanth Yamijala
>Assignee: Madhan Neethiraj
>
> Search DSL was enhanced to support the LIKE query in ATLAS-1807. This was a 
> great enhancement from a usability point of view and works as expected for 
> String attributes of a type - like hive_table.name, hive_table.owner etc.
> Another type of query that is useful is composite searches - for e.g. 
> hive_tables in a DB (given a DB name). This query currently works - 
> hive_table where db.name='xyz'.
> However, when we try a 'like' operator here, it fails - i.e. hive_table where 
> db.name LIKE '*xyz*' - this returns an error: Discovery query failed 
> `hive_table` db.name LIKE '*financ*'
> Can this be looked into if its an easy fix?



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

[jira] [Resolved] (ATLAS-1885) DELETE classification causes error message

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1885.
-
Resolution: Duplicate

This issue was fixed in ATLAS-1673; the fix will be available in next release 
from master and 0.8-incubating branches.

> DELETE classification causes error message
> --
>
> Key: ATLAS-1885
> URL: https://issues.apache.org/jira/browse/ATLAS-1885
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Laura Ngo
>
> * Created classification via POST (/v2/types/typedefs)
> * Tried to delete it via DELETE (/v2/types/typedefs)
> * Get 204 no content response (should have been removed)
> * Go to UI tag is still there
> * Get error in UI
> Discovery query failed g.V().has('__traitNames', T.in, traitNames) 
> [startIdx.. {code}
> {
>  "classificationDefs": [{
>   "name": "test_classification_10",
>   "superTypes": [],
>   "attributeDefs": []
>  }],
>  "entityDefs": [],
>  "enumDefs": [],
>  "structDefs": []
> }
> {code}



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

[jira] [Commented] (ATLAS-1885) DELETE classification causes error message

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1885:
-

[~LauraNgo] - this issue looks to be a duplicate of ATLAS-1673, which has been 
fixed in master and 0.8-incubting branches. But the fix is not present in 
0.8-incubating release. Can you try on the latest in 0.8-incubating branch or 
master branch?

> DELETE classification causes error message
> --
>
> Key: ATLAS-1885
> URL: https://issues.apache.org/jira/browse/ATLAS-1885
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Laura Ngo
>
> * Created classification via POST (/v2/types/typedefs)
> * Tried to delete it via DELETE (/v2/types/typedefs)
> * Get 204 no content response (should have been removed)
> * Go to UI tag is still there
> * Get error in UI
> Discovery query failed g.V().has('__traitNames', T.in, traitNames) 
> [startIdx.. {code}
> {
>  "classificationDefs": [{
>   "name": "test_classification_10",
>   "superTypes": [],
>   "attributeDefs": []
>  }],
>  "entityDefs": [],
>  "enumDefs": [],
>  "structDefs": []
> }
> {code}



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

[jira] [Commented] (ATLAS-1879) Updating classification removes some properties

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1879:
-

bq. PUT http://127.0.0.1:21000/api/atlas/v2/types/typedefs
[~LauraNgo] - can you add contents of the PUT body? Did it include 
'isIndexable: true' for attribute 'test_class_11'?

> Updating classification removes some properties
> ---
>
> Key: ATLAS-1879
> URL: https://issues.apache.org/jira/browse/ATLAS-1879
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Laura Ngo
>
> * Created classification via POST. 
> * Updated via PUT
> * Lost properties
> POST http://127.0.0.1:21000/api/atlas/v2/types/typedefs
> {code}
> {
>  "classificationDefs": [{
>   "name": "test_classification_11",
>   "description": "",
>   "createdBy" : "admin",
>   "superTypes": [],
>   "attributeDefs": [{
> "name" : "test_class_11",
> "typeName" : "string",
> "isOptional" : true,
> "isUnique" : true,
> "isIndexable" : true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1
> }]
>  }],
>  "entityDefs": [],
>  "enumDefs": [],
>  "structDefs": []
> }
> {code}
> GET 
> http://127.0.0.1:21000/api/atlas/v2/types/classification/name/test_classification_11
> {code}
> {
> "category": "CLASSIFICATION",
> "guid": "83162fe1-4bb4-4a87-b2b8-364e751a1265",
> "createdBy": "admin",
> "createTime": 1497485890857,
> "updateTime": 1497485890857,
> "version": 1,
> "name": "test_classification_11",
> "description": "",
> "typeVersion": "1.0",
> "attributeDefs": [
>   {
> "name": "test_class_11",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": true,
> "isIndexable": true
> }
> ],
> "superTypes": [],
> }
> {code}
> PUT http://127.0.0.1:21000/api/atlas/v2/types/typedefs
> Update attribute.
> GET 
> http://127.0.0.1:21000/api/atlas/v2/types/classification/name/test_classification_11
> {code}
> {
> "category": "CLASSIFICATION",
> "createdBy": "admin",
> "name": "test_classification_11",
> "description": "",
> "attributeDefs": [
>   {
> "name": "test_class_11",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": true,
> "isIndexable": false
> }
> ],
> "superTypes": [],
> }
> {code}
> Some properties are missing after PUT update of attribute "isIndexable"



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

[jira] [Commented] (ATLAS-1885) DELETE classification causes error message

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1885:
-

{quote}
- Tried to delete it via DELETE (/v2/types/typedefs)
- Get 204 no content response (should have been removed)
- Go to UI tag is still there
{quote}
[~LauraNgo] - After classifications were added/deleted via REST API, UI needs 
to be refreshed by clicking on 'refresh' icon. Can you please try?

{quote}
- Get error in UI
{quote}
Can you please add details of the error?

> DELETE classification causes error message
> --
>
> Key: ATLAS-1885
> URL: https://issues.apache.org/jira/browse/ATLAS-1885
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Laura Ngo
>
> * Created classification via POST (/v2/types/typedefs)
> * Tried to delete it via DELETE (/v2/types/typedefs)
> * Get 204 no content response (should have been removed)
> * Go to UI tag is still there
> * Get error in UI
> Discovery query failed g.V().has('__traitNames', T.in, traitNames) 
> [startIdx.. {code}
> {
>  "classificationDefs": [{
>   "name": "test_classification_10",
>   "superTypes": [],
>   "attributeDefs": []
>  }],
>  "entityDefs": [],
>  "enumDefs": [],
>  "structDefs": []
> }
> {code}



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

[jira] [Resolved] (ATLAS-1875) Gremlin id is no longer returned for vertices in gremlin query

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1875.
-
   Resolution: Fixed
Fix Version/s: 0.8.1-incubating
   0.9-incubating

Committed to the following branches:
 - master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/c6081ddc
 - 0.8-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/e183fe83

Thanks [~christianmr] for the patch and [~grahamwallis] for your help.

> Gremlin id is no longer returned for vertices in gremlin query
> --
>
> Key: ATLAS-1875
> URL: https://issues.apache.org/jira/browse/ATLAS-1875
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Christian R
>  Labels: dsl, gremlin
> Fix For: 0.9-incubating, 0.8.1-incubating
>
>
> Hi, 
> while investigating a move from atlas 0.7 to 0.8 (HDP 2.5 to HDP2.6) our 
> tests fail on gremlin queries. It turns out that the returned entities in a 
> gremlin search in 0.8 does not include the 'id' attribute. 
> I've built commit a0bd93945cd45457bbf34a8cb819d4fa4ba72964 (0.8-rc1) on linux 
> using berkely and elasticearch to test with. 
> The query 
> :21000/api/atlas/discovery/search/gremlin?g.V.has('__type.name', 
> 'Infrastructure').collect()
> on our 0.7 cluster gives
> {code:json}
> {
> __type.name: "Infrastructure",
> __type.category: "CLASS",
> __type: "typeSystem",
> id: "16640"
> }{code}
> while the same query on my 0.8-rc1 installation gives 
> {code:javascript}
> {
> __type.name: "Infrastructure",
> __version: "1",
> __type.category: "CLASS",
> __type.version: "1.0",
> __modificationTimestamp: "1497448424134",
> __type: "typeSystem",
> __type.options: "null",
> __type.description: "Infrastructure",
> __guid: "77d07283-7622-4305-9c0c-09ac5aee86c8",
> __timestamp: "1497448424134"
> }
> {code}
> Certainly more information, but id is missing. 
> The very poor DSL performance (see  ATLAS-1868) and a need for advanced 
> queries led us to base our queries on gremlin. This has worked very well so 
> far. We include both edges and nodes in the result set and use the inVertex, 
> outVertex and label info on the edges to rebuild our tree on the client side.
> I also see that gremlin has disappeared from version two of the API. Since 
> addE and addV lets you insert into the graph I can see how exposing a full 
> gremlin endpoint might not be wanted. 
> As an example of the queries we run that I haven't been able to express in 
> the DSL is 
> {noformat}
> query = g.V.has('__guid','').copySplit(
>   _().out('track'), 
>   _().as('x')
>   .out('functions', 'component')
>   .loop('x'){true}{true}
>   .copySplit(
>   _(),
>   _().in('part_of'),
>   _().outE('functions', 
> 'component'),
>   _().inE('part_of')
>   )
>   .exhaustMerge.dedup
>   )
>   .exhaustMerge
> .collect()
> {noformat}
> this might not be a normal usecase. 
> edit to add: 
> I looked at GraphBackedDiscoveryService.java and notice that:
> 0.7:
> {code:java}
> else if (r instanceof TitanVertex) {
> Iterable ps = ((TitanVertex) 
> r).getProperties();
> for (TitanProperty tP : ps) {
> String pName = tP.getPropertyKey().getName();
> Object pValue = ((TitanVertex) r).getProperty(pName);
> if (pValue != null) {
> oRow.put(pName, pValue.toString());
> }
> }
> {code}
> Vs 0.8 code: 
> {code:java}
> else if (value instanceof AtlasVertex) {
> AtlasVertex vertex = (AtlasVertex)value;
> for (String key : vertex.getPropertyKeys()) {
> Object propertyValue = 
> GraphHelper.getProperty(vertex,  key);
> if (propertyValue != null) {
> oRow.put(key, propertyValue.toString());
> }
> }
> {code}
> look very similar. 
> However, 0.8 handles id in edges explicitly while the 0.7 doesn’t treat edges 
> explicitly at all.
> {code:java}
> else if(value instanceof AtlasEdge) {
> AtlasEdge edge = (AtlasEdge) value;
> oRow.put("id", edge.getId().toString());
> oRow.put("label", 

[jira] [Resolved] (ATLAS-1852) Create RelationshipDef

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1852.
-
   Resolution: Fixed
Fix Version/s: 0.9-incubating

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

> Create RelationshipDef
> --
>
> Key: ATLAS-1852
> URL: https://issues.apache.org/jira/browse/ATLAS-1852
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Reporter: David Radley
>Assignee: David Radley
> Fix For: 0.9-incubating
>
>
> Introduce relationshipDef: 
> 1) Creation 
> 2) Get by name
> 3) Return relationshipdefs as part of a get typeDefs call. 
> At this stage the relationshiDef is defined as a Vertex in the graph. 
> getbyguid is not working
> update has not been tested
> implementation needs to be changed to an edge. Needs to be similar to 
> existing composition relationships in the types graph.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1768) Create common types for Open Metadata

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1768:
-

bq. Is the plan that a query for historic state (e.g. what was the state on 4th 
January 2017) can be created from rolling forward through the JSON records?
Historic state stored in audit log contains all attribute values; however I 
think it doesn't include details like associated classifications/classification 
attributes. Perhaps we should look to enhance what gets stored in audit record.

> Create common types for Open Metadata
> -
>
> Key: ATLAS-1768
> URL: https://issues.apache.org/jira/browse/ATLAS-1768
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata
>
> This JIRA describes a proposal for standard types for open metadata entities 
> and relationships.  For example, glossaries, database definitions, rules, 
> policies, ...
> The value of having standard definitions for metadata is to enable type safe 
> APIs and business level UIs plus be able to exchange metadata between 
> different instances of metadata repositories.
> The implementation of these common types is divided into 8 areas:
> * Area 0 - for extensions to Apache Atlas's base model
> * Area 1 - for definitions of the data-related assets we are governing and 
> using
> * Area 2 - for a glossary of meanings and semantic relationships
> * Area 3 - for information about asset use, crowd-sourced definitions and 
> collaboration around the data-related assets
> * Area 4 - for governance such as policies, rules and classifications
> * Area 5 - for reference models and reference data
> * Area 6 - for metadata discovery processes (see 
> https://issues.apache.org/jira/browse/ATLAS-1748)
> * Area 7 - for lineage
> Adaptation and flexibility are key in metadata environments so these common 
> definitions must be extensible - and we still need to support the ad hoc 
> definition of new types in Atlas.
> Apache Atlas supports meta-types that are used in the definition of new 
> types.  These are currently enumeration, struct, classification and entity.  
> JIRA https://issues.apache.org/jira/browse/ATLAS-1690 adds relationships to 
> this list.  The open metadata models make use of all of these meta-types.  
> These are represented by sterotypes on the classes of the open metadata 
> definitions.
> The Atlas wiki has the models as a set of linked pages which are probably the 
> easiest way to view the models.
> Start here: 
> https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1768) Create common types for Open Metadata

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1768:
-

bq. no additional vertex is created. What would be the need to store the state 
in a vertex?
[~grahamwallis] I caused the above confusion, not [~mandy_chessell]! Let me 
clarify my question:
 - Is it necessary to store earlier entity states in vertices? Is it not enough 
to store earlier states in stringified-JSON format?

Please note that entire entity state might not be stored in a single vertex - 
like when the entity includes attributes that refer to struct or other 
entities. Struct value is stored in its own vertex, which is referenced by 
entity vertex via an edge. References to other entities (like a hive_table 
referencing a hive_db) are stored as edges.

> Create common types for Open Metadata
> -
>
> Key: ATLAS-1768
> URL: https://issues.apache.org/jira/browse/ATLAS-1768
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata
>
> This JIRA describes a proposal for standard types for open metadata entities 
> and relationships.  For example, glossaries, database definitions, rules, 
> policies, ...
> The value of having standard definitions for metadata is to enable type safe 
> APIs and business level UIs plus be able to exchange metadata between 
> different instances of metadata repositories.
> The implementation of these common types is divided into 8 areas:
> * Area 0 - for extensions to Apache Atlas's base model
> * Area 1 - for definitions of the data-related assets we are governing and 
> using
> * Area 2 - for a glossary of meanings and semantic relationships
> * Area 3 - for information about asset use, crowd-sourced definitions and 
> collaboration around the data-related assets
> * Area 4 - for governance such as policies, rules and classifications
> * Area 5 - for reference models and reference data
> * Area 6 - for metadata discovery processes (see 
> https://issues.apache.org/jira/browse/ATLAS-1748)
> * Area 7 - for lineage
> Adaptation and flexibility are key in metadata environments so these common 
> definitions must be extensible - and we still need to support the ad hoc 
> definition of new types in Atlas.
> Apache Atlas supports meta-types that are used in the definition of new 
> types.  These are currently enumeration, struct, classification and entity.  
> JIRA https://issues.apache.org/jira/browse/ATLAS-1690 adds relationships to 
> this list.  The open metadata models make use of all of these meta-types.  
> These are represented by sterotypes on the classes of the open metadata 
> definitions.
> The Atlas wiki has the models as a set of linked pages which are probably the 
> easiest way to view the models.
> Start here: 
> https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1768) Create common types for Open Metadata

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1768:
-

bq. Presumably when we create the new vertex we are not copying any 
relationships (edges) from the original to the new (chained) vertex.
I agree [~grahamwallis]. Copying the relationship edges to the earlier entity 
version vertex will make navigating the graph complicated.

[~mandy_chessell] - currently when an entity is updated, the entity state 
(including all attribute values) are copied in an audit record; however, no 
additional vertex is created. What would be the need to store the state in a 
vertex?

> Create common types for Open Metadata
> -
>
> Key: ATLAS-1768
> URL: https://issues.apache.org/jira/browse/ATLAS-1768
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata
>
> This JIRA describes a proposal for standard types for open metadata entities 
> and relationships.  For example, glossaries, database definitions, rules, 
> policies, ...
> The value of having standard definitions for metadata is to enable type safe 
> APIs and business level UIs plus be able to exchange metadata between 
> different instances of metadata repositories.
> The implementation of these common types is divided into 8 areas:
> * Area 0 - for extensions to Apache Atlas's base model
> * Area 1 - for definitions of the data-related assets we are governing and 
> using
> * Area 2 - for a glossary of meanings and semantic relationships
> * Area 3 - for information about asset use, crowd-sourced definitions and 
> collaboration around the data-related assets
> * Area 4 - for governance such as policies, rules and classifications
> * Area 5 - for reference models and reference data
> * Area 6 - for metadata discovery processes (see 
> https://issues.apache.org/jira/browse/ATLAS-1748)
> * Area 7 - for lineage
> Adaptation and flexibility are key in metadata environments so these common 
> definitions must be extensible - and we still need to support the ad hoc 
> definition of new types in Atlas.
> Apache Atlas supports meta-types that are used in the definition of new 
> types.  These are currently enumeration, struct, classification and entity.  
> JIRA https://issues.apache.org/jira/browse/ATLAS-1690 adds relationships to 
> this list.  The open metadata models make use of all of these meta-types.  
> These are represented by sterotypes on the classes of the open metadata 
> definitions.
> The Atlas wiki has the models as a set of linked pages which are probably the 
> easiest way to view the models.
> Start here: 
> https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ATLAS-1045) HiveHook fails to post metadata for "Create view" with "Relative path in absolute URI: NULL::character%20varying" exception

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1045.
-
Resolution: Duplicate

https://issues.apache.org/jira/browse/HIVE-14322

> HiveHook fails to post metadata for "Create view" with "Relative path in 
> absolute URI: NULL::character%20varying" exception
> ---
>
> Key: ATLAS-1045
> URL: https://issues.apache.org/jira/browse/ATLAS-1045
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.7-incubating
>Reporter: Ayub Pathan
>Assignee: Qiang Zhang
>Priority: Critical
>
> *Impact: No metadata for "create view" on atlas.*
> Steps to repro:
> {noformat}
> * create table sample (abc String);
> * create view sample_view_1 (url COMMENT 'URL of Referring page') AS  SELECT 
> * from sample;
> {noformat}
> Hiveserver2.log snapshot
> {noformat}
> 2016-07-23 17:28:24,371 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> hooks.ATSHook (ATSHook.java:(90)) - Created ATS Hook
> 2016-07-23 17:28:24,371 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> log.PerfLogger (PerfLogger.java:PerfLogBegin(148)) -  method=PostHook.org.apache.hadoop.hive.ql.hooks.ATSHook 
> from=org.apache.hadoop.hive.ql.Driver>
> 2016-07-23 17:28:24,371 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(176)) -  method=PostHook.org.apache.hadoop.hive.ql.hooks.ATSHook start=1469294904371 
> end=1469294904371 duration=0 from=org.apache.hadoop.hive.ql.Driver>
> 2016-07-23 17:28:24,372 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> log.PerfLogger (PerfLogger.java:PerfLogBegin(148)) -  method=PostHook.org.apache.atlas.hive.hook.HiveHook 
> from=org.apache.hadoop.hive.ql.Driver>
> 2016-07-23 17:28:24,372 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(176)) -  method=PostHook.org.apache.atlas.hive.hook.HiveHook start=1469294904372 
> end=1469294904372 duration=0 from=org.apache.hadoop.hive.ql.Driver>
> 2016-07-23 17:28:24,372 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> ql.Driver (Driver.java:execute(1635)) - Resetting the caller context to 
> HIVE_SSN_ID:8cc6511f-5454-431b-aa2f-d7a1c11159a7
> 2016-07-23 17:28:24,373 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(176)) -  method=Driver.execute start=1469294904326 end=1469294904373 duration=47 
> from=org.apache.hadoop.hive.ql.Driver>
> 2016-07-23 17:28:24,373 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> ql.Driver (SessionState.java:printInfo(939)) - OK
> 2016-07-23 17:28:24,373 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> log.PerfLogger (PerfLogger.java:PerfLogBegin(148)) -  method=releaseLocks from=org.apache.hadoop.hive.ql.Driver>
> 2016-07-23 17:28:24,373 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(176)) -  method=releaseLocks start=1469294904373 end=1469294904373 duration=0 
> from=org.apache.hadoop.hive.ql.Driver>
> 2016-07-23 17:28:24,373 INFO  [HiveServer2-Background-Pool: Thread-9870]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(176)) -  method=Driver.run start=1469294904233 end=1469294904373 duration=140 
> from=org.apache.hadoop.hive.ql.Driver>
> 2016-07-23 17:28:24,373 INFO  [Atlas Logger 1]: hook.HiveHook 
> (HiveHook.java:fireAndForget(202)) - Entered Atlas hook for hook type 
> POST_EXEC_HOOK operation CREATEVIEW
> 2016-07-23 17:28:24,374 INFO  [Atlas Logger 1]: metastore.HiveMetaStore 
> (HiveMetaStore.java:logInfo(822)) - 6: get_database: default
> 2016-07-23 17:28:24,374 INFO  [Atlas Logger 1]: HiveMetaStore.audit 
> (HiveMetaStore.java:logAuditEvent(391)) - 
> ugi=hive/nat-s11-4-kuls-atlas-1.openstacklo...@hwqe.hortonworks.com 
> ip=unknown-ip-addr  cmd=get_database: default
> 2016-07-23 17:28:24,380 INFO  [Atlas Logger 1]: metastore.HiveMetaStore 
> (HiveMetaStore.java:logInfo(822)) - 6: get_database: default
> 2016-07-23 17:28:24,380 INFO  [Atlas Logger 1]: HiveMetaStore.audit 
> (HiveMetaStore.java:logAuditEvent(391)) - 
> ugi=hive/nat-s11-4-kuls-atlas-1.openstacklo...@hwqe.hortonworks.com 
> ip=unknown-ip-addr  cmd=get_database: default
> 2016-07-23 17:28:24,385 INFO  [Atlas Logger 1]: bridge.HiveMetaStoreBridge 
> (HiveMetaStoreBridge.java:createOrUpdateDBInstance(161)) - Importing objects 
> from databaseName : default
> 2016-07-23 17:28:24,385 INFO  [Atlas Logger 1]: metastore.HiveMetaStore 
> (HiveMetaStore.java:logInfo(822)) - 6: get_table : db=default tbl=sample
> 2016-07-23 17:28:24,385 INFO  [Atlas Logger 1]: HiveMetaStore.audit 
> (HiveMetaStore.java:logAuditEvent(391)) - 
> ugi=hive/nat-s11-4-kuls-atlas-1.openstacklo...@hwqe.hortonworks.com 
> 

[jira] [Resolved] (ATLAS-1368) Knox query processing: If the originalUrl value has "ampersand"(&) in it, the value after ampersand is ignored.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1368.
-
Resolution: Duplicate

Fixed in https://issues.apache.org/jira/browse/KNOX-820

> Knox query processing: If the originalUrl value has "ampersand"(&) in it, the 
> value after ampersand is ignored.
> ---
>
> Key: ATLAS-1368
> URL: https://issues.apache.org/jira/browse/ATLAS-1368
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sharmadha Sainath
>Priority: Critical
>
> Example URL is: 
> knoxgateway:port/knoxsso/knoxauth/login.html?originalUrl=atlashost:21000/api/atlas/discovery/search/dsl?limit=25=hive_table
>  
> After providing the username and password, the above page gets redirected to 
> "atlashost:21000/api/atlas/discovery/search/dsl?limit=25", leaving 
> "query=hive_table". This seems to be an issue with knox query processing. 
> Original query:
> atlashost:21000/api/atlas/discovery/search/dsl?limit=25=hive_table  
> Redirects to 
> knoxgateway:port/knoxsso/knoxauth/login.html?originalUrl=atlashost:21000/api/atlas/discovery/search/dsl?limit=25=hive_table
>  
> Enclosed the URL 
> atlashost:21000/api/atlas/discovery/search/dsl?limit=25=hive_table with 
> double quotes and encoded it and gave it as original URL . Still it doesn't 
> work.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ATLAS-170) Result of search based on attributes of a Traits is not displayed correctly

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-170.

Resolution: Won't Fix

Currently Atlas doesn't support search by trait attribute values. This is one 
of the often asked features and will be considered for a future release.

> Result of search based on attributes of a Traits is not displayed correctly
> ---
>
> Key: ATLAS-170
> URL: https://issues.apache.org/jira/browse/ATLAS-170
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Herman Yu
>Priority: Blocker
>  Labels: ATLAS-UI-BUGS
> Attachments: screenshot-1.png
>
>
> when search based on an attribute of a trait, it returns the correct # of 
> entities found, but list of matched entities are not shown.
> for example, a traits ("mytrait") is defined with an attribute (myTraitAttr). 
> then associate this trait to an entity with "myvalue" as the value of the 
> attribute. When search with "mytrait.myTraitAttr="myvalue"", it returns 1 
> record matched, but doesn't show the entity in the list. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-170) Result of search based on attributes of a Traits is not displayed correctly

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-170:
---
 Environment: (was: HDP2.3.1)
Request participants:   (was: )

> Result of search based on attributes of a Traits is not displayed correctly
> ---
>
> Key: ATLAS-170
> URL: https://issues.apache.org/jira/browse/ATLAS-170
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Herman Yu
>Priority: Blocker
>  Labels: ATLAS-UI-BUGS
> Attachments: screenshot-1.png
>
>
> when search based on an attribute of a trait, it returns the correct # of 
> entities found, but list of matched entities are not shown.
> for example, a traits ("mytrait") is defined with an attribute (myTraitAttr). 
> then associate this trait to an entity with "myvalue" as the value of the 
> attribute. When search with "mytrait.myTraitAttr="myvalue"", it returns 1 
> record matched, but doesn't show the entity in the list. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ATLAS-637) Build fails (jenkins, local)

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-637.

Resolution: Cannot Reproduce

[~jonesn] - I am able to successfully build master & 0.8-incubating branches in 
Linux. Apache build also goes through successfully. Please reopen if you still 
see the issue.

> Build fails (jenkins, local)
> 
>
> Key: ATLAS-637
> URL: https://issues.apache.org/jira/browse/ATLAS-637
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Nigel Jones
>Priority: Blocker
>
> I am seeing the Atlas build fail when building the Web UI on 2 local (linux) 
> systems of mine. Whilst about to debug I noticed that Apache jenkins is also 
> reporting a build failure on the mailing list as reported at 
> news://news.gmane.org:119/579606293.2657.1459820983173.JavaMail.jenkins@crius
> The jenkins report seems very similar to mine, so I paste that below, and 
> will add further info from my local install attempt:
> See 
> Changes:
> [sumasai.shivaprasad] ATLAS-571 Modify Atlas client for necessary changes in 
> context of HA
> [sumasai.shivaprasad] ATLAS-607 Add Support for delete entity through a 
> qualifiedName (sumasai
> --
> [...truncated 5060 lines...]
> [ERROR] npm http 200 https://registry.npmjs.org/serve-static
> [ERROR] npm http 200 
> https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-1.0.0.tgz
> [ERROR] npm http 200 https://registry.npmjs.org/finalhandler/0.3.6
> [ERROR] npm http 304 https://registry.npmjs.org/escape-html/1.0.1
> [ERROR] npm http 304 https://registry.npmjs.org/etag
> [ERROR] npm http 200 https://registry.npmjs.org/content-disposition/0.5.0
> [ERROR] npm http GET https://registry.npmjs.org/ansi-regex
> [ERROR] npm http GET https://registry.npmjs.org/ansi-regex
> [ERROR] npm http GET https://registry.npmjs.org/get-stdin
> [ERROR] npm http 304 https://registry.npmjs.org/on-finished
> [ERROR] npm http GET 
> https://registry.npmjs.org/finalhandler/-/finalhandler-0.3.6.tgz
> [ERROR] npm http GET 
> https://registry.npmjs.org/serve-static/-/serve-static-1.9.3.tgz
> [ERROR] npm http GET 
> https://registry.npmjs.org/content-disposition/-/content-disposition-0.5.0.tgz
> [ERROR] npm http 304 https://registry.npmjs.org/parseurl
> [ERROR] npm http GET https://registry.npmjs.org/etag/-/etag-1.6.0.tgz
> [ERROR] npm http 200 https://registry.npmjs.org/qs/-/qs-2.4.2.tgz
> [ERROR] npm http 304 https://registry.npmjs.org/type-is
> [ERROR] npm http 304 https://registry.npmjs.org/vary
> [ERROR] npm http GET 
> https://registry.npmjs.org/on-finished/-/on-finished-2.2.1.tgz
> [ERROR] npm http 200 https://registry.npmjs.org/send/0.12.3
> [ERROR] npm http 304 https://registry.npmjs.org/utils-merge/1.0.0
> [ERROR] npm http 200 
> https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-0.1.3.tgz
> [ERROR] npm http 304 https://registry.npmjs.org/accepts
> [ERROR] npm http 200 https://registry.npmjs.org/depd/-/depd-1.0.1.tgz
> [ERROR] npm http GET https://registry.npmjs.org/send/-/send-0.12.3.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/content-disposition/-/content-disposition-0.5.0.tgz
> [ERROR] npm http 304 https://registry.npmjs.org/ansi-regex
> [ERROR] npm http 304 https://registry.npmjs.org/ansi-regex
> [ERROR] npm http 304 https://registry.npmjs.org/get-stdin
> [ERROR] npm http 200 https://registry.npmjs.org/etag/-/etag-1.6.0.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/on-finished/-/on-finished-2.2.1.tgz
> [ERROR] npm http 200 https://registry.npmjs.org/send/-/send-0.12.3.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/finalhandler/-/finalhandler-0.3.6.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/serve-static/-/serve-static-1.9.3.tgz
> [ERROR] npm http GET https://registry.npmjs.org/crc32-stream
> [ERROR] npm http GET https://registry.npmjs.org/node-int64
> [ERROR] npm http 200 https://registry.npmjs.org/node-int64
> [ERROR] npm http 200 https://registry.npmjs.org/crc32-stream
> [ERROR] npm http GET 
> https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz
> [ERROR] npm http GET 
> https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/crc32-stream/-/crc32-stream-0.3.4.tgz
> [ERROR] npm http 200 
> https://registry.npmjs.org/node-int64/-/node-int64-0.3.3.tgz
> [ERROR] npm http GET https://registry.npmjs.org/crc/3.2.1
> [ERROR] npm http GET https://registry.npmjs.org/ee-first/1.1.0
> [ERROR] npm http GET https://registry.npmjs.org/forwarded
> [ERROR] npm http GET https://registry.npmjs.org/ipaddr.js/1.0.5
> [ERROR] npm http GET https://registry.npmjs.org/negotiator/0.5.3
> [ERROR] npm http GET 

[jira] [Resolved] (ATLAS-1619) import-hive.sh script failure

[Madhan Neethiraj (JIRA)]

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

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

[~ssainath] - this issue doesn't reproduce any more. Please reopen if you see 
this issue with latest master/0.8-incubating branches.

> import-hive.sh script failure
> -
>
> Key: ATLAS-1619
> URL: https://issues.apache.org/jira/browse/ATLAS-1619
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Priority: Blocker
> Attachments: import-hive atlas logs.txt, import hive exception.txt
>
>
> 1. Disabled the hive hook
> 2. created hive_table in hive CLI
> 3. ran import-hive.sh script which ran fine.
> 4. Altered table in hive CLI and added new columns.
> 5. Ran import-hive.sh script. Import-hive.sh failed to take the update 
> throwing 404 exception.
> Attached the console logs on running import-hive and atlas logs. 
> Problems :
> 1. /logs/import-hive.log is not created.
> 2. Exceptions seen on console while executing the script and in 
> application.log are attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1848) UI- Remove json2.js library from atlas

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1848:

Description: Update Atlas to avoid using JSON licensed work; please refer 
to https://www.apache.org/legal/resolved#json for more details.

> UI- Remove json2.js library from atlas
> --
>
> Key: ATLAS-1848
> URL: https://issues.apache.org/jira/browse/ATLAS-1848
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-1848.patch
>
>
> Update Atlas to avoid using JSON licensed work; please refer to 
> https://www.apache.org/legal/resolved#json for more details.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ATLAS-1744) Error when searching type with attribute name "order" , "limit" , "offset"

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1744.
-
Resolution: Fixed

> Error when searching type with attribute name "order" , "limit" , "offset"
> --
>
> Key: ATLAS-1744
> URL: https://issues.apache.org/jira/browse/ATLAS-1744
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Suma Shivaprasad
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: OrderSearchError.txt
>
>
> 1.Created a type with attributes "order", "limit", "offset"
> 2.Created an entity for the type.
> 3.Searched 
> type where order="random" 
> which threw 500 internal server error with error notification
> {code}
> Discovery query failed type_entity where order ="random"
> {code}.
> Same exception when searching type with name "limit" and "offset"
> type where limit="upper"
> type where offset="middle"
> Attached the complete exception stack trace .



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ATLAS-1440) Inconsistency in DSL search of tag

[Madhan Neethiraj (JIRA)]

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

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

[~ssainath] - this issue could not be reproduced with the most recent build in 
master/0.8-incubating branches. I tried the following DSL queries:
- Asset where isa parent_tag
- Asset where isa child_tag

In both cases, UI returned a single entity where both tags were attached to. 
Can you please try again? This issue might have existed in pre-release 0.8 
builds; and might have been fixed with the updates for basic-search 
implementation.

> Inconsistency in DSL search of tag
> --
>
> Key: ATLAS-1440
> URL: https://issues.apache.org/jira/browse/ATLAS-1440
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Sharmadha Sainath
>Priority: Critical
> Attachments: parent_tag_response.txt, parent_tag_UI.png
>
>
> Created tags :
> 1. parent_tag
> 2. child_tag which has parent_tag has Parent tag
> 1.Associated child_tag to the hive_table . DSL query of both child_tag and 
> parent tag listed entity but GET response of hive_table had only child_tag
> This is reported in https://issues.apache.org/jira/browse/ATLAS-1439.
> 2. Associated parent_tag also to hive_table. DSL query response of parent_tag 
> returns hive_table twice. But UI response is empty.
> Attached the DSL query response of parent_tag and UI screenshot.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1819:

Affects Version/s: 0.8-incubating

> V2 APIs : Entity Resource GET query with classification returns 500.
> 
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ruchi Solani
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ArrayOutOfBoundsException.txt, ATLAS-1819.patch
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error. 
> {code}
> /api/atlas/v2/entity/guid//classification/tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the 
> unassociated tag throws 404 , else 500.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1819.
-
   Resolution: Fixed
Fix Version/s: 0.8.1-incubating
   0.9-incubating

Committed to the following branches:
 - master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/35c77644
 - 0.8-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/a3a59183

> V2 APIs : Entity Resource GET query with classification returns 500.
> 
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ruchi Solani
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ArrayOutOfBoundsException.txt, ATLAS-1819.patch
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error. 
> {code}
> /api/atlas/v2/entity/guid//classification/tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the 
> unassociated tag throws 404 , else 500.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1819:
-

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

> V2 APIs : Entity Resource GET query with classification returns 500.
> 
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: ArrayOutOfBoundsException.txt, ATLAS-1819.patch
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error. 
> {code}
> /api/atlas/v2/entity/guid//classification/tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the 
> unassociated tag throws 404 , else 500.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1812) On browser refresh if, tag is doesn't exist, then URL should update with the first tag.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1812:
-

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

> On browser refresh if, tag is doesn't exist, then URL should update with the 
> first tag.
> ---
>
> Key: ATLAS-1812
> URL: https://issues.apache.org/jira/browse/ATLAS-1812
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Attachments: ATLAS-1812.1.patch, ATLAS-1812.patch
>
>
> - While clicking on refresh button of tag tab if tag which is deleted from 
> other sessions and it is active from UI side, then the browser URL should 
> update with the first tag if available.
> - Above scenario should be happened for browser refresh, as well. 
> - If user type in tag-name into URL which does not exist in tag list,  then 
> the browser URL should update with the first tag if available.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1816) UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1816:
-

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

> UI,excludeDeletedEntities : Next button in Basic query result view is not 
> working if result query has DELETED entities
> --
>
> Key: ATLAS-1816
> URL: https://issues.apache.org/jira/browse/ATLAS-1816
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-1816.patch
>
>
> 1. Created 50 tables
> 2. Deleted 5 tables which are shown in the first page of the basic query 
> search.
> 3. Fired a basic query : type name = hive_table 
> 4. Page showed only 20 results. Because there were only 20 results , Next 
> button used to navigate to next page was disabled.
> 5. Checked the "Include historical entities" check box. 25 results displayed 
> but still Next button was disabled. 
> 6. Hence even if one DELETED entity is returned in the basic query , 
> navigation to next table becomes impossible.
> If all returned entities in the limit 25 are ACTIVE , Next button is enabled. 
> For example out of 150 entities , 5 entities are DELETED . Those DELETED 
> entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is 
> possible . From there on , even though "Include Historical entities"  is 
> checked and 25 results are returned for the page ,  next button is disabled.
> [ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the 
> reasons for this bug.
> Advanced(DSL) query result window is not suffering from this issue probably 
> because excludeDeletedEntities parameter is not honored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1807) Enhance DSL query to support "like" operator for wildcard searches

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1807:

   Affects Version/s: (was: 0.9-incubating)
  (was: trunk)
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating

> Enhance DSL query to support "like" operator for wildcard searches
> --
>
> Key: ATLAS-1807
> URL: https://issues.apache.org/jira/browse/ATLAS-1807
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1807.2.patch
>
>
> Current DSL search cannot do wildcard searches, this JIRA will introduce a 
> new operator in DSL for wildcard - "like"
> eg. 
> * hive_table where name like "employee*"
> * hive_column where qualifiedName like "defa?lt*"
> * hive_column where name like "loc*" and position=5 and qualifiedName like 
> "default.employee2*"



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1780) Type deletion blocks ability to redefine same type with different attribute

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1780:

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

> Type deletion blocks ability to redefine same type with different attribute
> ---
>
> Key: ATLAS-1780
> URL: https://issues.apache.org/jira/browse/ATLAS-1780
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.9-incubating, 0.8.1-incubating
>
>
> This change supports the use-case where the user creates a type and deletes 
> it sometime later, now the redefinition of the type is restricted to use the 
> same data type for the attributes used during the initial creation. 
> Solution: Rename the propertyKey corresponding to that attribute using the 
> titan management API by suffing _deleted_xxx where xxx is an increasing 
> integer sequence starting from 0. The reason for increment of xxx is that the 
> type create, delete and re-create can be done multiple times without any 
> conflicting key in Titan.
> Use case: Create a Tag/Trait with atleast one attribute, delete the tag, 
> recreate the exact same tag with a different data type for the attribute. 
> Creation will be a success, try associating the Tag/trait with any entity 
> with the attribute value (new data type) this should fail with a 
> ClassCastException



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1756) Allow user to edit associated Tag (classification)

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1756:

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

> Allow user to edit associated Tag (classification)
> --
>
> Key: ATLAS-1756
> URL: https://issues.apache.org/jira/browse/ATLAS-1756
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1756.1.patch, ATLAS-1756.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1777) UI : Include historical entities check box is not shown when searching a type with all DELETED entities, hence no entities are retrieved by search.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1777:

Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating

> UI : Include historical entities check box is not shown when searching a type 
> with all DELETED entities, hence no entities are retrieved by search.
> ---
>
> Key: ATLAS-1777
> URL: https://issues.apache.org/jira/browse/ATLAS-1777
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: all_DELETED_entities.png, one_ACTIVE_entity.png
>
>
> 1. Created a type and 10 entities of that type. 
> 2. Deleted 9 entities out of 10 .
> 3. In basic search , searched for the type which listed only one ACTIVE 
> entity. 
> 4. Checked the "Include historical entities" check box. It listed the 9 
> DELETED entities and 1 ACTIVE entity. (Attached the screenshot)
> 5. Now , deleted the last one ACTIVE entity of the type.(all entities of the 
> type are now DELETED)
> 6. Searched for the same type again. Results were empty since 
> excludeDeletedEntities=True is set by default.
> 7. Since there were no results, "Include historical entities" check box is 
> not shown at all.(Attached the screenshot) . Hence , there is now no way of 
> retrieving entities of the type in Basic search.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1776) Include historical entities in UI : A query is made and cancelled every time the check box is checked/unchecked showing "Invalid expression:null" notification

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1776:

Request participants:   (was: )
   Fix Version/s: (was: 0.8-incubating)
  0.8.1-incubating

> Include historical entities in UI : A query is made and cancelled every time 
> the check box is checked/unchecked showing "Invalid expression:null" 
> notification
> --
>
> Key: ATLAS-1776
> URL: https://issues.apache.org/jira/browse/ATLAS-1776
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1776.1.patch, ATLAS-1776.2.patch
>
>
> Steps to replicate :
> 1.In basic search , searched for type "hive_table".
> 2.Checked "Include historical entities" 
> 3. Unchecked it. At this time the following query is made twice :
> http://localhost:21000/api/atlas/v2/search/basic?limit=25=true=table
> first of the 2 queries is cancelled and Invalid Expression : null 
> notification pops up.
> Note : This happens only when clicking on the "Include historical entities" 
> text . On checking / unchecking the check box itself, no such extra queries 
> are made.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1759) UI - Add checkbox to exclude/include deleted entities in schema table.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1759:

Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating
  Issue Type: Improvement  (was: Bug)

> UI - Add checkbox to exclude/include deleted entities in schema table.
> --
>
> Key: ATLAS-1759
> URL: https://issues.apache.org/jira/browse/ATLAS-1759
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1759.1.patch, ATLAS-1759.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1770) HardDeleteHandlerV1Test and SoftDeleteHandlerV1Test failure during setup

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1770:

   Affects Version/s: (was: 0.9-incubating)
  0.8-incubating
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
 Description: 
org.apache.atlas.exception.AtlasBaseException: Given type OrgLevel already 
exists
at 
org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypeWithNoRefResolve(AtlasTypeRegistry.java:630)
at 
org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypesWithNoRefResolve(AtlasTypeRegistry.java:668)
at 
org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypes(AtlasTypeRegistry.java:405)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryTypeCreation(AtlasTypeDefGraphStore.java:896)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.createTypesDef(AtlasTypeDefGraphStore.java:301)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:51)
at 
org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test.setUp(AtlasDeleteHandlerV1Test.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at 
org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
at 
org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:173)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:105)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at 
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:129)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:113)
at 
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

  was:

org.apache.atlas.exception.AtlasBaseException: Given type OrgLevel already 
exists
at 
org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypeWithNoRefResolve(AtlasTypeRegistry.java:630)
at 
org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypesWithNoRefResolve(AtlasTypeRegistry.java:668)
at 
org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypes(AtlasTypeRegistry.java:405)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryTypeCreation(AtlasTypeDefGraphStore.java:896)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.createTypesDef(AtlasTypeDefGraphStore.java:301)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:51)
at 
org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test.setUp(AtlasDeleteHandlerV1Test.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 

[jira] [Updated] (ATLAS-855) Atlas logs contain stale transaction eviction message

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-855:
---
   Affects Version/s: (was: trunk)
Request participants:   (was: )
   Fix Version/s: (was: 0.8-incubating)
  (was: trunk)
  0.8.1-incubating

> Atlas logs contain stale transaction eviction message
> -
>
> Key: ATLAS-855
> URL: https://issues.apache.org/jira/browse/ATLAS-855
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Hemanth Yamijala
>Assignee: Sarath Subramanian
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: application.log.tar.gz, ATLAS-855.1.patch
>
>
> In situations that are hard to replicate, we are getting a message in the 
> Atlas server logs as follows:
> {code}
> Evicted [16@c0a801069313-hemanthijalambp-home1] from cache but waiting too 
> long for transactions to close. Stale transaction alert on: 
> [standardtitantx[null]] (ManagementLogger:189)
> {code}
> I started seeing this a lot more often with the business catalog delete 
> functionality (ATLAS-793), although it is not consistent with this.
> This jira is to track down the cause and fix it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1762) Specifying invalid types for superTypes , datatype throws 404 Not Found.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1762:

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

> Specifying invalid types for superTypes , datatype throws 404 Not Found.
> 
>
> Key: ATLAS-1762
> URL: https://issues.apache.org/jira/browse/ATLAS-1762
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.9-incubating, 0.8.1-incubating
>
>
> Following tests
> Creating a type with super type that doesn’t exist
> Updating a type with super type that doesn’t exist
> Creating a type with attribute of unknown data type
> throw 404 Not Found error. Expected is 400 Bad Request.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1730) Error after updating attribute's data type of an Atlas type

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1730:

   Affects Version/s: (was: 0.9-incubating)
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating

> Error after updating attribute's data type of an Atlas type 
> 
>
> Key: ATLAS-1730
> URL: https://issues.apache.org/jira/browse/ATLAS-1730
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
> Fix For: 0.9-incubating, 0.8.1-incubating
>
>
> 1.Created a type with one of its attributes' type as date and POSTed the type 
> definition to 
> {code}
> /api/atlas/v2/types/typedefs
> {code}
> 2. Tried to update the attribute data type to string , hence modified the 
> JSON (changed "date" to "string") and PUT the JSON to the same API which 
> succeeded.
> 3. Tried to create an entity of the type and provided "val1" as value for the 
> string attribute (which was updated from date).
> 4. Entity creation failed with
> {code}
> java.lang.ClassCastException: java.lang.Long cannot be cast to 
> java.lang.String
> {code}
> This could be a rare one but this scenario might cause issues when user 
> initially gave data type as "date" by mistake and wants to update it as 
> "string". 
> Also , since attribute delete is not allowed as part of type update , 
> attribute with "date" type can't be deleted and recreated with string.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1736) Type registration becomes inconsistent after creating a type with attribute name having special characters.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1736:

   Affects Version/s: (was: 0.9-incubating)
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating

> Type registration becomes inconsistent after creating a type with attribute 
> name having special characters.
> ---
>
> Key: ATLAS-1736
> URL: https://issues.apache.org/jira/browse/ATLAS-1736
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: SplCharInAttrName.txt
>
>
> Created a type with attribute name as "attribute$" (with special character $).
> 1.Type creation succeeded with 200 OK 
> 2.Null Pointer exception is seen in application logs 
> 3.Searching the type throws 500 Internal server error though the drop down 
> lists the type.
> 4. After creating such type , subsequent type creations are inconsistent. 
> (i.e) Type creation succeeds but Null pointer exception is thrown and 500 
> Internal server error while searching the type. 
> Attached the exception stack trace. 
> This issue is similar to https://issues.apache.org/jira/browse/ATLAS-1681.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1747) Difference in result of POSTing Structs to V1 APIs and V2 APIs

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1747:

   Affects Version/s: (was: 0.9-incubating)
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating

> Difference in result of POSTing Structs to V1 APIs and V2 APIs
> --
>
> Key: ATLAS-1747
> URL: https://issues.apache.org/jira/browse/ATLAS-1747
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: struct_V1_API_400_Bad_Req.txt, struct_V2_API_200_OK.txt
>
>
> Created a struct without attribute definitions.
> 1. POSTing it to V1 APIs threw 400 Bad Request with exception 
> {code}
> Caused by: java.lang.IllegalArgumentException: Collection Attribute 
> definitions is empty
> {code}
> 2. POSTing it to V2 APIs throws the above exception but struct is created 
> successfully.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1760) For rendering property tab use type definition of the entity

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1760:

Request participants:   (was: )

> For rendering property tab use type definition of the entity
> 
>
> Key: ATLAS-1760
> URL: https://issues.apache.org/jira/browse/ATLAS-1760
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1760.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1724) Exporting a non-existing entity results in success. Ideally, this should result in error.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1724:

Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating

> Exporting a non-existing entity results in success. Ideally, this should 
> result in error.
> -
>
> Key: ATLAS-1724
> URL: https://issues.apache.org/jira/browse/ATLAS-1724
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Ashutosh Mestry
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1724.patch
>
>
> Exporting a non-existing entity results in success. Ideally, this should 
> result in error.
> {noformat}
> apathan@Ayub-sys-101:~/Documents/ExportAPI/outputs > pj atlas-export-info.json
> {
> "clientIpAddress": "172.27.23.198",
> "hostName": "10.42.80.143",
> "metrics": {
> "duration": 368
> },
> "operationStatus": "SUCCESS",
> "request": {
> "itemsToExport": [
> {
> "typeName": "hive_db",
> "uniqueAttributes": {
> "qualifiedName": "db121@cl1"
> }
> }
> ]
> },
> "timeStamp": 1491635440500,
> "userName": "admin"
> }
> apathan@Ayub-sys-101:~/Documents/ExportAPI/outputs > pj atlas-typesdef.json
> {
> "classificationDefs": [],
> "entityDefs": [],
> "enumDefs": [],
> "structDefs": []
> }
> apathan@Ayub-sys-101:~/Documents/ExportAPI/outputs > pj 
> atlas-export-order.json
> []
> apathan@Ayub-sys-101:~/Documents/ExportAPI/outputs >
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1750:

   Affects Version/s: 0.8-incubating
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating

> Typeahead Search Implemented on create entity.
> --
>
> Key: ATLAS-1750
> URL: https://issues.apache.org/jira/browse/ATLAS-1750
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1750.1.patch, ATLAS-1750.2.patch, 
> ATLAS-1750.patch, ATLAS-1750-without-attrName-queryParam.patch
>
>
> Implement Typeahead search for the data type array of entity while creating 
> and updating entity.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1755) UI - Add checkbox to exclude deleted entities in basic and fulltext search

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1755:

   Affects Version/s: (was: 0.9-incubating)
  0.8-incubating
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  Issue Type: Improvement  (was: Bug)

> UI - Add checkbox to exclude deleted entities in basic and fulltext search
> --
>
> Key: ATLAS-1755
> URL: https://issues.apache.org/jira/browse/ATLAS-1755
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1755.1.patch, ATLAS-1755.2.patch, ATLAS-1755.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1761) Improve attribute search to enable search based on display text and guid

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1761:

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

> Improve attribute search to enable search based on display text and guid
> 
>
> Key: ATLAS-1761
> URL: https://issues.apache.org/jira/browse/ATLAS-1761
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1761.1.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1742) Provide option in server side to exclude deleted entities in basic and fulltext search

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1742:

   Affects Version/s: (was: 0.9-incubating)
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating

> Provide option in server side to exclude deleted entities in basic and 
> fulltext search
> --
>
> Key: ATLAS-1742
> URL: https://issues.apache.org/jira/browse/ATLAS-1742
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1742.1.patch
>
>
> Atlas UI needs to be enhanced to enable search on active entities in fulltext 
> and basic search. This JIRA addresses the backend changes needed to enable 
> this functionality.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1611) Regression: Incorrect error code for the negative tests. Returned: "500 server error", expected: "400 Bad Request"

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1611:

   Affects Version/s: (was: trunk)
Request participants:   (was: )

> Regression: Incorrect error code for the negative tests. Returned: "500 
> server error", expected: "400 Bad Request"
> --
>
> Key: ATLAS-1611
> URL: https://issues.apache.org/jira/browse/ATLAS-1611
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Sarath Subramanian
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1611.3.patch, ATLAS-1611.4.patch
>
>
> * *Scenario-1: Creating an entity with invalidGUID results in "500 server 
> error", expected response is "400 Bad Request"*
> Sample json when posted to atlas results in 500 internal error,
> {noformat}
>   {
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"invalid",
>   "version":0,
>   "typeName":"ComplexEntityTestColumnroshbaacqm",
>   "state":"ACTIVE"
> },
> "typeName":"ComplexEntityTestColumnroshbaacqm",
> "values":{
>   "name":"column1hlrfnjmmth"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
>   "createdBy":null,
>   "modifiedBy":null,
>   "createdTime":null,
>   "modifiedTime":null
> }
>   }
> {noformat}
> * *Scenario-2: Full update REST API call of an entity with request payload 
> having unsupported value for a type(for example: for float type value is set 
> as "str") results in "500 server error" but the expected response is "400 bad 
> request".*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1737) UI - Delete tag(classification) from UI.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1737:

Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating

> UI - Delete tag(classification) from UI.
> 
>
> Key: ATLAS-1737
> URL: https://issues.apache.org/jira/browse/ATLAS-1737
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1737.1.patch, ATLAS-1737.2.patch, 
> ATLAS-1737.3.patch, Atlas-1737 issue.png, ATLAS-1737.patch
>
>
> Ability to delete tag from UI using API 
> (api/atlas/v2/types/typedefs?type=classification) DELETE method.
> _Tags which are not assigned to any entity can be only deleted._



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1744) Error when searching type with attribute name "order" , "limit" , "offset"

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1744:

   Affects Version/s: (was: 0.9-incubating)
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating

> Error when searching type with attribute name "order" , "limit" , "offset"
> --
>
> Key: ATLAS-1744
> URL: https://issues.apache.org/jira/browse/ATLAS-1744
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Suma Shivaprasad
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: OrderSearchError.txt
>
>
> 1.Created a type with attributes "order", "limit", "offset"
> 2.Created an entity for the type.
> 3.Searched 
> type where order="random" 
> which threw 500 internal server error with error notification
> {code}
> Discovery query failed type_entity where order ="random"
> {code}.
> Same exception when searching type with name "limit" and "offset"
> type where limit="upper"
> type where offset="middle"
> Attached the complete exception stack trace .



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1751) Implement REST end-point to update classification attribute

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1751:

   Affects Version/s: (was: 0.9-incubating)
  0.8-incubating
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating

> Implement REST end-point to update classification attribute
> ---
>
> Key: ATLAS-1751
> URL: https://issues.apache.org/jira/browse/ATLAS-1751
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1751.1.patch
>
>
> Current REST implementation for classification supports only create and 
> delete classification associated with entities. This JIRA addresses update to 
> multiple classification attributes associated with entities.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1752) Atlas Group mapping for ranger doesn't work if using kerberos authentication

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1752:

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

> Atlas Group mapping for ranger doesn't work if using kerberos authentication
> 
>
> Key: ATLAS-1752
> URL: https://issues.apache.org/jira/browse/ATLAS-1752
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
> Environment: secure
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1752.patch
>
>
> {code}
> [DI50253@devbir1en3l ~]$ curl --negotiate -u : -X GET 
> "http://devbir1on5l:21000/api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f;
>  
>  
>  
>  
> Error 403 {AuthorizationError:You are not authorized 
> for READ on [ENTITY] : *} 
>  
> HTTP ERROR 403 
> Problem accessing 
> /api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f. Reason: 
>  {AuthorizationError:You are not authorized for READ 
> on [ENTITY] : *}Powered by 
> Jetty:// 
>  
>  
> I checked ID of the user and they belong to the group that is in ranger.
> If he uses ldap authentication then it group mapping works
> [DI50253@devbir1en3l ~]$ curl -u DI50253: -X GET 
> "http://devbir1on5l:21000/api/atlas/entities/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f;
>  
> {"requestId":"qtp1641313620-23 - 
> \/api\/atlas\/entities\/7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f - 
> 3f71704c-75e4-40dc-9796-4827e5997ea6","definition":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"7bb9c916-8fd3-40ef-b65f-855ed5bf4f9f","version":0,"typeName":"hive_db","state":"ACTIVE"},"typeName":"hive_db","values":{"name":"dz_1_disc","location":"hdfs:\/\/devbir1\/data\/discovery\/dz_1\/disc","description":null,"ownerType":{"value":"USER","ordinal":1},"qualifiedName":"dz_1_disc@devbir1","owner":"hive","clusterName":"devbir1","parameters":null},"traitNames":[],"traits":{}}}
>  
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1680) Support for browser login using kerberos kytab

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1680:

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

> Support for browser login using kerberos kytab
> --
>
> Key: ATLAS-1680
> URL: https://issues.apache.org/jira/browse/ATLAS-1680
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1680.patch
>
>
> After following the steps mentioned in the below link
> https://ping.force.com/Support/PingFederate/Integrations/How-to-configure-supported-browsers-for-Kerberos-NTLM
> Browser login using kerberos keytab is not going through.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1745) Font Usage: Attribution Missing

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1745:

   Affects Version/s: (was: trunk)
Request participants:   (was: )
   Fix Version/s: (was: trunk)
  0.8.1-incubating
  0.9-incubating

> Font Usage: Attribution Missing
> ---
>
> Key: ATLAS-1745
> URL: https://issues.apache.org/jira/browse/ATLAS-1745
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
>  Labels: license
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1707.2.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> To resolve ATLAS-1707 the fonts were made inline to CSS. The LICENSE for 
> usage is missing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1726) Creating type name with space causes exceptions while doing DSL search

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1726:

   Affects Version/s: (was: 0.9-incubating)
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating

> Creating type name with space causes exceptions while doing DSL search
> --
>
> Key: ATLAS-1726
> URL: https://issues.apache.org/jira/browse/ATLAS-1726
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1726.1.patch
>
>
> 1.Created a type "type 1" successfully
> 2.Searched the type "type 1" in Basic search which worked fine.
> 3.Same type when selected in drop down list of types in DSL , failed with 500 
> internal server error with exception :
> {code}
> org.apache.atlas.query.Expressions$UnresolvedException: Unresolved datatype. 
> Can not resolve due to unresolved children, expression: type where 1
> {code}
> 4. If typename is provided as `type 1` in "Search by Query" text box (with 
> backquotes) like mentioned in https://issues.apache.org/jira/browse/ATLAS-263 
> , it works fine.
> User might perceive that the type is not registered properly due to the 
> exception.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1707) Atlas WUI on continues loading behind FireWall

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1707:

Request participants:   (was: )
   Fix Version/s: (was: 0.8-incubating)
  0.8.1-incubating

> Atlas WUI on continues loading behind FireWall
> --
>
> Key: ATLAS-1707
> URL: https://issues.apache.org/jira/browse/ATLAS-1707
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.7-incubating
> Environment: Atlas: Version":"0.7.0.2.5.3
> JDK 1.8
> Linux
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Nixon Rodrigues
>  Labels: patch, test
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1707.2.patch, ATLAS-1707.3.patch, 
> ATLAS-1707.patch, index.html, index.html.original
>
>
> Atlas is behind a FW in which does return a response. We Identify index.html 
> was loading googleapis css does not have a timeout and proceed with the WUI;
> ref:http://tinyurl.com/lan4by9 
> By removing the bellow line from the html file, there were no problem. 
>  href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic;
>  rel="stylesheet" type="text/css">
> 1. Shouldn't be applications self-contain in case of such situation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1710) Implement entity-lookup API for entity create/update UI

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1710:

   Affects Version/s: (was: 0.9-incubating)
  (was: trunk)
  0.8-incubating
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating
  Issue Type: Improvement  (was: Bug)

> Implement entity-lookup API for entity create/update UI
> ---
>
> Key: ATLAS-1710
> URL: https://issues.apache.org/jira/browse/ATLAS-1710
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
>
> Implement the entity-lookup API



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1735) Coverity Scan Issues Detected on 4/13

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1735:

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

> Coverity Scan Issues Detected on 4/13
> -
>
> Key: ATLAS-1735
> URL: https://issues.apache.org/jira/browse/ATLAS-1735
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1735-Coverity-Scan-fixes.patch
>
>
>Please find the latest report on new defect(s) introduced to Apache Atlas 
> found with Coverity Scan.
> 
> 6 new defect(s) introduced to Apache Atlas found with Coverity Scan.
> 1 defect(s), reported by Coverity Scan earlier, were marked fixed in the 
> recent build analyzed by Coverity Scan.
> 
> New defect(s) Reported-by: Coverity Scan
> Showing 6 of 6 defect(s)
> 
> 
> ** CID 161397:  Null pointer dereferences  (NULL_RETURNS)
> /common/src/main/java/org/apache/atlas/utils/AuthenticationUtil.java: 57 
> in org.apache.atlas.utils.AuthenticationUtil.getBasicAuthenticationInput()()
> 
> 
> 
> 
> *** CID 161397:  Null pointer dereferences  (NULL_RETURNS)
> /common/src/main/java/org/apache/atlas/utils/AuthenticationUtil.java: 57 
> in org.apache.atlas.utils.AuthenticationUtil.getBasicAuthenticationInput()()
> 51 String username = null;
> 52 String password = null;
> 53
> 54 try {
> 55 Console console = System.console();
> 56 username = console.readLine("Enter username for atlas 
> :- ");
> >>> CID 161397:  Null pointer dereferences  (NULL_RETURNS)
> >>> Dereferencing a pointer that might be null 
> "console.readPassword("Enter password for atlas :- ")" when calling "String".
> 57 password = new String(console.readPassword("Enter 
> password for atlas :- "));
> 58 } catch (Exception e) {
> 59 System.out.print("Error while reading ");
> 60 System.exit(1);
> 61 }
> 62 return new String[]{username, password};
> 63 }
> 64
> 
> ** CID 161396:  Null pointer dereferences  (NULL_RETURNS)
> 
> /repository/src/test/java/org/apache/atlas/repository/impexp/ZipFileResourceTestUtils.java:
>  148 in 
> org.apache.atlas.repository.impexp.ZipFileResourceTestUtils.runAndVerifyQuickStart_v1_Import(org.apache.atlas.repository.impexp.ImportService,
>  org.apache.atlas.repository.impexp.ZipSource)()
> 
> 
> 
> 
> *** CID 161396:  Null pointer dereferences  (NULL_RETURNS)
> 
> /repository/src/test/java/org/apache/atlas/repository/impexp/ZipFileResourceTestUtils.java:
>  148 in 
> org.apache.atlas.repository.impexp.ZipFileResourceTestUtils.runAndVerifyQuickStart_v1_Import(org.apache.atlas.repository.impexp.ImportService,
>  org.apache.atlas.repository.impexp.ZipSource)()
> 142 AtlasImportResult result = importService.run(source, 
> request, userName, hostName, requestingIP);
> 143 Assert.assertEquals(result.getOperationStatus(), 
> AtlasImportResult.OperationStatus.SUCCESS);
> 144 return result;
> 145 }
> 146
> 147 public static void 
> runAndVerifyQuickStart_v1_Import(ImportService importService, ZipSource 
> zipSource) throws AtlasBaseException, IOException {
> >>> CID 161396:  Null pointer dereferences  (NULL_RETURNS)
> >>> Assigning: "exportResult" = null return value from 
> "getExportResult".
> 148 AtlasExportResult exportResult = 
> zipSource.getExportResult();
> 149 List creationOrder = zipSource.getCreationOrder();
> 150
> 151 AtlasImportRequest request = getDefaultImportRequest();
> 152 AtlasImportResult result = 
> runImportWithParameters(importService, request, zipSource);
> 153
> 
> ** CID 161395:  Null pointer dereferences  (NULL_RETURNS)
> 
> /repository/src/test/java/org/apache/atlas/repository/impexp/ExportServiceTest.java:
>  256 in 
> 

[jira] [Updated] (ATLAS-1709) Export & Import API: Unit Tests

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1709:

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

> Export & Import API: Unit Tests
> ---
>
> Key: ATLAS-1709
> URL: https://issues.apache.org/jira/browse/ATLAS-1709
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1709-IX-Unit-tests.patch
>
>
> Import & Export API functionality should be verifiable via unit tests.
> Unit tests should cover following areas:
> * _ZipSink_
> * _ZipSource_
> * _ExportService_
> * _ImportService_



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1719) Tag association UI should allow users to input value for enum type attributes from a drop-down

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1719:

   Affects Version/s: (was: 0.9-incubating)
  0.8-incubating
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  Issue Type: Improvement  (was: Bug)

>  Tag association UI should allow users to input value for enum type 
> attributes from a drop-down
> ---
>
> Key: ATLAS-1719
> URL: https://issues.apache.org/jira/browse/ATLAS-1719
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1719.1.patch, ATLAS-1719.patch
>
>
> Tag association UI should allow users to input value for enum type attributes 
> from a drop-down.
> Ex. For hive_principal_type enum type drop-down should shown { USER, ROLE, 
> GROUP }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1718) In Create tag UI, attribute datatype should provide enum-types in drop-down along with built-in types

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1718:

   Affects Version/s: (was: 0.9-incubating)
  0.8-incubating
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  Issue Type: Improvement  (was: Bug)

> In Create tag UI, attribute datatype should provide enum-types in drop-down 
> along with built-in types
> -
>
> Key: ATLAS-1718
> URL: https://issues.apache.org/jira/browse/ATLAS-1718
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1718.1.patch, ATLAS-1718.patch
>
>
>  In Create/update tag UI, attribute datatype should provide enum-types in 
> drop-down along with built-in types. ( like hive_principal_type, file_action)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1717) Export & Import API: Documentation

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1717:

   Affects Version/s: (was: trunk)
Request participants:   (was: )
   Fix Version/s: (was: trunk)
  0.8.1-incubating
  0.9-incubating

> Export & Import API: Documentation
> --
>
> Key: ATLAS-1717
> URL: https://issues.apache.org/jira/browse/ATLAS-1717
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1717-IX-Documentation.patch
>
>
> Update documentation to include Export & Import REST APIs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1727) Mask userdetails in quick Start utility

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1727:

   Affects Version/s: 0.8-incubating
Request participants:   (was: )
   Fix Version/s: 0.8.1-incubating
  0.9-incubating

> Mask userdetails in quick Start utility 
> 
>
> Key: ATLAS-1727
> URL: https://issues.apache.org/jira/browse/ATLAS-1727
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1727.patch
>
>
> Quick Start utility requires username and password.
> Its better to hide the password part of it



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1721) Import Process: Audit Do Not Have Information About Import

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1721:

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

> Import Process: Audit Do Not Have Information About Import
> --
>
> Key: ATLAS-1721
> URL: https://issues.apache.org/jira/browse/ATLAS-1721
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1721-Import-Audit.patch
>
>
> Steps to duplicate:
> - Perform an import using REST APIs.
> - Log in to Atlas Web UI.
> - Search for the imported entity and display the details page and open the 
> 'Audit' tab.
> Expected: Audits should have information that says that it was created via 
> import process.
> Observed: Audit show that entity was created.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1732) After Zoom_out from Lineage view scroll stopped working

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1732:

Fix Version/s: 0.8.1-incubating

> After Zoom_out from Lineage view scroll stopped working
> ---
>
> Key: ATLAS-1732
> URL: https://issues.apache.org/jira/browse/ATLAS-1732
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1732.patch
>
>
> Steps to reproduce.
> * Collapse Lineage window.
> * Then click on zoom-in button
> * Then click on zoom-out button
> After performing the above step you will see scroll stopped working. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1433) Atlas allows creation of tag with attributes' name same as that of its parent tags.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1433:

Affects Version/s: 0.8-incubating

> Atlas allows creation of tag with attributes' name same as that of its parent 
> tags.
> ---
>
> Key: ATLAS-1433
> URL: https://issues.apache.org/jira/browse/ATLAS-1433
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1433.1.patch, ATLAS-1433.patch
>
>
> Created a tag parent_tag with attributes name and id. Created an other tag 
> child_tag inheriting from parent_tag .  And gave attribute names for 
> child_tag same as that of parent_tag. child_tag is successfully created.
> Associated child_tag to an entity. Atlas UI prompts values for 4 attributes 
> as :
> name :
> id: 
> name:
> id:
> Values provided for last set of name ,id are finally assigned to the tag 
> associated for the entity.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1433) Atlas allows creation of tag with attributes' name same as that of its parent tags.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1433:

Fix Version/s: 0.8.1-incubating
   0.9-incubating

> Atlas allows creation of tag with attributes' name same as that of its parent 
> tags.
> ---
>
> Key: ATLAS-1433
> URL: https://issues.apache.org/jira/browse/ATLAS-1433
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1433.1.patch, ATLAS-1433.patch
>
>
> Created a tag parent_tag with attributes name and id. Created an other tag 
> child_tag inheriting from parent_tag .  And gave attribute names for 
> child_tag same as that of parent_tag. child_tag is successfully created.
> Associated child_tag to an entity. Atlas UI prompts values for 4 attributes 
> as :
> name :
> id: 
> name:
> id:
> Values provided for last set of name ,id are finally assigned to the tag 
> associated for the entity.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1714:

Affects Version/s: (was: 0.9-incubating)
   0.8-incubating

> UI : Properties tab doesn't load when an entity has attribute of type array 
> of integers 
> 
>
> Key: ATLAS-1714
> URL: https://issues.apache.org/jira/browse/ATLAS-1714
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1714.patch
>
>
> Created a type with array of integers as on of its attributes :
> {code}
>   { 
>"name":"type_set_int",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"array",
>"valuesMaxCount":1,
>"cardinality":"SET",
>"valuesMinCount":0
> }
> {code}
> Created an entity of the type with value for type_set_int as [1,2,3]. Entity 
> is created with 200 OK.
> Following exception is thrown in console tab :
> {code}
> Uncaught TypeError: inputOutputField.indexOf is not a function
> at http://172.27.16.74:21000/js/utils/CommonViewFunction.js:148:46
> at Array.map (native)
> at Object.CommonViewFunction.propertyTable 
> (http://172.27.16.74:21000/js/utils/CommonViewFunction.js:129:39)
> at n.entityTableGenerate 
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:68:48)
> at n.onRender 
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:56:22)
> at 
> http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:7823
> at n.triggerMethod 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:20703)
> at n.render 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:21699)
> at n.render 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:30148)
> at constructor.show 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:11890)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1714:

Fix Version/s: 0.8.1-incubating
   0.9-incubating

> UI : Properties tab doesn't load when an entity has attribute of type array 
> of integers 
> 
>
> Key: ATLAS-1714
> URL: https://issues.apache.org/jira/browse/ATLAS-1714
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1714.patch
>
>
> Created a type with array of integers as on of its attributes :
> {code}
>   { 
>"name":"type_set_int",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"array",
>"valuesMaxCount":1,
>"cardinality":"SET",
>"valuesMinCount":0
> }
> {code}
> Created an entity of the type with value for type_set_int as [1,2,3]. Entity 
> is created with 200 OK.
> Following exception is thrown in console tab :
> {code}
> Uncaught TypeError: inputOutputField.indexOf is not a function
> at http://172.27.16.74:21000/js/utils/CommonViewFunction.js:148:46
> at Array.map (native)
> at Object.CommonViewFunction.propertyTable 
> (http://172.27.16.74:21000/js/utils/CommonViewFunction.js:129:39)
> at n.entityTableGenerate 
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:68:48)
> at n.onRender 
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:56:22)
> at 
> http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:7823
> at n.triggerMethod 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:20703)
> at n.render 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:21699)
> at n.render 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:30148)
> at constructor.show 
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:11890)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1673) Type deletion not working as expected

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1673:

Fix Version/s: 0.8.1-incubating

> Type deletion not working as expected
> -
>
> Key: ATLAS-1673
> URL: https://issues.apache.org/jira/browse/ATLAS-1673
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.8-incubating, 0.9-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1673.patch
>
>
> When a type (wihout any references/instances) is deleted, the transient 
> registry still retains it and leads to inconsistent data. This forbids 
> recreation of the same type as long as the server is active and not restarted.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1697) import-hive.sh script logs debug/info logs on console instead of import-hive.log log file.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1697:

Fix Version/s: 0.8.1-incubating

> import-hive.sh script logs debug/info logs on console instead of 
> import-hive.log  log file.
> ---
>
> Key: ATLAS-1697
> URL: https://issues.apache.org/jira/browse/ATLAS-1697
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1697.patch, atlas-log4j.xml, import-hive.sh
>
>
> Found the issue of hive import script logs not being appended to log file. 
> For import-hive the log file path of import-hive.log  is configured in script 
> and the logs should append to this log file. 
> Log file for import is /usr/hdp/current/atlas-server/logs/import-hive.log  
> But the atlas-log4j.xml referenced from class-path is from typesystem module 
> in which it is mentioned to output debug logs on console and also do not not 
> have file appender in it. 
> {noformat}
> log4j: Using URL 
> [jar:file:/grid/0/hdp/2.6.0.0-598/atlas/hook/hive/atlas-hive-plugin-impl/atlas-typesystem-0.8.0.2.6.0.0-598.jar!/atlas-log4j.xml]
>  for automatic log4j configuration.
> 
> 
> 
> 
> {noformat}
> The fix for appending logs in 
> /usr/hdp/current/atlas-server/logs/import-hive.log  file.
> # change the typesystem module atlas-log.xml and add log appender tag but it 
> cannot be edited since it packaged in jar
> # referer to /etc/atlas/conf/atlas-log4j.xml but macros *\{atlas.log.file\}*  
> and *\{atlas.log.dir\}* in this file are already expanded and also the file 
> may not be present on server where hive is running. 
> # Have a copy 
> [atlas-log4j.xml|https://github.com/apache/incubator-atlas/blob/master/typesystem/src/main/resources/atlas-log4j.xml]
>  for import hive and update path in import-hive.sh to use this 
> atlas-log4j.xml [ This is workaround if hit by this issue ]
> {noformat}
> JAVA_PROPERTIES="$ATLAS_OPTS -Datlas.log.dir=$ATLAS_LOG_DIR 
> -Datlas.log.file=import-hive.log -Dlog4j.configuration=atlas-log4j.xml"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1686) Import API fails with "com.esotericsoftware.kryo.KryoException: Class cannot be created (missing no-arg constructor): java.util.Collections$UnmodifiableSet"

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1686:

Fix Version/s: 0.8.1-incubating

> Import API fails with "com.esotericsoftware.kryo.KryoException: Class cannot 
> be created (missing no-arg constructor): 
> java.util.Collections$UnmodifiableSet"
> 
>
> Key: ATLAS-1686
> URL: https://issues.apache.org/jira/browse/ATLAS-1686
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Ashutosh Mestry
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: application.log, ATLAS-1686.patch, default_res.zip
>
>
> Importing the attached zip file for hiveDB type results in below exceptions.
> *First try resulted in below exception*
> {noformat}
> 2017-03-27 11:23:10,419 ERROR - [pool-2-thread-9 - 
> 7817471f-de23-47e8-bbd3-a1edd3d05c06:hrt_qa:POST/api/atlas/admin/import] ~ 
> Error handling a request: 875da67cba3c17ae (ExceptionMapperUtil:32)
> org.apache.atlas.exception.AtlasBaseException: 
> org.apache.atlas.exception.AtlasBaseException: invalid parameters: entity: 
> 269b5610-7be4-4a14-b264-395bb1172aa6, already associated with classification: 
> trait_gqjdehhtnn
>   at 
> org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:372)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)
>   at 
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)
>   at 
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)
>   at 
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
>   at 
> org.apache.atlas.web.filters.ActiveServerFilter.doFilter(ActiveServerFilter.java:82)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:78)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> org.apache.atlas.web.filters.StaleTransactionCleanupFilter.doFilter(StaleTransactionCleanupFilter.java:56)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> 

[jira] [Updated] (ATLAS-1688) Resize Lineage window will move legend out of the Lineage panel

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1688:

Fix Version/s: 0.8.1-incubating

> Resize Lineage window will move legend out of the Lineage panel
> ---
>
> Key: ATLAS-1688
> URL: https://issues.apache.org/jira/browse/ATLAS-1688
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1688.2.patch, ATLAS-1688.3.patch, 
> ATLAS-1688.patch, Lineage_out_of_the_panel.png, tooltip.png
>
>
> 1 ) In Detail page of entity try to resize the panel of Lineage it will move 
> both Legend and graph out of the panel.
> 2 ) Tool tip size is too big it should have scroll inside it.
> I have attached the screen shot for better understanding.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1685) Fix coverity scan issues found in latest report

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1685:

Fix Version/s: 0.8.1-incubating

> Fix coverity scan issues found in latest report
> ---
>
> Key: ATLAS-1685
> URL: https://issues.apache.org/jira/browse/ATLAS-1685
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1685.1.patch
>
>
>   ** CID 161144:  Null pointer dereferences  (NULL_RETURNS)
> 
> /repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java:
>  267 in 
> org.apache.atlas.discovery.EntityDiscoveryService.searchUsingBasicQuery(java.lang.String,
>  java.lang.String, java.lang.String, int, int)()
> 
> 
> 
> 
> *** CID 161144:  Null pointer dereferences  (NULL_RETURNS)
> 
> /repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java:
>  267 in 
> org.apache.atlas.discovery.EntityDiscoveryService.searchUsingBasicQuery(java.lang.String,
>  java.lang.String, java.lang.String, int, int)()
> 261
> 262 bindings.put("startIdx", params.offset());
> 263 bindings.put("endIdx", params.offset() + 
> params.limit());
> 264
> 265 basicQuery += 
> gremlinQueryProvider.getQuery(AtlasGremlinQuery.TO_RANGE_LIST);
> 266
> >>> CID 161144:  Null pointer dereferences  (NULL_RETURNS)
> >>> Assigning: "scriptEngine" = null return value from 
> "getGremlinScriptEngine".
> 267 ScriptEngine scriptEngine = 
> graph.getGremlinScriptEngine();
> 268
> 269 try {
> 270 Object result = 
> graph.executeGremlinScript(scriptEngine, bindings, basicQuery, false);
> 271
> 272 if (result instanceof List && 
> CollectionUtils.isNotEmpty((List) result)) {
> 
> ** CID 161143:  Null pointer dereferences  (NULL_RETURNS)
> 
> /graphdb/titan0/src/main/java/org/apache/atlas/repository/graphdb/titan0/Titan0Graph.java:
>  329 in 
> org.apache.atlas.repository.graphdb.titan0.Titan0Graph.executeGremlinScript(java.lang.String)()
> 
> 
> 
> 
> *** CID 161143:  Null pointer dereferences  (NULL_RETURNS)
> 
> /graphdb/titan0/src/main/java/org/apache/atlas/repository/graphdb/titan0/Titan0Graph.java:
>  329 in 
> org.apache.atlas.repository.graphdb.titan0.Titan0Graph.executeGremlinScript(java.lang.String)()
> 323
> 324 private Object executeGremlinScript(String gremlinQuery) 
> throws ScriptException {
> 325 Object   result = null;
> 326 ScriptEngine engine = getGremlinScriptEngine();
> 327
> 328 try {
> >>> CID 161143:  Null pointer dereferences  (NULL_RETURNS)
> >>> Calling a method on null object "engine".
> 329 Bindings bindings = engine.createBindings();
> 330
> 331 bindings.put("g", getGraph());
> 332
> 333 result = engine.eval(gremlinQuery, bindings);
> 334 } finally {



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1687) Upgrade: hbase_column_family and hbase_column are not loaded into Atlas, even though hbase model json has it.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1687:

Fix Version/s: 0.8.1-incubating

> Upgrade: hbase_column_family and hbase_column are not loaded into Atlas, even 
> though hbase model json has it.
> -
>
> Key: ATLAS-1687
> URL: https://issues.apache.org/jira/browse/ATLAS-1687
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Sarath Subramanian
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: BUG-78102.2.patch
>
>
> Atlas is installed on a cluster and the cluster is upgraded.
> hbase_column_family and hbase_column are not found in the 
> /api/atlas/v2/types/typedefs/headers response in the upgraded cluster.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1681) Atlas went into inconsistent state after creating a type with faulty definition

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1681:

Fix Version/s: 0.8.1-incubating
   0.9-incubating

> Atlas went into inconsistent state after creating a type with faulty 
> definition
> ---
>
> Key: ATLAS-1681
> URL: https://issues.apache.org/jira/browse/ATLAS-1681
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: EmptyAttrNameInTypeDef.txt
>
>
> Created an entity type with one of its attribute name empty with the 
> following definition with the following JSON:
> {code}
> {
>"structDefs":[
>],
>"entityDefs":[
>   {
>  "category":"ENTITY",
>  "updateTime":12345,
>  "name":"entity_incorrect",
>  "typeVersion":"0.1",
>  "attributeDefs":[
> {
>"name":"type_str",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"string",
>"valuesMaxCount":1,
>"cardinality":"SINGLE",
>"valuesMinCount":0
> },
> {
>"name":"",
>"typeName":"int",
>"isOptional":true,
>"cardinality":"SINGLE",
>"valuesMinCount":-1,
>"valuesMaxCount":-1,
>"isUnique":false,
>"isIndexable":false
> }
>  ],
>  "superTypes":[
>  ],
>  "version":12345,
>  "guid":"-48964f25979it51334479",
>  "createTime":12345,
>  "description":"incorrect json"
>   }
>],
>"classificationDefs":[
>],
>"enumDefs":[
>]
> }
> {code}
> *Note the second attribute name in the attribute definition*
> POSTed the type definition to
> {code}
> /api/atlas/v2/types/typedefs
> {code}
> The type is created ,with 200 OK but with exception 
> {code}
> java.lang.IllegalArgumentException: Attribute name cannot be empty
> {code}
> (Attached the complete stack trace as a file)
> Inconsistency Observed :
> 1. Types drop down box lists the type entity_incorrect , but clicking on it 
> throws "Invalid Expression" exception
>  
> 2. Therafter ,any type creation (entity type , classification etc) is 
> succeeding with 200 OK but application.log has exception :
> {code}
> org.apache.atlas.query.Expressions$UnresolvedException: Unresolved id, 
> expression: entity_correct
> {code}
> Example :
> After POSTing the incorrect json to Atlas , created a tag tag_after in UI . 
> It succeeded. But Search of tag throws invalid expression and tag Association 
> to entity fails with  
> {code}
> org.apache.atlas.exception.AtlasBaseException: 
> org.apache.atlas.repository.RepositoryException: 
> org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown 
> datatype: tag_after
> {code}
> Type registration is affected when Atlas accepts the wrong JSON.
> Giving an empty attribute name is not a very common scenario but at what 
> conditions such wrong JSONs could be accepted should be looked at.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1684) Export/import: export should include super-type definitions, import should preserve system attribute values

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1684:

Fix Version/s: 0.8.1-incubating

> Export/import: export should include super-type definitions, import should 
> preserve system attribute values
> ---
>
> Key: ATLAS-1684
> URL: https://issues.apache.org/jira/browse/ATLAS-1684
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1684.patch
>
>
> When type of the entity exported has super-types, the type-def of the 
> super-types are not included in the exported file. This can cause the import 
> to fail, if these types are not present in the instance.
> For imported entities, the system attribute values (create-time, 
> modified-type, created-by, modified-by, status) should be preserved as in the 
> exported file (i.e. source system).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1660) Regression : Error code mismatch in while GETing a type that doesn't exist.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1660:

Fix Version/s: 0.8.1-incubating

> Regression : Error code mismatch in while GETing a type that doesn't exist.
> ---
>
> Key: ATLAS-1660
> URL: https://issues.apache.org/jira/browse/ATLAS-1660
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1660.1.patch
>
>
> Querying for a type that doesn't exist results in 400 [Bad Request] . It 
> should be 404 [Not Found] .
> Both V1 and V2 APIs return 400 .
> {code}
> /api/atlas/types/unknowntype
> /api/atlas/v2/types/typedef/name/unknowntype
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1682) UI updates for lineage label and issue in toggling between basic & advanced search

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1682:

Fix Version/s: 0.8.1-incubating

> UI updates for lineage label and issue in toggling between basic & advanced 
> search
> --
>
> Key: ATLAS-1682
> URL: https://issues.apache.org/jira/browse/ATLAS-1682
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1682.patch
>
>
> Patch contain following changes.
> # Added Overlay Loader in all Tables.
> # Heading change from Lineage to LINEAGE & IMPACT
> # While adding attributes if any input is empty and user clicks on add button 
> it will close popup with warning message and wont add any attribute.
> # Click on "..." button from list of Tags it will redirect to Basic search 
> page.
> # Click on  "..." button will search for tag with old type selected issue.
> # Clicking on refresh button of Search Tab will refresh search table view 
> also. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1663) Fix defects reported by Coverity Scan

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1663:

Fix Version/s: 0.8.1-incubating

> Fix defects reported by Coverity Scan
> -
>
> Key: ATLAS-1663
> URL: https://issues.apache.org/jira/browse/ATLAS-1663
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1663.1.patch
>
>
> Please find the latest report on new defect(s) introduced to Apache Atlas 
> found with Coverity Scan.
> 
> 3 new defect(s) introduced to Apache Atlas found with Coverity Scan.
> 1 defect(s), reported by Coverity Scan earlier, were marked fixed in the 
> recent build analyzed by Coverity Scan.
> 
> New defect(s) Reported-by: Coverity Scan
> Showing 3 of 3 defect(s)
> 
> 
> ** CID 157015:  Null pointer dereferences  (NULL_RETURNS)
> 
> /graphdb/titan0/src/main/java/org/apache/atlas/repository/graphdb/titan0/Titan0Graph.java:
>  293 in 
> org.apache.atlas.repository.graphdb.titan0.Titan0Graph.getGremlinScriptEngine()()
> 
> 
> 
> 
> *** CID 157015:  Null pointer dereferences  (NULL_RETURNS)
> 
> /graphdb/titan0/src/main/java/org/apache/atlas/repository/graphdb/titan0/Titan0Graph.java:
>  293 in 
> org.apache.atlas.repository.graphdb.titan0.Titan0Graph.getGremlinScriptEngine()()
> 287 @Override
> 288 public ScriptEngine getGremlinScriptEngine() {
> 289 ScriptEngineManager manager = new ScriptEngineManager();
> 290 ScriptEngineengine  = 
> manager.getEngineByName("gremlin-groovy");
> 291
> 292 //Do not cache script compilations due to memory 
> implications
> >>> CID 157015:  Null pointer dereferences  (NULL_RETURNS)
> >>> Calling a method on null object "engine".
> 293 
> engine.getContext().setAttribute("#jsr223.groovy.engine.keep.globals", 
> "phantom", ScriptContext.ENGINE_SCOPE);
> 294
> 295 return engine;
> 296 }
> 297
> 298 @Override
> 
> ** CID 157014:  Null pointer dereferences  (FORWARD_NULL)
> 
> /webapp/src/main/java/org/apache/atlas/web/security/AtlasLdapAuthenticationProvider.java:
>  75 in 
> org.apache.atlas.web.security.AtlasLdapAuthenticationProvider.authenticate(org.springframework.security.core.Authentication)()
> 
> 
> 
> 
> *** CID 157014:  Null pointer dereferences  (FORWARD_NULL)
> 
> /webapp/src/main/java/org/apache/atlas/web/security/AtlasLdapAuthenticationProvider.java:
>  75 in 
> org.apache.atlas.web.security.AtlasLdapAuthenticationProvider.authenticate(org.springframework.security.core.Authentication)()
> 69
> 70 @Override
> 71 public Authentication authenticate(Authentication 
> authentication)
> 72 throws AuthenticationException {
> 73 try {
> 74 authentication = 
> getLdapBindAuthentication(authentication);
> >>> CID 157014:  Null pointer dereferences  (FORWARD_NULL)
> >>> Comparing "authentication" to null implies that "authentication" 
> might be null.
> 75 if (authentication != null && 
> authentication.isAuthenticated()) {
> 76 return authentication;
> 77 } else {
> 78 authentication = 
> getLdapAuthentication(authentication);
> 79 if (authentication != null && 
> authentication.isAuthenticated()) {
> 80 return authentication;
> 
> ** CID 157013:  Null pointer dereferences  (FORWARD_NULL)
> /webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java: 426 in 
> org.apache.atlas.web.rest.EntityREST.createOrUpdate(org.apache.atlas.model.instance.AtlasEntity$AtlasEntitiesWithExtInfo)()
> 
> 
> 
> 
> *** CID 157013:  Null pointer dereferences  (FORWARD_NULL)
> /webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java: 426 in 
> org.apache.atlas.web.rest.EntityREST.createOrUpdate(org.apache.atlas.model.instance.AtlasEntity$AtlasEntitiesWithExtInfo)()
> 420 @Produces(Servlets.JSON_MEDIA_TYPE)
> 421 public EntityMutationResponse 
> createOrUpdate(AtlasEntitiesWithExtInfo 

[jira] [Updated] (ATLAS-1676) HDFS path entity created by Hive hook has no value for hdfs_path.clusterName attribute

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1676:

Fix Version/s: 0.8.1-incubating

> HDFS path entity created by Hive hook has no value for hdfs_path.clusterName 
> attribute
> --
>
> Key: ATLAS-1676
> URL: https://issues.apache.org/jira/browse/ATLAS-1676
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1676.patch
>
>
> HDFS path entities created by Atlas Hive hook does not have any value 
> assigned to clusterName attribute. This attribute should be set to value 
> similar to Falcon and Storm hooks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1675) In HA mode , tag created in Active Server not present in new Active server after failover.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1675:

Fix Version/s: 0.8.1-incubating

> In HA mode , tag created in Active Server not present in new Active server 
> after failover.
> --
>
> Key: ATLAS-1675
> URL: https://issues.apache.org/jira/browse/ATLAS-1675
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1675.patch
>
>
> A)
> 1.host1 , host2 both are up and host1 is ACTIVE.
> 2.Created a tag when host1 is ACTIVE and tag creation is successful .
> 3.Did a manual failover. 
> 4.Now host2 is ACTIVE and host1 is PASSIVE.
> *same tag is not present in host2*
> B) :
> 1. host1 is up and host2 is down.
> 2.Created tag in host1 . 
> 3.Started host2
> 4.brought down host1 and started host1 (just to make host2 ACTIVE)
> 5.*Now tag is present in host2 and host1*
> This happens only for tag . For entities created through hook or UI , entity 
> persists in both hosts in both scenarios. (Verified with hive_table created 
> through hook and an hdfs_path created in UI)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1671) Client IP is not populated for Atlas service in audit tab of Ranger

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1671:

Fix Version/s: 0.8.1-incubating

> Client IP is not populated for Atlas service in audit tab of Ranger
> ---
>
> Key: ATLAS-1671
> URL: https://issues.apache.org/jira/browse/ATLAS-1671
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
> Environment: Atlas with ranger plugin on
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1671.patch, atlas_client_IP.png
>
>
> Client IP is not populated for Atlas service in audit tab of Ranger, refer 
> attached image
>  
> !atlas_client_IP.png|width=300,height=300!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1672) Coverity Scan Issues Detected on 3/18

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1672:

Fix Version/s: 0.8.1-incubating

> Coverity Scan Issues Detected on 3/18
> -
>
> Key: ATLAS-1672
> URL: https://issues.apache.org/jira/browse/ATLAS-1672
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 0.9-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1672-Coverity Scan-3-18.patch
>
>
> 2 new defect(s) introduced to Apache Atlas found with Coverity Scan.
> New defect(s) Reported-by: Coverity Scan
> Showing 2 of 2 defect(s)
> ** CID 160099:  Null pointer dereferences  (NULL_RETURNS)
> /repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityChangeNotifier.java:
>  234 in 
> org.apache.atlas.repository.store.graph.v1.AtlasEntityChangeNotifier.updateFullTextMapping(java.lang.String,
>  java.util.List)()
> 
> *** CID 160099:  Null pointer dereferences  (NULL_RETURNS)
> /repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityChangeNotifier.java:
>  234 in 
> org.apache.atlas.repository.store.graph.v1.AtlasEntityChangeNotifier.updateFullTextMapping(java.lang.String,
>  java.util.List)()
> 228 LOG.warn("Unable to determine if FullText is disabled. 
> Proceeding with FullText mapping");
> 229 }
> 230
> 231 if (StringUtils.isEmpty(entityId) || 
> CollectionUtils.isEmpty(classifications)) {
> 232 return;
> 233 }
>  CID 160099:  Null pointer dereferences  (NULL_RETURNS)
>  Assigning: "atlasVertex" = null return value from "findByGuid".
> 234 AtlasVertex atlasVertex = 
> AtlasGraphUtilsV1.findByGuid(entityId);
> 235
> 236 try {
> 237 String classificationFullText = 
> fullTextMapperV2.getIndexTextForClassifications(entityId, classifications);
> 238 String existingFullText = (String) 
> GraphHelper.getProperty(atlasVertex, Constants.ENTITY_TEXT_PROPERTY_KEY);
> 239
> ** CID 160098:  Null pointer dereferences  (NULL_RETURNS)
> /webapp/src/main/java/org/apache/atlas/web/resources/ZipSource.java: 199 in 
> org.apache.atlas.web.resources.ZipSource.getEntity(java.lang.String)()
> 
> *** CID 160098:  Null pointer dereferences  (NULL_RETURNS)
> /webapp/src/main/java/org/apache/atlas/web/resources/ZipSource.java: 199 in 
> org.apache.atlas.web.resources.ZipSource.getEntity(java.lang.String)()
> 193 return null;
> 194 }
> 195 }
> 196
> 197 private AtlasEntity getEntity(String guid) throws 
> AtlasBaseException {
> 198 if(guidEntityJsonMap.containsKey(guid)) {
>  CID 160098:  Null pointer dereferences  (NULL_RETURNS)
>  Calling a method on null object "getEntityWithExtInfo(guid)".
> 199 return getEntityWithExtInfo(guid).getEntity();
> 200 }
> 201
> 202 return null;
> 203 }
> 204



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1664) Able to add already added tag to an entity through REST API

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1664:

Fix Version/s: 0.8.1-incubating
   0.9-incubating

> Able to add already added tag to an entity through REST API
> ---
>
> Key: ATLAS-1664
> URL: https://issues.apache.org/jira/browse/ATLAS-1664
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1664.2.patch
>
>
> Created a tag and POSTed using V1 APIs :
> {code}
> /api/atlas/entities/guid/traits
> {code}
> POST json :
> {code}
> {
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
>   "typeName":"tag2",
>   "values":{
> "name":"abc"
>   }
> }
> {code}
> The tag is associated. POSTed the same JSON again . Request succeeded with 
> 201 Created. Audits tab also has a Tag Added Event for tag being added for 
> the second time.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1670) Fix for IT failures introduced due to ATLAS-1664

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1670:

Fix Version/s: 0.8.1-incubating
   0.9-incubating

> Fix for IT failures introduced due to ATLAS-1664
> 
>
> Key: ATLAS-1670
> URL: https://issues.apache.org/jira/browse/ATLAS-1670
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1670.1.patch
>
>
> One of the IT - EntityV2JerseyResourceIT.testSubmitEntity() was re-adding the 
> same classifications. ATLAS-1664 restricts adding duplicate tags for the same 
> entity. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1659) FullText V2 mapping after adding/removing traits

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1659:

Fix Version/s: 0.8.1-incubating

> FullText V2 mapping after adding/removing traits
> 
>
> Key: ATLAS-1659
> URL: https://issues.apache.org/jira/browse/ATLAS-1659
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1659.patch
>
>
> Currently any addition/removal of traits doesn't trigger the full text remap.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1469) User provided values for tag attributes should be evaluated for its data type.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1469:

Fix Version/s: 0.8.1-incubating

> User provided values for tag attributes should be evaluated for its data type.
> --
>
> Key: ATLAS-1469
> URL: https://issues.apache.org/jira/browse/ATLAS-1469
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1469.patch
>
>
> Type verification is not done for Tag's attribute values . If no values are 
> given , data type's corresponding values like 0 for int , null for string are 
> taken. But type is not checked when users provide values. For example , 
> "value1" for int is accepted ,but value at the end is 0 for the attribute. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1470) Tag is not associated to an entity when incorrect value for byte type is provided.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1470:

Fix Version/s: 0.8.1-incubating

> Tag is not associated to an entity when incorrect value for byte type is 
> provided.
> --
>
> Key: ATLAS-1470
> URL: https://issues.apache.org/jira/browse/ATLAS-1470
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha Sainath
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1470.1.patch, byte_with_string_value.txt
>
>
> Unlike other data types, when incorrect value like "value1" is provided for 
> an attribute of type byte, the tag is not associated to the entitiy. No 
> errors/warnings are shown in UI.
> Attached the exception stack trace which reports number format exception.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1668) Exclude terms from tags UI - add-tag popup, search-page dropdown and assign-tag popup

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1668:

Fix Version/s: 0.8.1-incubating

> Exclude terms from tags UI - add-tag popup, search-page dropdown and 
> assign-tag popup
> -
>
> Key: ATLAS-1668
> URL: https://issues.apache.org/jira/browse/ATLAS-1668
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1668.patch
>
>
> (filing on behalf of [~kevalbhatt])
> Exclude terms from the following UI that shows tags:
>  - add-tag popup
>  - search-page dropdown
>  - assign-tag popup



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1669) Remove unused classes

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1669:

Fix Version/s: 0.8.1-incubating

> Remove unused classes
> -
>
> Key: ATLAS-1669
> URL: https://issues.apache.org/jira/browse/ATLAS-1669
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1669.patch
>
>
> Files XMLPropertiesUtil.java and ModelDefinitionDump.java are unused and 
> should be removed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1666) Improve on Overly Broad Throws

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1666:

Fix Version/s: 0.8.1-incubating

> Improve on Overly Broad Throws
> --
>
> Key: ATLAS-1666
> URL: https://issues.apache.org/jira/browse/ATLAS-1666
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1666.1.patch, ATLAS-1666.patch
>
>
> Methods in the following classes throws generic exception. This makes it hard 
> for callers to effectively handle errors and recover. Although, this does not 
> impact functionality. It would be valuable to improve on this.
> Below is a files that have this pattern: 
> 1. _ActiveInstanceState.java_
> 2. _AbstractParam.java_
> 3. _QuickStart.java_
> 4. _SetupSteps.java_
> 5. _FalconHook.java_
> 6. _AtlasLdapAuthenticationProvider.java_
> 7. _FalconEventPublisher.java_
> 8. _AtlasADAuthenticationProvider.java_
> 9. _StormHook.java_
> 10. _FalconBridge.java_
> 11. _EmbeddedServer.java_
> 12. _StormTopologyUtil.java_
> 13. _SqoopHook.java_
> 14. _HiveHook.java_
> 15. _HiveMetaStoreBridge.java_
> General approach to refactoring would be define an error code in 
> _AtlasErrorCode_ and throw _AtlasBaseException_.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1503) Export/import support to copy data between Atlas instances

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1503:

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

> Export/import support to copy data between Atlas instances
> --
>
> Key: ATLAS-1503
> URL: https://issues.apache.org/jira/browse/ATLAS-1503
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Ashutosh Mestry
>  Labels: patch
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1503.2.patch, ATLAS-1503.7.patch, 
> ATLAS-1503-Import.2.patch, ATLAS-1503-Import-Optimized.patch, 
> ATLAS-1630.4.patch
>
>
> One of the often asked feature is the ability to export data stored in Atlas 
> (entity, lineage, tag-association, types) and import the exported data into 
> another Atlas instance. This feature should support the ability to export 
> specified list of objects, along with their associated objects, tags and 
> type. For example, if a hive_db named "finance" is specified, export should 
> include the following:
> - hive_db entity along with its tags
> - all tables in this database and their tags
> - all columns in above tables and their tags
> - the lineage information associated with above entities
> - type-defintion of all above entities
> During import, if an exported entity is not present in the target Atlas, it 
> should be created. If the entity already exists at the target (by guid or by 
> unique attribute value), the entity should be updated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1611) Regression: Incorrect error code for the negative tests. Returned: "500 server error", expected: "400 Bad Request"

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1611:

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

> Regression: Incorrect error code for the negative tests. Returned: "500 
> server error", expected: "400 Bad Request"
> --
>
> Key: ATLAS-1611
> URL: https://issues.apache.org/jira/browse/ATLAS-1611
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Sarath Subramanian
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1611.3.patch, ATLAS-1611.4.patch
>
>
> * *Scenario-1: Creating an entity with invalidGUID results in "500 server 
> error", expected response is "400 Bad Request"*
> Sample json when posted to atlas results in 500 internal error,
> {noformat}
>   {
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"invalid",
>   "version":0,
>   "typeName":"ComplexEntityTestColumnroshbaacqm",
>   "state":"ACTIVE"
> },
> "typeName":"ComplexEntityTestColumnroshbaacqm",
> "values":{
>   "name":"column1hlrfnjmmth"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
>   "createdBy":null,
>   "modifiedBy":null,
>   "createdTime":null,
>   "modifiedTime":null
> }
>   }
> {noformat}
> * *Scenario-2: Full update REST API call of an entity with request payload 
> having unsupported value for a type(for example: for float type value is set 
> as "str") results in "500 server error" but the expected response is "400 bad 
> request".*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1813) UI to escape special characters in URL.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1813:

Fix Version/s: 0.8.1-incubating

> UI to escape special characters in URL.
> ---
>
> Key: ATLAS-1813
> URL: https://issues.apache.org/jira/browse/ATLAS-1813
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1813.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1813) UI to escape special characters in URL.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1813:
-

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

> UI to escape special characters in URL.
> ---
>
> Key: ATLAS-1813
> URL: https://issues.apache.org/jira/browse/ATLAS-1813
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-1813.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1771) Atlas UI - While deleting Tag the Confirmation Popup appears incorrectly in IE-9

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1771:
-

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

> Atlas UI - While deleting Tag the Confirmation Popup appears incorrectly in 
> IE-9
> 
>
> Key: ATLAS-1771
> URL: https://issues.apache.org/jira/browse/ATLAS-1771
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
> Environment: Browser - IE-9
>Reporter: Nixon Rodrigues
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1771.patch, SS3.jpg
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1690) Introduce top level relationships

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1690:
-

>From [~davidrad]:
bq. I think the propagated classifications would be derived at query time and 
could be useful -do we need an effective classification?
I am not suggesting to materialize (i.e. copy) the propagated tags - that will 
add unnecessary complexity in dealing with tag attribute value changes, 
relationship changes, etc. Deriving the propagated tags dynamically when 
looking at (or retreiving) entity details would be a good choice.

bq. do we need an effective classification?
I think what is the "effective classification" is better left to the consumer 
of the tags of an entity. The requirement might vary, depending on how the tags 
are used. The example you detailed is one use case: to use of classification 
"level" to determine the effective classification. There could be other ways to 
pick the effective classification.

>From Atlas API perspective, I think we should make it clear which tags are 
>directly associated with the entity being retrieved and which ones come via 
>propagation.

bq. I wonder whether a smarter approach would be to tag the relationship as 
"propagate-1-to-2" (hopefully something more meaningful like 
propogate-table-to-column") and Ranger picks up this hint. Ranger could decide 
to run a simple rule of propagating all the tags from 1 to 2 or a more complex 
rule taking other conditions into account.
Wouldn't this require Ranger to know about all the entities, relationships and 
the propagation rules in Atlas? And a way to navigate them easily? This might 
be easier in Atlas, give we use Graph DB; but for consumer's of Atlas 
entity/tags, it might not be practical.  Also, I think it will be good to see 
both tags and propagated-tags in Atlas UI - which would require Atlas to deal 
with propagation logic. Given this, I think it will be useful to make this 
information available via Atlas API.

> Introduce top level relationships
> -
>
> Key: ATLAS-1690
> URL: https://issues.apache.org/jira/browse/ATLAS-1690
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
> Attachments: Atlas_RelationDef_Json_Structure_v1.pdf, Atlas 
> Relationships proposal v1.0.pdf, Atlas Relationships proposal v1.1.pdf, Atlas 
> Relationships proposal v1.2.pdf, Atlas Relationships proposal v1.3.pdf, Atlas 
> Relationships proposal v1.4.pdf, Atlas Relationships proposal v1.5.pdf, Atlas 
> Relationships proposal v1.6.pdf, Atlas Relationships proposal v1.7.pdf
>
>
> Introduce top level relationships including support for 
> -many to many relationships
> - relationship names including the name for both ends and the relationship.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1690) Introduce top level relationships

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1690:
-

On earlier comment from [~cmgrote]:

bq. What about "propagatesTags" being an enum rather than a simple boolean, 
e.g. "FROM-TO", "TO-FROM", "BI-DIRECTIONAL"; in case there are scenarios where 
it would make sense to apply the super-set of tags (from both sides of the 
relationship)?
Yes. This is a good idea and will be very helpful. For example, in case of 
synonym relationship between terms, tags associated with either end of the 
relationship might be applicable to terms at each end. I think one of the enum 
value should be "NONE" - to handle the cases where tags shouldn't be propagated.

> Introduce top level relationships
> -
>
> Key: ATLAS-1690
> URL: https://issues.apache.org/jira/browse/ATLAS-1690
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
> Attachments: Atlas_RelationDef_Json_Structure_v1.pdf, Atlas 
> Relationships proposal v1.0.pdf, Atlas Relationships proposal v1.1.pdf, Atlas 
> Relationships proposal v1.2.pdf, Atlas Relationships proposal v1.3.pdf, Atlas 
> Relationships proposal v1.4.pdf, Atlas Relationships proposal v1.5.pdf, Atlas 
> Relationships proposal v1.6.pdf, Atlas Relationships proposal v1.7.pdf
>
>
> Introduce top level relationships including support for 
> -many to many relationships
> - relationship names including the name for both ends and the relationship.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-855) Atlas logs contain stale transaction eviction message

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-855:


+1 for the patch. Please commit this fix in 0.8-incubating branch as well.

> Atlas logs contain stale transaction eviction message
> -
>
> Key: ATLAS-855
> URL: https://issues.apache.org/jira/browse/ATLAS-855
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.8-incubating
>Reporter: Hemanth Yamijala
>Assignee: Sarath Subramanian
>Priority: Critical
> Fix For: trunk, 0.9-incubating
>
> Attachments: application.log.tar.gz, ATLAS-855.1.patch
>
>
> In situations that are hard to replicate, we are getting a message in the 
> Atlas server logs as follows:
> {code}
> Evicted [16@c0a801069313-hemanthijalambp-home1] from cache but waiting too 
> long for transactions to close. Stale transaction alert on: 
> [standardtitantx[null]] (ManagementLogger:189)
> {code}
> I started seeing this a lot more often with the business catalog delete 
> functionality (ATLAS-793), although it is not consistent with this.
> This jira is to track down the cause and fix it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1690) Introduce top level relationships

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1690:
-

Ref: [~davidrad]'s earlier comment:
bq. 1. I do not think we should have "to" and "from". This implies a direction.
"to" and "from" may not be appropriate in all relationships. Perhaps we can 
name it as "endPoint1" and "endPoint2"?

bq. 2. I am wondering about the use case for a relationship to have more than 
one type. We can allow more than one type here if there is a compelling use 
case.
A single type should be good enough for now. If case for more than one type 
comes up, we can review it then.


> Introduce top level relationships
> -
>
> Key: ATLAS-1690
> URL: https://issues.apache.org/jira/browse/ATLAS-1690
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
> Attachments: Atlas_RelationDef_Json_Structure_v1.pdf, Atlas 
> Relationships proposal v1.0.pdf, Atlas Relationships proposal v1.1.pdf, Atlas 
> Relationships proposal v1.2.pdf, Atlas Relationships proposal v1.3.pdf, Atlas 
> Relationships proposal v1.4.pdf, Atlas Relationships proposal v1.5.pdf, Atlas 
> Relationships proposal v1.6.pdf, Atlas Relationships proposal v1.7.pdf
>
>
> Introduce top level relationships including support for 
> -many to many relationships
> - relationship names including the name for both ends and the relationship.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1690) Introduce top level relationships

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1690:
-

bq. Ideally propagation of tags should be defined in Ranger rules - as we are 
likely to want different tag propagation in different contexts
For a consumer to handle tag-propagation, they would need to know of the 
complex relationship between entities - which might end up having to duplicate 
much of data in Atlas (and keep them in sync constantly). Let us review few 
usecases:
- when a table/column is classified as PII, any lineage from this 
table/view/column should also be automatically be classified as PII
- when a term is classified as PII, all entities that are associated with the 
term also should automatically be classified as PII
- when a term is classified as PII, all terms that are synonym of this term 
(and all the entities associated with the synonym terms) also should 
automatically be classified as PII

I think pushing such propagation to the consumers, like Ranger, would require 
them to understand the complex relationship between various entities. Given 
such propagations can be handled naturally in a graph DB, it will be cleaner to 
have this piece owned by Atlas. We can enhance the API for the consumer, to 
provide 'propagated-tags' along with entities own tags - for example by adding 
member 'propagatedClassifications' as shown below:

{code}
public class AtlasEntity {
  // ...
  List   classifications;
  List propagatedClassifications;
}

public class AtlasPropagatedClassification {
  String  guidPropagatedFrom; // reference to the entity where the 
classification was attached to
  AtlasClassification classification;
}
{code}

CC: [~abhayk]

> Introduce top level relationships
> -
>
> Key: ATLAS-1690
> URL: https://issues.apache.org/jira/browse/ATLAS-1690
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
> Attachments: Atlas_RelationDef_Json_Structure_v1.pdf, Atlas 
> Relationships proposal v1.0.pdf, Atlas Relationships proposal v1.1.pdf, Atlas 
> Relationships proposal v1.2.pdf, Atlas Relationships proposal v1.3.pdf, Atlas 
> Relationships proposal v1.4.pdf, Atlas Relationships proposal v1.5.pdf, Atlas 
> Relationships proposal v1.6.pdf, Atlas Relationships proposal v1.7.pdf
>
>
> Introduce top level relationships including support for 
> -many to many relationships
> - relationship names including the name for both ends and the relationship.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (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:comment-tabpanel=15995158#comment-15995158
 ] 

Madhan Neethiraj commented on ATLAS-1763:
-

[~Kalyanikashikar] - after deleting a tag, can UI trigger a cache-refresh - 
which can help address this issue?

> 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: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Trivial
>
> 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
(v6.3.15#6346)