Re: Review Request 71738: ATLAS-3517: Enhance suggestions REST API to have optional 'fieldName' parameter to get suggestions from

2019-11-07 Thread Madhan Neethiraj 

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


Fix it, then Ship it!





repository/src/main/java/org/apache/atlas/discovery/SuggestionsProviderImpl.java
Lines 48 (patched)


Consider handing fieldName==null here, with:
  String indexFieldName = (fieldName == null) ? null : 
typeRegistry.getIndexFieldName(fieldName);


- Madhan Neethiraj


On Nov. 8, 2019, 3:35 a.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/71738/
> ---
> 
> (Updated Nov. 8, 2019, 3:35 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Aadarsh Jajodia, Sridhar K, Le Ma, 
> Madhan Neethiraj, Mandar Ambawane, Nikhil Bonte, Nixon Rodrigues, Sameer 
> Shaikh, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-3517
> https://issues.apache.org/jira/browse/ATLAS-3517
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Suggestions REST API searches against all indexed fields (terms) to retrieve 
> the top frequently used terms.
> 
> we don't have a way to retrieve suggestions only from a specific indexed 
> field.
> 
> This enhancement introduces a new optional parameter in suggestions API - 
> 'fieldName', which when specified will provide suggestions against that 
> indexed field name.
> 
>  
> 
> This will be useful to get suggestions on only a specific field - say labels 
> 
> 
> *Solution:*
> 
> Solr already provides a way to search on etrms against a specific field.
> 
> https://lucene.apache.org/solr/guide/6_6/the-terms-component.html
> 
> "terms.fl=" need to added as part of the request to solr 
> client on terms search
> 
> 
> Diffs
> -
> 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraphIndexClient.java
>  09a88d930 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraphIndexClient.java
>  278ec5db1 
>   
> intg/src/main/java/org/apache/atlas/model/discovery/AtlasSuggestionsResult.java
>  054ea2e87 
>   
> repository/src/main/java/org/apache/atlas/discovery/AtlasDiscoveryService.java
>  3feae27b5 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java
>  23fd7e9c5 
>   
> repository/src/main/java/org/apache/atlas/discovery/SuggestionsProvider.java 
> 4ee1b13a9 
>   
> repository/src/main/java/org/apache/atlas/discovery/SuggestionsProviderImpl.java
>  c00a65066 
>   webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java 908ae7033 
> 
> 
> Diff: https://reviews.apache.org/r/71738/diff/1/
> 
> 
> Testing
> ---
> 
> Precommit: 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1535/console
> 
> Manually validated that suggestions api filters based on provided field name.
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

[jira] [Commented] (ATLAS-3504) Regression: DSL query with "like" clause returns unexpected entities for custom entity type.

2019-11-07 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3504:


Commit ecd144d3703e127f48f1d5a1059a5643b6176d02 in atlas's branch 
refs/heads/branch-2.0 from nikhilbonte
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ecd144d ]

ATLAS-3504:- DSL query with like clause returns unexpected results #1.

Signed-off-by: nixonrodrigues 
(cherry picked from commit 24fb2b066bcff11a8b667b0f90d43cb482fb0e81)


> Regression: DSL query with "like" clause returns unexpected entities for 
> custom entity type.
> 
>
> Key: ATLAS-3504
> URL: https://issues.apache.org/jira/browse/ATLAS-3504
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Attachments: 
> ATLAS-3504-DSL-query-with-like-clause-returns-unexpected-results-p2.patch, 
> ATLAS-3504-DSL-query-with-like-clause-returns-unexpected-results-v1.patch, 
> entity1, entity2, type
>
>
> *Problem*
>  # Created a custom type type1 with string attributes name and type_str
>  # Created 2 entities of type1:
>  ## name : entity1 , type_str : rand_str
>  ## name : entity2 , type_str : str_rand
>  # Fired DSL query : type1 where type_str like "rand*"
> Expected that , entity1 only will be returned , but entity2 is also returned.
> For all the following queries , both entities are returned:
> 1.type1 where type_str like "rand*"
> 2.type1 where type_str like "*rand"
> 3.type1 where type_str like "rand"
>  
> Basic search filter "begins with" works correctly. Issue seems to be with 
> only DSL search. The issue is consistently reproducible.
>  
> *Root cause:*
> Creating typeDef having attribute with typeName as 'biginteger' or 
> 'bigdecimal', throws exception -
> {code:java}
> "java.lang.IllegalArgumentException: Unsupported data type [class 
> java.math.BigInteger] for field: ftol", {code}
> This affects text search.
>  
>  
> *Solution:*
> Added check to allow if data type of attribute is BigInteger or BigDecimal.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3504) Regression: DSL query with "like" clause returns unexpected entities for custom entity type.

