[jira] [Assigned] (ATLAS-3696) [Business Metadata] No option to check/uncheck Business Metadata field in search results

[Pinal (Jira)]

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

Pinal reassigned ATLAS-3696:


Assignee: Keval Bhatt  (was: Pinal)

> [Business Metadata] No option to check/uncheck Business Metadata field in 
> search results
> 
>
> Key: ATLAS-3696
> URL: https://issues.apache.org/jira/browse/ATLAS-3696
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 9.00.55 PM.png, Screenshot 
> 2020-03-26 at 9.04.22 PM.png
>
>
> For instance, there is no way to show "Business Metadata" column if Business 
> Metadata attribute filter is not applied while searching. Attached screenshots



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

Re: Review Request 72270: ATLAS-3689 Add audits entries when Business Metadata Attributes are added/updated/deleted to an entity

[Nikhil Bonte]

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




intg/src/main/java/org/apache/atlas/listener/EntityChangeListenerV2.java
Lines 185 (patched)


I suggest to have input as list of businessMetadataAttributes.
That way events can be put for all businessMetadataAttributes at one go 
instead putting for 1 attribute at a time.

Same may be done for case update, delete.


- Nikhil Bonte


On April 8, 2020, 2:30 p.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72270/
> ---
> 
> (Updated April 8, 2020, 2:30 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
> Nixon Rodrigues, Sarath Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-3689
> https://issues.apache.org/jira/browse/ATLAS-3689
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add audits entries when Namespace Attributes are added/updated/deleted to an 
> entity
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/listener/EntityChangeListenerV2.java 
> 2394a12 
>   intg/src/main/java/org/apache/atlas/model/audit/EntityAuditEventV2.java 
> 9301e21 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/AtlasAuditService.java
>  590f7a0 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
>  cab4e1e 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java
>  00c0114 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
>  0d5b631 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/IAtlasEntityChangeNotifier.java
>  c4dc5a1 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/bulkimport/EntityChangeNotifierNop.java
>  2943ea9 
>   
> webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java
>  6d64fec 
> 
> 
> Diff: https://reviews.apache.org/r/72270/diff/3/
> 
> 
> Testing
> ---
> 
> Pre-commit: 
> https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1759/console
> 
> Basic testing is done.
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>

Re: Review Request 72338: ATLAS-3726: Add result count to Atlas Admin Audit and enable filters on count for get audit

[Sarath Subramanian]

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




addons/models/-Area0/0010-base_model.json
Lines 487 (patched)


change 'isIndexable' to true to enable search on result count


- Sarath Subramanian


On April 8, 2020, 11:19 a.m., Sidharth Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72338/
> ---
> 
> (Updated April 8, 2020, 11:19 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-3726
> https://issues.apache.org/jira/browse/ATLAS-3726
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Added a new field for result count at model, Changed the DTO and service 
> accordingly. UT has been modified too. Now sort and filter will also work on 
> top of result count in admin audit
> 
> 
> Diffs
> -
> 
>   addons/models/-Area0/0010-base_model.json 351e07bd3 
>   intg/src/main/java/org/apache/atlas/model/audit/AtlasAuditEntry.java 
> f2a8b3e4d 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/AtlasAuditService.java
>  590f7a034 
>   
> repository/src/main/java/org/apache/atlas/repository/ogm/AtlasAuditEntryDTO.java
>  8e4bdb523 
>   
> repository/src/test/java/org/apache/atlas/repository/audit/AdminPurgeTest.java
>  0a2fc39a3 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> 9bc70400e 
> 
> 
> Diff: https://reviews.apache.org/r/72338/diff/1/
> 
> 
> Testing
> ---
> 
> Manual Testing:
> 
> curl --location --request POST 
> 'http://sid-ycloud-atlas1-1.sid-ycloud-atlas1.root.hwx.site:31000/api/atlas/admin/audits/'
>  \
> --header 'Content-Type: application/json' \
> --header 'Authorization: Basic YWRtaW46YWRtaW4xMjM=' \
> --data-raw '{
> "auditFilters": {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "userName",
> "operator": "like",
> "attributeValue": "admin"
> },
> {
> "attributeName": "operation",
> "operator": "like",
> "attributeValue": "PURGE"
> },
> {
> "attributeName": "clientId",
> "operator": "eq",
> "attributeValue": "10.96.94.236"
> },
> {
> "attributeName": "startTime",
> "operator": "gte",
> "attributeValue": "1575958152162"
> },
> {
> "attributeName": "endTime",
> "operator": "gte",
> "attributeValue": "1575958152184"
> },
> {
> "attributeName": "resultCount",
> "operator": "eq",
> "attributeValue": "4"
> }
> ]
> },
> "limit": 15,
> "offset": 0,
> "sortBy": "resultCount",
> "sortOrder": "DESCENDING"
> }'
> 
> 
> Thanks,
> 
> Sidharth Mishra
> 
>