2019-11-07 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3504:


Commit 24fb2b066bcff11a8b667b0f90d43cb482fb0e81 in atlas's branch 
refs/heads/master from nikhilbonte
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=24fb2b0 ]

ATLAS-3504:- DSL query with like clause returns unexpected results #1.

Signed-off-by: nixonrodrigues 


> Regression: DSL query with "like" clause returns unexpected entities for 
> custom entity type.
> 
>
> Key: ATLAS-3504
> URL: https://issues.apache.org/jira/browse/ATLAS-3504
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Attachments: 
> ATLAS-3504-DSL-query-with-like-clause-returns-unexpected-results-p2.patch, 
> ATLAS-3504-DSL-query-with-like-clause-returns-unexpected-results-v1.patch, 
> entity1, entity2, type
>
>
> *Problem*
>  # Created a custom type type1 with string attributes name and type_str
>  # Created 2 entities of type1:
>  ## name : entity1 , type_str : rand_str
>  ## name : entity2 , type_str : str_rand
>  # Fired DSL query : type1 where type_str like "rand*"
> Expected that , entity1 only will be returned , but entity2 is also returned.
> For all the following queries , both entities are returned:
> 1.type1 where type_str like "rand*"
> 2.type1 where type_str like "*rand"
> 3.type1 where type_str like "rand"
>  
> Basic search filter "begins with" works correctly. Issue seems to be with 
> only DSL search. The issue is consistently reproducible.
>  
> *Root cause:*
> Creating typeDef having attribute with typeName as 'biginteger' or 
> 'bigdecimal', throws exception -
> {code:java}
> "java.lang.IllegalArgumentException: Unsupported data type [class 
> java.math.BigInteger] for field: ftol", {code}
> This affects text search.
>  
>  
> *Solution:*
> Added check to allow if data type of attribute is BigInteger or BigDecimal.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3515) Migration: New Types Referenced within Existing Types

2019-11-07 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3515:


Commit 98163440590852fa9d142c23e596e8975a322349 in atlas's branch 
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9816344 ]

ATLAS-3515: Migration import now creates new types and then updates existing 
types.


> Migration: New Types Referenced within Existing Types
> -
>
> Key: ATLAS-3515
> URL: https://issues.apache.org/jira/browse/ATLAS-3515
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3515-Migration-import-type-definition.patch
>
>
> *Background*
> During migration import (and regular Import) types coming in are processed in 
> the following way:
>  * New types are determined.
>  * Modification to existing types are determined.
> *Steps to Duplicate*
> _Pre-requisites:_
>  * Create type definition with new _structDef_.
>  * Modify _hive_table_ (existing) such a new attribute references the 
> _structDef_.
> _Steps_
>  * Initiate migration import.
> _Expected outcome_
>  * New types should be part of the types definition (using REST APIs and 
> property pages).
>  * Data should get migrated.
> _Actual outcome_
>  * Type definition import fails.
> _Additional information_
> Stack trace:
> {code:java}
> org.apache.atlas.exception.AtlasBaseException: Given typename 
> hive_table_profile_data was invalid
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025)
> 
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285)
> 
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3517) Enhance suggestions REST API to have optional 'fieldName' parameter to get suggestions from

2019-11-07 Thread Sarath Subramanian (Jira) 


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

Sarath Subramanian updated ATLAS-3517:
--
Description: 
Suggestions REST API searches against all indexed fields (terms) to retrieve 
the top frequently used terms.

we don't have a way to retrieve suggestions only from a specific indexed field.

This enhancement introduces a new optional parameter in suggestions API - 
'fieldName', which when specified will provide suggestions against that indexed 
field name.

 

This will be useful to get suggestions on only a specific field - say labels 

  was:
Suggestions REST API searches against all indexed fields (terms) to retrieve 
the top frequently used terms.

we don't have a way to retrieve suggestions only from a specific indexed field.

This enhancement introduces a new optional parameter in suggestions API - 
'fieldName', which when specified will provide suggestions against that indexed 
field name.

 


> Enhance suggestions REST API to have optional 'fieldName' parameter to get 
> suggestions from
> ---
>
> Key: ATLAS-3517
> URL: https://issues.apache.org/jira/browse/ATLAS-3517
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
>
> Suggestions REST API searches against all indexed fields (terms) to retrieve 
> the top frequently used terms.
> we don't have a way to retrieve suggestions only from a specific indexed 
> field.
> This enhancement introduces a new optional parameter in suggestions API - 
> 'fieldName', which when specified will provide suggestions against that 
> indexed field name.
>  
> This will be useful to get suggestions on only a specific field - say labels 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3517) Enhance suggestions REST API to have optional 'fieldName' parameter to get suggestions from

2019-11-07 Thread Sarath Subramanian (Jira) 


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

Sarath Subramanian updated ATLAS-3517:
--
Description: 
Suggestions REST API searches against all indexed fields (terms) to retrieve 
the top frequently used terms.

we don't have a way to retrieve suggestions only from a specific indexed field.

This enhancement introduces a new optional parameter in suggestions API - 
'fieldName', which when specified will provide suggestions against that indexed 
field name.

 

  was:
Suggestions REST API searches against all indexed fields (terms) to retrieve 
the top frequently used terms.

we don't have a way to retrieve suggestions only from a specific indexed field.

This enhancement introduces a new optional parameter in suggestions API - 
'fieldName', which when specified which provide suggestions against that index 
field name.

 


> Enhance suggestions REST API to have optional 'fieldName' parameter to get 
> suggestions from
> ---
>
> Key: ATLAS-3517
> URL: https://issues.apache.org/jira/browse/ATLAS-3517
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
>
> Suggestions REST API searches against all indexed fields (terms) to retrieve 
> the top frequently used terms.
> we don't have a way to retrieve suggestions only from a specific indexed 
> field.
> This enhancement introduces a new optional parameter in suggestions API - 
> 'fieldName', which when specified will provide suggestions against that 
> indexed field name.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3518) Create Audit Framework for Atlas Purge Entity

2019-11-07 Thread Sidharth Kumar Mishra (Jira) 


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

Sidharth Kumar Mishra updated ATLAS-3518:
-
Issue Type: New Feature  (was: Bug)

> Create Audit Framework for Atlas Purge Entity
> -
>
> Key: ATLAS-3518
> URL: https://issues.apache.org/jira/browse/ATLAS-3518
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> Right now for purge, delete entity, etc. at Atlas we create audit entry at 
> HBase. User can go to entity and click on audit to see the audit information 
> for that particular entity. But if user purge one entity there will not be 
> any vertex at Janus graph and user will not able to get the purge audit which 
> is important for governance purpose.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-3518) Create Audit Framework for Atlas Purge Entity

2019-11-07 Thread Sidharth Kumar Mishra (Jira) 
Sidharth Kumar Mishra created ATLAS-3518:


 Summary: Create Audit Framework for Atlas Purge Entity
 Key: ATLAS-3518
 URL: https://issues.apache.org/jira/browse/ATLAS-3518
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra


Right now for purge, delete entity, etc. at Atlas we create audit entry at 
HBase. User can go to entity and click on audit to see the audit information 
for that particular entity. But if user purge one entity there will not be any 
vertex at Janus graph and user will not able to get the purge audit which is 
important for governance purpose.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-3517) Enhance suggestions REST API to have optional 'fieldName' parameter to get suggestions from

2019-11-07 Thread Sarath Subramanian (Jira) 
Sarath Subramanian created ATLAS-3517:
-

 Summary: Enhance suggestions REST API to have optional 'fieldName' 
parameter to get suggestions from
 Key: ATLAS-3517
 URL: https://issues.apache.org/jira/browse/ATLAS-3517
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 2.1.0


Suggestions REST API searches against all indexed fields (terms) to retrieve 
the top frequently used terms.

we don't have a way to retrieve suggestions only from a specific indexed field.

This enhancement introduces a new optional parameter in suggestions API - 
'fieldName', which when specified which provide suggestions against that index 
field name.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-11-07 Thread Sarath Subramanian (Jira) 


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

Sarath Subramanian updated ATLAS-3477:
--
Component/s:  atlas-core

> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3477.patch
>
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.
> As part of this issue solution we should be able to purge the entities which 
> are already soft deleted. This will be useful to users who is interested to 
> purge some list of soft deleted entities from Atlas. Due to governance 
> compliances, only admin can perform purge of entities.
> Purge should have separate Audit similar to delete entity.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-11-07 Thread Sidharth Kumar Mishra (Jira) 


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Attachment: (was: ATLAS-3477.patch)

> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3477.patch
>
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.
> As part of this issue solution we should be able to purge the entities which 
> are already soft deleted. This will be useful to users who is interested to 
> purge some list of soft deleted entities from Atlas. Due to governance 
> compliances, only admin can perform purge of entities.
> Purge should have separate Audit similar to delete entity.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-11-07 Thread Sidharth Kumar Mishra (Jira) 


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Attachment: ATLAS-3477.patch

> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-3477.patch
>
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.
> As part of this issue solution we should be able to purge the entities which 
> are already soft deleted. This will be useful to users who is interested to 
> purge some list of soft deleted entities from Atlas. Due to governance 
> compliances, only admin can perform purge of entities.
> Purge should have separate Audit similar to delete entity.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Review Request 71737: ATLAS-3477: Introduce purging of entity in Atlas

2019-11-07 Thread Sidharth Mishra 

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

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


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


Repository: atlas


Description
---

As part of this solution users can purge the entities which are already soft 
deleted. This will be useful as someone may be interested to purge some list of 
soft deleted entities from Atlas. Due to governance compliances, only admin can 
perform purge of entities.

Purge will also create separate Audit entry at HBase similar to delete entity 
operation.


Diffs
-

  authorization/src/main/java/org/apache/atlas/authorize/AtlasPrivilege.java 
59c596d66 
  client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 199d6bf58 
  intg/src/main/java/org/apache/atlas/listener/EntityChangeListenerV2.java 
444167eae 
  intg/src/main/java/org/apache/atlas/model/audit/EntityAuditEventV2.java 
e9cc7cd3d 
  
intg/src/main/java/org/apache/atlas/model/instance/EntityMutationResponse.java 
7ace00dff 
  intg/src/main/java/org/apache/atlas/model/instance/EntityMutations.java 
daf4ca88c 
  
repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
 43a9b842c 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
 01e339d23 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasEntityStore.java
 b94590bf1 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
 d2544df4f 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java
 3389d2465 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java
 17a96493f 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasGraphUtilsV2.java
 4d57d8bc8 
  server-api/src/main/java/org/apache/atlas/RequestContext.java 3d2a18f0c 
  
webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java
 48f0cd3c2 
  webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
464d46f1e 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityV2JerseyResourceIT.java
 5d506bbc2 


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


Testing
---

IT has been added. 
Validated manually by running below mentioned queries and REST:


a) create table thursday_07_11_1 (id int);
   create table thursday_07_11_1_ctas as select * from thursday_07_11_1;

   create table thursday_07_11_2 (id int);
   create table thursday_07_11_2_ctas as select * from thursday_07_11_2;
b) The above will create two lineages. Go to Atlas UI and get the vertices for 
atleast any two.


c) Using rest delete those two entities or use below query:
drop table thursday_07_11_1;
drop table thursday_07_11_1_ctas;

drop table thursday_07_11_2;
drop table thursday_07_11_2_ctas;

REST delete example:
DELETE 
http://localhopst:31000/api/atlas/v2/entity/guid/7dd7fd9c-0185-41a5-aff0-4212fa7eb87c

d) Now use the same guids and call purge REST:
DELETE 
http://localhost:31000/api/atlas/admin/purge/?guid=75983487-9e29-41ee-9bae-53f0a0b54c05=98bee463-8810-402a-bcdc-3eb00bf50365

Check the response which will return all the successfully purged entities

e) For each guid check if the audit has separate new entry for purge. REST used:
GET 
http://localhost:31000/api/atlas/v2/entity/7b6806c1-8daf-4e0f-8d10-672a192968f1/audit

Example Response:

[
{
"entityId": "7b6806c1-8daf-4e0f-8d10-672a192968f1",
"timestamp": 1573161789065,
"user": "admin",
"action": "ENTITY_PURGE",
"details": "Purged entity",
"eventKey": "7b6806c1-8daf-4e0f-8d10-672a192968f1:1573161789065:1",
"entity": null,
"type": null
},
{
"entityId": "7b6806c1-8daf-4e0f-8d10-672a192968f1",
"timestamp": 1573161729972,
"user": "impala",
"action": "ENTITY_DELETE",
"details": "Deleted entity",
"eventKey": "7b6806c1-8daf-4e0f-8d10-672a192968f1:1573161729972:1",
"entity": null,
"type": null
},
{
"entityId": "7b6806c1-8daf-4e0f-8d10-672a192968f1",
"timestamp": 1573161727305,
"user": "admin",
"action": "ENTITY_UPDATE",
"details": "Updated: 
{\"typeName\":\"hive_column\",\"attributes\":{\"owner\":\"admin\",\"replicatedTo\":null,\"replicatedFrom\":null,\"qualifiedName\":\"default.thursday_07_11_5.id@cm\",\"name\":\"id\",\"description\":null,\"comment\":null,\"position\":0,\"type\":\"int\"},\"guid\":\"7b6806c1-8daf-4e0f-8d10-672a192968f1\",\"isIncomplete\":false,\"status\":\"ACTIVE\",\"createdBy\":\"impala\",\"updatedBy\":\"admin\",\"createTime\":1573161723180,\"updateTime\":1573161727305,\"version\":0,\"labels\":[]}",

[jira] [Updated] (ATLAS-3477) Introduce purging of entity in Atlas

2019-11-07 Thread Sidharth Kumar Mishra (Jira) 


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

Sidharth Kumar Mishra updated ATLAS-3477:
-
Description: 
In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there is 
no way to do cleanup if user wants to delete those permanently. Right now we 
can change the configuration 

atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.

HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
desired. But what happens to existing soft deleted Entities. There is no way in 
that case.

As part of this issue solution we should be able to purge the entities which 
are already soft deleted. This will be useful to users who is interested to 
purge some list of soft deleted entities from Atlas. Due to governance 
compliances, only admin can perform purge of entities.

Purge should have separate Audit similar to delete entity.

  was:
In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there is 
no way to do cleanup if user wants to delete those permanently. Right now we 
can change the configuration 

atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.

HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
desired. But what happens to existing soft deleted Entities. There is no way in 
that case.

There are two cases which needs to be addressed as part of this problem.
 # There is an active entity which has to be purged in case the entity is 
dropped.
 # There might be existing soft deleted entities and which has to be purge 
deleted if user desires

In both the above cases we also need to think about the auditing and its impact.


> Introduce purging of entity in Atlas
> 
>
> Key: ATLAS-3477
> URL: https://issues.apache.org/jira/browse/ATLAS-3477
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> In case of soft delete at Atlas i.e. the entities marked as 'DELETED' there 
> is no way to do cleanup if user wants to delete those permanently. Right now 
> we can change the configuration 
> atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.
> HardDeleteHandlerV1 and make the new delete of entity to be cleaned up as 
> desired. But what happens to existing soft deleted Entities. There is no way 
> in that case.
> As part of this issue solution we should be able to purge the entities which 
> are already soft deleted. This will be useful to users who is interested to 
> purge some list of soft deleted entities from Atlas. Due to governance 
> compliances, only admin can perform purge of entities.
> Purge should have separate Audit similar to delete entity.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3515) Migration: New Types Referenced within Existing Types

2019-11-07 Thread Sarath Subramanian (Jira) 


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

Sarath Subramanian commented on ATLAS-3515:
---

+1 for the patch. Thanks [~amestry]

> Migration: New Types Referenced within Existing Types
> -
>
> Key: ATLAS-3515
> URL: https://issues.apache.org/jira/browse/ATLAS-3515
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3515-Migration-import-type-definition.patch
>
>
> *Background*
> During migration import (and regular Import) types coming in are processed in 
> the following way:
>  * New types are determined.
>  * Modification to existing types are determined.
> *Steps to Duplicate*
> _Pre-requisites:_
>  * Create type definition with new _structDef_.
>  * Modify _hive_table_ (existing) such a new attribute references the 
> _structDef_.
> _Steps_
>  * Initiate migration import.
> _Expected outcome_
>  * New types should be part of the types definition (using REST APIs and 
> property pages).
>  * Data should get migrated.
> _Actual outcome_
>  * Type definition import fails.
> _Additional information_
> Stack trace:
> {code:java}
> org.apache.atlas.exception.AtlasBaseException: Given typename 
> hive_table_profile_data was invalid
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025)
> 
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285)
> 
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3515) Migration: New Types Referenced within Existing Types

2019-11-07 Thread Ashutosh Mestry (Jira) 


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

Ashutosh Mestry commented on ATLAS-3515:


PC build: 
[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1533/]

> Migration: New Types Referenced within Existing Types
> -
>
> Key: ATLAS-3515
> URL: https://issues.apache.org/jira/browse/ATLAS-3515
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3515-Migration-import-type-definition.patch
>
>
> *Background*
> During migration import (and regular Import) types coming in are processed in 
> the following way:
>  * New types are determined.
>  * Modification to existing types are determined.
> *Steps to Duplicate*
> _Pre-requisites:_
>  * Create type definition with new _structDef_.
>  * Modify _hive_table_ (existing) such a new attribute references the 
> _structDef_.
> _Steps_
>  * Initiate migration import.
> _Expected outcome_
>  * New types should be part of the types definition (using REST APIs and 
> property pages).
>  * Data should get migrated.
> _Actual outcome_
>  * Type definition import fails.
> _Additional information_
> Stack trace:
> {code:java}
> org.apache.atlas.exception.AtlasBaseException: Given typename 
> hive_table_profile_data was invalid
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025)
> 
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285)
> 
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-3516) Provide a command line script for S3 Bulk extraction and define assemblies for commandline..

2019-11-07 Thread Sridhar (Jira) 
Sridhar created ATLAS-3516:
--

 Summary: Provide a command line script for S3 Bulk extraction and 