[jira] [Created] (ATLAS-3727) Add get purge result summary REST for admin audit record

[Sidharth Kumar Mishra (Jira)]

Sidharth Kumar Mishra created ATLAS-3727:


 Summary: Add get purge result summary REST for admin audit record
 Key: ATLAS-3727
 URL: https://issues.apache.org/jira/browse/ATLAS-3727
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sidharth Kumar Mishra


Right now purge admin audit result stores purged entities guids. We need a 
separate REST call to get more details summary of the entities purged.



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

Review Request 72338: ATLAS-3726: Add result count to Atlas Admin Audit and enable filters on count for get audit

[Sidharth Mishra]

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

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


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


Repository: atlas


Description
---

Added a new field for result count at model, Changed the DTO and service 
accordingly. UT has been modified too. Now sort and filter will also work on 
top of result count in admin audit


Diffs
-

  addons/models/-Area0/0010-base_model.json 351e07bd3 
  intg/src/main/java/org/apache/atlas/model/audit/AtlasAuditEntry.java 
f2a8b3e4d 
  
repository/src/main/java/org/apache/atlas/repository/audit/AtlasAuditService.java
 590f7a034 
  
repository/src/main/java/org/apache/atlas/repository/ogm/AtlasAuditEntryDTO.java
 8e4bdb523 
  
repository/src/test/java/org/apache/atlas/repository/audit/AdminPurgeTest.java 
0a2fc39a3 
  webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
9bc70400e 


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


Testing
---

Manual Testing:

curl --location --request POST 
'http://sid-ycloud-atlas1-1.sid-ycloud-atlas1.root.hwx.site:31000/api/atlas/admin/audits/'
 \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic YWRtaW46YWRtaW4xMjM=' \
--data-raw '{
"auditFilters": {
"condition": "AND",
"criterion": [
{
"attributeName": "userName",
"operator": "like",
"attributeValue": "admin"
},
{
"attributeName": "operation",
"operator": "like",
"attributeValue": "PURGE"
},
{
"attributeName": "clientId",
"operator": "eq",
"attributeValue": "10.96.94.236"
},
{
"attributeName": "startTime",
"operator": "gte",
"attributeValue": "1575958152162"
},
{
"attributeName": "endTime",
"operator": "gte",
"attributeValue": "1575958152184"
},
{
"attributeName": "resultCount",
"operator": "eq",
"attributeValue": "4"
}
]
},
"limit": 15,
"offset": 0,
"sortBy": "resultCount",
"sortOrder": "DESCENDING"
}'


Thanks,

Sidharth Mishra

[jira] [Created] (ATLAS-3726) Add result count to Atlas Admin Audit and enable filters on count for get audit

[Sidharth Kumar Mishra (Jira)]

Sidharth Kumar Mishra created ATLAS-3726:


 Summary: Add result count to Atlas Admin Audit and enable filters 
on count for get audit
 Key: ATLAS-3726
 URL: https://issues.apache.org/jira/browse/ATLAS-3726
 Project: Atlas
  Issue Type: Bug
Reporter: Sidharth Kumar Mishra
Assignee: Sidharth Kumar Mishra






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

Re: Review Request 72270: ATLAS-3689 Add audits entries when Business Metadata Attributes are added/updated/deleted to an entity

[Mandar Ambawane]

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

(Updated April 8, 2020, 2:30 p.m.)


Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
Nixon Rodrigues, Sarath Subramanian, and Sidharth Mishra.


Changes
---

Addressed review comments


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


Repository: atlas


Description
---

Add audits entries when Namespace Attributes are added/updated/deleted to an 
entity


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/listener/EntityChangeListenerV2.java 
2394a12 
  intg/src/main/java/org/apache/atlas/model/audit/EntityAuditEventV2.java 
9301e21 
  
repository/src/main/java/org/apache/atlas/repository/audit/AtlasAuditService.java
 590f7a0 
  
repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
 cab4e1e 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java
 00c0114 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
 0d5b631 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/IAtlasEntityChangeNotifier.java
 c4dc5a1 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/bulkimport/EntityChangeNotifierNop.java
 2943ea9 
  
webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java
 6d64fec 


Diff: https://reviews.apache.org/r/72270/diff/3/

Changes: https://reviews.apache.org/r/72270/diff/2-3/


Testing
---

Pre-commit: 
https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1759/console

Basic testing is done.


Thanks,

Mandar Ambawane

Re: Review Request 72317: ATLAS-3709 Issues with quick search/suggestions in conjunction with Business Metadata attributes

[Mandar Ambawane]

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

(Updated April 8, 2020, 2:15 p.m.)


Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
Nixon Rodrigues, Sarath Subramanian, and Sidharth Mishra.


Changes
---

Addressed review comments


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


Repository: atlas


Description
---

Resolved issues in conjunction with Business Metadata attributes.
Also handled index populate for Business Metadata attributes at the time of 
start up.


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/listener/ChangedTypeDefs.java 58e889a 
  intg/src/main/java/org/apache/atlas/type/AtlasTypeRegistry.java 9df89a2 
  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
 647e304 


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

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


Testing
---

Pre-commit https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1784/console

Manual testing done.

CASE:1
1. create Busines meatadata "BM1" 
2. add one attribute "attr1" in "BM1" (search weight 9)
3. create one entity "hdfsentity1"
4. associate "attr1" to "hdfsentity1"
5. check in quick search and suggestions for "attr1" value

6. add another attribute "attr2" in "BM1" (search weight 9)
7. associate "attr2" to "hdfsentity1"
8. check in quick search and suggestions


CASE:2
1. create Busines meatadata "BM1" 
2. add one attribute "attr1" in "BM1" (search weight 9)
3. create one entity "hdfsentity1"
4. associate "attr1" to "hdfsentity1"
5. check in quick search and suggestions for "attr1" value

6. add another attribute "attr2" in "BM1" (search weight 10)
7. associate "attr2" to "hdfsentity1"
8. check in quick search and suggestions for "attr1" and "attr2" values


CASE:3
1. create Busines meatadata "BM1" 
2. add one attribute "attr1" in "BM1" (search weight 9)
3. create one entity "hdfsentity1"
4. associate "attr1" to "hdfsentity1"
5. check in quick search and suggestions for "attr1" value

6. create another Busines meatadata "BM2" 
7. add attribute "attr2" in "BM2" (search weight 9)
8. associate "attr2" to "hdfsentity1"
9. check in quick search and suggestions for "attr1" and "attr2" values


Thanks,

Mandar Ambawane

[jira] [Created] (ATLAS-3725) Are UI pages considering i18n internationalization support?

[kangjunxiang (Jira)]

kangjunxiang created ATLAS-3725:
---

 Summary: Are UI pages considering i18n internationalization 