define assemblies for commandline..
 Key: ATLAS-3516
 URL: https://issues.apache.org/jira/browse/ATLAS-3516
 Project: Atlas
  Issue Type: Improvement
Reporter: Sridhar
Assignee: Sridhar






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-3515) Migration: New Types Referenced within Existing Types

2019-11-07 Thread Ashutosh Mestry (Jira) 
Ashutosh Mestry created ATLAS-3515:
--

 Summary: Migration: New Types Referenced within Existing Types
 Key: ATLAS-3515
 URL: https://issues.apache.org/jira/browse/ATLAS-3515
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.0.0, trunk
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
 Fix For: trunk, 2.1.0


*Background*

During migration import (and regular Import) types coming in are processed in 
the following way:
 * New types are determined.
 * Modification to existing types are determined.

*Steps to Duplicate*

_Pre-requisites:_
 * Create type definition with new _structDef_.
 * Modify _hive_table_ (existing) such a new attribute references the 
_structDef_.

_Steps_
 * Initiate migration import.

_Expected outcome_
 * New types should be part of the types definition (using REST APIs and 
property pages).
 * Data should get migrated.

_Actual outcome_
 * Type definition import fails.

_Additional information_

Stack trace:
{code:java}
org.apache.atlas.exception.AtlasBaseException: Given typename 
hive_table_profile_data was invalid
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025)

at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285)

at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3515) Migration: New Types Referenced within Existing Types

2019-11-07 Thread Ashutosh Mestry (Jira) 


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

Ashutosh Mestry updated ATLAS-3515:
---
Attachment: ATLAS-3515-Migration-import-type-definition.patch

> Migration: New Types Referenced within Existing Types
> -
>
> Key: ATLAS-3515
> URL: https://issues.apache.org/jira/browse/ATLAS-3515
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3515-Migration-import-type-definition.patch
>
>
> *Background*
> During migration import (and regular Import) types coming in are processed in 
> the following way:
>  * New types are determined.
>  * Modification to existing types are determined.
> *Steps to Duplicate*
> _Pre-requisites:_
>  * Create type definition with new _structDef_.
>  * Modify _hive_table_ (existing) such a new attribute references the 
> _structDef_.
> _Steps_
>  * Initiate migration import.
> _Expected outcome_
>  * New types should be part of the types definition (using REST APIs and 
> property pages).
>  * Data should get migrated.
> _Actual outcome_
>  * Type definition import fails.
> _Additional information_
> Stack trace:
> {code:java}
> org.apache.atlas.exception.AtlasBaseException: Given typename 
> hive_table_profile_data was invalid
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.tryUpdateByName(AtlasTypeDefGraphStore.java:1025)
> 
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateEntityDefByName(AtlasTypeDefGraphStore.java:285)
> 
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySprin
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Review Request 71736: ATLAS-3482 Enhance basic search to enable search on entity system attributes

2019-11-07 Thread Le Ma 

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

Review request for atlas, Ashutosh Mestry, Aadarsh Jajodia, Sridhar K, Madhan 
Neethiraj, and Sarath Subramanian.


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


Repository: atlas


Description
---

Introduce ALL_ENTITY_TYPE to support search on system attributes across all 
entity types. System attributes will be passed in as normal entity attributes.


Diffs
-

  intg/src/main/java/org/apache/atlas/model/discovery/SearchParameters.java 
8f0e5912d 
  intg/src/main/java/org/apache/atlas/type/AtlasBuiltInTypes.java ed1e5ded2 
  intg/src/main/java/org/apache/atlas/type/AtlasClassificationType.java 
417194202 
  intg/src/main/java/org/apache/atlas/type/AtlasEntityType.java 884447f81 
  intg/src/main/java/org/apache/atlas/type/AtlasStructType.java e8bf7f9eb 
  
repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
 672f38132 
  
repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java 
03eb92bcc 
  
repository/src/main/java/org/apache/atlas/discovery/FullTextSearchProcessor.java
 152ade8d4 
  repository/src/main/java/org/apache/atlas/discovery/SearchContext.java 
7ad32bdb9 
  repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
b56d8e83a 
  webapp/src/test/java/org/apache/atlas/web/adapters/TestEntitiesREST.java 
cd8f8981c 


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


Testing
---

- Added new unit tests, passed.
- will run pre-commit job.


Thanks,

Le Ma

Re: Would you please give me the permission as a contributor

2019-11-07 Thread Madhan Neethiraj 
Hello,

Thanks for your interest in contributing to Apache Atlas. You have been added 
as a contributor. Welcome to Apache Atlas community!

Regards,
Madhan