support?
 Key: ATLAS-3725
 URL: https://issues.apache.org/jira/browse/ATLAS-3725
 Project: Atlas
  Issue Type: Improvement
  Components: atlas-webui
Affects Versions: 2.0.0
Reporter: kangjunxiang


Are UI pages considering i18n internationalization support?



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

Re: Review Request 72270: ATLAS-3689 Add audits entries when Business Metadata Attributes are added/updated/deleted to an entity

[Sarath Subramanian]

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




intg/src/main/java/org/apache/atlas/listener/EntityChangeListenerV2.java
Lines 178 (patched)


consider adding comments to be in alignment with other methods in this 
interface.



intg/src/main/java/org/apache/atlas/model/audit/EntityAuditEventV2.java
Lines 54 (patched)


BUSINESS_ATTRIBUTE_ADD=> BUSINESS_METADATA_ATTRIBUTE_ADD
BUSINESS_ATTRIBUTE_UPDATE => BUSINESS_METADATA_ATTRIBUTE_UPDATE
BUSINESS_ATTRIBUTE_DELETE => BUSINESS_METADATA_ATTRIBUTE_DELETE

consider updating in line 95, 97 and 99 as well



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java
Lines 411 (patched)


why this check is added? we are not creating any audit vertex for business 
metadata add/update/delete. Please review and remove.



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
Lines 452 (patched)


instead of creating audit entries for every iteration of for loop. Consider 
sending audits at the end to avoid multiple calls to write to audit repository.

maintain a list of business metadata attributes - added/updated/deleted for 
entity and send audit notification outside for loop.



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
Lines 520 (patched)


same comment. consider sending audit entries at the end - outside for loop.



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
Lines 567 (patched)


consider adding the audit entry after you exit out of for loop, so 
notification is sent at the end. A recent change was added to add bulk audit 
notification for add classifications. Please review.



webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java
Lines 323 (patched)


nit: add comments inside these methods - "// do nothing -> notification not 
sent out for business metadata attribute addition/updation/removal from 
entities"


- Sarath Subramanian


On April 6, 2020, 11:21 p.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72270/
> ---
> 
> (Updated April 6, 2020, 11:21 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
> Nixon Rodrigues, Sarath Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-3689
> https://issues.apache.org/jira/browse/ATLAS-3689
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add audits entries when Namespace Attributes are added/updated/deleted to an 
> entity
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/listener/EntityChangeListenerV2.java 
> 2394a12 
>   intg/src/main/java/org/apache/atlas/model/audit/EntityAuditEventV2.java 
> 9301e21 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/AtlasAuditService.java
>  590f7a0 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
>  cab4e1e 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java
>  00c0114 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
>  75b016c 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/IAtlasEntityChangeNotifier.java
>  c4dc5a1 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/bulkimport/EntityChangeNotifierNop.java
>  2943ea9 
>   
> webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java
>  6d64fec 
> 
> 
> Diff: https://reviews.apache.org/r/72270/diff/2/
> 
> 
> Testing
> ---
> 
> Pre-commit: 
> https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1759/console
> 
> Basic testing is done.
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>

[jira] [Created] (ATLAS-3724) Qualified name pattern for Column cause ambiguity in Quickstart data.

[chaitali borole (Jira)]

chaitali borole created ATLAS-3724:
--

 Summary: Qualified name pattern for Column cause ambiguity in 
Quickstart data.
 Key: ATLAS-3724
 URL: https://issues.apache.org/jira/browse/ATLAS-3724
 Project: Atlas
  Issue Type: Bug
Affects Versions: 2.0.0, 3.0.0
Reporter: chaitali borole


1) Create Entity of type Column name = app_id, qualified name = app_id@cl1
assign Table - logging_fact_monthly_mv
2) Again Create same entity with same qualified name
assign different Table - log_fact_daily_mv
3) Check Column Relationship, Only one Table relationship is seen
4) Check Table (logging_fact_monthly_mv,log_fact_daily_mv) In Both 
Relationship, Column app_id is seen



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

[jira] [Assigned] (ATLAS-3724) Qualified name pattern for Column cause ambiguity in Quickstart data.

[chaitali borole (Jira)]

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

chaitali borole reassigned ATLAS-3724:
--

Assignee: chaitali borole

> Qualified name pattern for Column cause ambiguity in Quickstart data.
> -
>
> Key: ATLAS-3724
> URL: https://issues.apache.org/jira/browse/ATLAS-3724
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0, 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> 1) Create Entity of type Column name = app_id, qualified name = app_id@cl1
> assign Table - logging_fact_monthly_mv
> 2) Again Create same entity with same qualified name
> assign different Table - log_fact_daily_mv
> 3) Check Column Relationship, Only one Table relationship is seen
> 4) Check Table (logging_fact_monthly_mv,log_fact_daily_mv) In Both 
> Relationship, Column app_id is seen



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

Re: Review Request 72317: ATLAS-3709 Issues with quick search/suggestions in conjunction with Business Metadata attributes

[Sarath Subramanian]

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




intg/src/main/java/org/apache/atlas/type/AtlasTypeRegistry.java
Lines 1000 (patched)


code duplicated. Try to combine with for loop above for 
'ttr.getAllEntityTypes()' line #984



repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
Lines 214 (patched)


code duplicated. Try to use 'changedTypeDefs' to include 
'changedBusinessMetadataDefs'


- Sarath Subramanian


On April 6, 2020, 11:20 p.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72317/
> ---
> 
> (Updated April 6, 2020, 11:20 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
> Nixon Rodrigues, Sarath Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-3709
> https://issues.apache.org/jira/browse/ATLAS-3709
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Resolved issues in conjunction with Business Metadata attributes.
> Also handled index populate for Business Metadata attributes at the time of 
> start up.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/listener/ChangedTypeDefs.java 58e889a 
>   intg/src/main/java/org/apache/atlas/type/AtlasTypeRegistry.java 9df89a2 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  647e304 
> 
> 
> Diff: https://reviews.apache.org/r/72317/diff/1/
> 
> 
> Testing
> ---
> 
> Pre-commit 
> https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1784/console
> 
> Manual testing done.
> 
> CASE:1
> 1. create Busines meatadata "BM1" 
> 2. add one attribute "attr1" in "BM1" (search weight 9)
> 3. create one entity "hdfsentity1"
> 4. associate "attr1" to "hdfsentity1"
> 5. check in quick search and suggestions for "attr1" value
> 
> 6. add another attribute "attr2" in "BM1" (search weight 9)
> 7. associate "attr2" to "hdfsentity1"
> 8. check in quick search and suggestions
> 
> 
> CASE:2
> 1. create Busines meatadata "BM1" 
> 2. add one attribute "attr1" in "BM1" (search weight 9)
> 3. create one entity "hdfsentity1"
> 4. associate "attr1" to "hdfsentity1"
> 5. check in quick search and suggestions for "attr1" value
> 
> 6. add another attribute "attr2" in "BM1" (search weight 10)
> 7. associate "attr2" to "hdfsentity1"
> 8. check in quick search and suggestions for "attr1" and "attr2" values
> 
> 
> CASE:3
> 1. create Busines meatadata "BM1" 
> 2. add one attribute "attr1" in "BM1" (search weight 9)
> 3. create one entity "hdfsentity1"
> 4. associate "attr1" to "hdfsentity1"
> 5. check in quick search and suggestions for "attr1" value
> 
> 6. create another Busines meatadata "BM2" 
> 7. add attribute "attr2" in "BM2" (search weight 9)
> 8. associate "attr2" to "hdfsentity1"
> 9. check in quick search and suggestions for "attr1" and "attr2" values
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>