On 11/7/19, 4:08 AM, "leslizhang(张雄)"  wrote:

HiGuys,

I want to contribute to ApacheAtlas.Would you please give me the permission 
as a contributor?
 My JIRA ID is leslizhang.

best regards!

Would you please give me the permission as a contributor

2019-11-07 Thread 张雄 
HiGuys,

I want to contribute to ApacheAtlas.Would you please give me the permission as 
a contributor?
 My JIRA ID is leslizhang.

best regards!

[jira] [Commented] (ATLAS-3509) UI: Add basic search hyperlink in metric popup

2019-11-07 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3509:


Commit 213e86bca0bf42f7ac0df98f5fda5f5e85f70341 in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=213e86b ]

ATLAS-3509 : UI: Add basic search hyperlink in metric popup

(cherry picked from commit d5c8bf40dc92ff538daf7da1ad9bac0dbb7a26fd)


> UI: Add basic search hyperlink in metric popup
> --
>
> Key: ATLAS-3509
> URL: https://issues.apache.org/jira/browse/ATLAS-3509
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3509-1.patch, ATLAS-3509-2.patch, 
> ATLAS-3509.patch, Screen Shot 2019-11-05 at 5.23.33 PM.png, Screen Shot 
> 2019-11-05 at 5.23.39 PM.png, Screen Shot 2019-11-05 at 5.23.46 PM.png
>
>
> !Screen Shot 2019-11-05 at 5.23.33 PM.png|width=612,height=317!
>  
> !Screen Shot 2019-11-05 at 5.23.39 PM.png|width=622,height=298!
>  
> !Screen Shot 2019-11-05 at 5.23.46 PM.png|width=632,height=309!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3509) UI: Add basic search hyperlink in metric popup

2019-11-07 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-3509:


Commit d5c8bf40dc92ff538daf7da1ad9bac0dbb7a26fd in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d5c8bf4 ]

ATLAS-3509 : UI: Add basic search hyperlink in metric popup


> UI: Add basic search hyperlink in metric popup
> --
>
> Key: ATLAS-3509
> URL: https://issues.apache.org/jira/browse/ATLAS-3509
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3509-1.patch, ATLAS-3509-2.patch, 
> ATLAS-3509.patch, Screen Shot 2019-11-05 at 5.23.33 PM.png, Screen Shot 
> 2019-11-05 at 5.23.39 PM.png, Screen Shot 2019-11-05 at 5.23.46 PM.png
>
>
> !Screen Shot 2019-11-05 at 5.23.33 PM.png|width=612,height=317!
>  
> !Screen Shot 2019-11-05 at 5.23.39 PM.png|width=622,height=298!
>  
> !Screen Shot 2019-11-05 at 5.23.46 PM.png|width=632,height=309!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3509) UI: Add basic search hyperlink in metric popup

2019-11-07 Thread Keval Bhatt (Jira) 


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

Keval Bhatt updated ATLAS-3509:
---
Attachment: ATLAS-3509-2.patch

> UI: Add basic search hyperlink in metric popup
> --
>
> Key: ATLAS-3509
> URL: https://issues.apache.org/jira/browse/ATLAS-3509
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3509-1.patch, ATLAS-3509-2.patch, 
> ATLAS-3509.patch, Screen Shot 2019-11-05 at 5.23.33 PM.png, Screen Shot 
> 2019-11-05 at 5.23.39 PM.png, Screen Shot 2019-11-05 at 5.23.46 PM.png
>
>
> !Screen Shot 2019-11-05 at 5.23.33 PM.png|width=612,height=317!
>  
> !Screen Shot 2019-11-05 at 5.23.39 PM.png|width=622,height=298!
>  
> !Screen Shot 2019-11-05 at 5.23.46 PM.png|width=632,height=309!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3509) UI: Add basic search hyperlink in metric popup

2019-11-07 Thread Nixon Rodrigues (Jira) 


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

Nixon Rodrigues commented on ATLAS-3509:


[~kevalbhatt] thanks for the patch.

 

The changes looks good +1.

> UI: Add basic search hyperlink in metric popup
> --
>
> Key: ATLAS-3509
> URL: https://issues.apache.org/jira/browse/ATLAS-3509
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3509-1.patch, ATLAS-3509.patch, Screen Shot 
> 2019-11-05 at 5.23.33 PM.png, Screen Shot 2019-11-05 at 5.23.39 PM.png, 
> Screen Shot 2019-11-05 at 5.23.46 PM.png
>
>
> !Screen Shot 2019-11-05 at 5.23.33 PM.png|width=612,height=317!
>  
> !Screen Shot 2019-11-05 at 5.23.39 PM.png|width=622,height=298!
>  
> !Screen Shot 2019-11-05 at 5.23.46 PM.png|width=632,height=309!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (ATLAS-3514) UI : Allows user to search using multiple classification

2019-11-07 Thread Sameer Shaikh (Jira) 


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

Sameer Shaikh reassigned ATLAS-3514:


Assignee: Sameer Shaikh  (was: Keval Bhatt)

> UI : Allows user to search using multiple classification
> 
>
> Key: ATLAS-3514
> URL: https://issues.apache.org/jira/browse/ATLAS-3514
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Sameer Shaikh
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3514) UI : Allows user to search using multiple classification

2019-11-07 Thread Keval Bhatt (Jira) 


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

Keval Bhatt updated ATLAS-3514:
---
Issue Type: Improvement  (was: Bug)

> UI : Allows user to search using multiple classification
> 
>
> Key: ATLAS-3514
> URL: https://issues.apache.org/jira/browse/ATLAS-3514
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-3514) UI : Allows user to search using multiple classification

2019-11-07 Thread Keval Bhatt (Jira) 
Keval Bhatt created ATLAS-3514:
--

 Summary: UI : Allows user to search using multiple classification
 Key: ATLAS-3514
 URL: https://issues.apache.org/jira/browse/ATLAS-3514
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3513) Classic UI: Sidebar not rendered on refresh if url has 'from=classification' queryParam

2019-11-07 Thread Keval Bhatt (Jira) 


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

Keval Bhatt updated ATLAS-3513:
---
Summary: Classic UI: Sidebar not rendered on refresh if url has 
'from=classification' queryParam   (was: UI: Classic UI: Sidebar not rendered 
on refresh if url has 'from=classification' queryParam )

> Classic UI: Sidebar not rendered on refresh if url has 'from=classification' 
> queryParam 
> 
>
> Key: ATLAS-3513
> URL: https://issues.apache.org/jira/browse/ATLAS-3513
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: Screen Shot 2019-11-07 at 2.54.59 PM.png
>
>
> !Screen Shot 2019-11-07 at 2.54.59 PM.png|width=686,height=357!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3513) UI: Classic UI: Sidebar not rendered on refresh if url has 'from=classification' queryParam

2019-11-07 Thread Keval Bhatt (Jira) 


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

Keval Bhatt updated ATLAS-3513:
---
Fix Version/s: 3.0.0
   2.1.0

> UI: Classic UI: Sidebar not rendered on refresh if url has 
> 'from=classification' queryParam 
> 
>
> Key: ATLAS-3513
> URL: https://issues.apache.org/jira/browse/ATLAS-3513
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: Screen Shot 2019-11-07 at 2.54.59 PM.png
>
>
> !Screen Shot 2019-11-07 at 2.54.59 PM.png|width=686,height=357!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3513) UI: Classic UI: Sidebar not rendered on refresh if url has 'from=classification' queryParam

2019-11-07 Thread Keval Bhatt (Jira) 


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

Keval Bhatt updated ATLAS-3513:
---
Description: !Screen Shot 2019-11-07 at 2.54.59 PM.png|width=686,height=357!

> UI: Classic UI: Sidebar not rendered on refresh if url has 
> 'from=classification' queryParam 
> 
>
> Key: ATLAS-3513
> URL: https://issues.apache.org/jira/browse/ATLAS-3513
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: Screen Shot 2019-11-07 at 2.54.59 PM.png
>
>
> !Screen Shot 2019-11-07 at 2.54.59 PM.png|width=686,height=357!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3513) UI: Classic UI: Sidebar not rendered on refresh if url has 'from=classification' queryParam

2019-11-07 Thread Keval Bhatt (Jira) 


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

Keval Bhatt updated ATLAS-3513:
---
Attachment: Screen Shot 2019-11-07 at 2.54.59 PM.png

> UI: Classic UI: Sidebar not rendered on refresh if url has 
> 'from=classification' queryParam 
> 
>
> Key: ATLAS-3513
> URL: https://issues.apache.org/jira/browse/ATLAS-3513
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: Screen Shot 2019-11-07 at 2.54.59 PM.png
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-3513) UI: Classic UI: Sidebar not rendered on refresh if url has 'from=classification' queryParam

2019-11-07 Thread Keval Bhatt (Jira) 
Keval Bhatt created ATLAS-3513:
--

 Summary: UI: Classic UI: Sidebar not rendered on refresh if url 
has 'from=classification' queryParam 
 Key: ATLAS-3513
 URL: https://issues.apache.org/jira/browse/ATLAS-3513
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt






--
This message was sent by Atlassian Jira
(v8.3.4#803005)