[
https://issues.apache.org/jira/browse/ATLAS-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-3738:
--------------------------------------
Assignee: Mandar Ambawane
> [Business Metadata] Suggestions does not honour Business Metadata Attribute's
> Search Weight value
> -------------------------------------------------------------------------------------------------
>
> Key: ATLAS-3738
> URL: https://issues.apache.org/jira/browse/ATLAS-3738
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Umesh Padashetty
> Assignee: Mandar Ambawane
> Priority: Critical
> Attachments: Screenshot 2020-04-20 at 4.02.28 PM.png, Screenshot
> 2020-04-20 at 4.02.36 PM.png
>
>
> In the new Business Metadata UI, the user can provide the search weight for
> each attribute. This search weight is used in quick search and suggestions
> API, to list the values based on their search weight. An attribute with a
> search weight 10 appears before the attribute with a search weight of 9, when
> they have the same attribute values.
> Defined BM attributes, with search weight in the following order
> * Test2A1 = Test2A3 > Test1A1 > Test3A1 > Test4A1
> where Test1, Test2... are the Business Metadatas.
> Added these BM attributes to the entities with values <key_name>+value for
> better clarity.
> As per the functionality, suggestions should be listed in below order when I
> enter "test"
> * test2a1value
> * test2a3value
> * test1a1value
> * test3a1value
> * test4a1value
> but they are listed as
> * test2a1value
> * test3a1value
> * test1a1value
> * test4a1value
> * test2a3value
> Quick search, on the other hand, works fine. Also, the following logs were
> observed in atlas/application.log when I enter a search pattern in quick
> search/suggestion box.
> {code:java}
> 2020-04-20 10:39:15,969 WARN - [etp851765426-201 -
> 56181e81-11e6-4e02-a23a-d72940f3703c:] ~ Could not convert given VERTEX index
> query: [test1a1value] (IndexSerializer:626)
> 2020-04-20 10:39:15,978 WARN - [etp851765426-201 -
> 56181e81-11e6-4e02-a23a-d72940f3703c:] ~ Could not convert given VERTEX index
> query: [test1a1value] (IndexSerializer:626)
> 2020-04-20 10:39:24,733 WARN - [etp851765426-160 -
> d0030733-2fb9-4dfc-8659-7a3c62415ee0:] ~ Could not convert given VERTEX index
> query: [test1a1value*] (IndexSerializer:626)
> 2020-04-20 10:39:24,784 WARN - [etp851765426-160 -
> d0030733-2fb9-4dfc-8659-7a3c62415ee0:] ~ Could not convert given VERTEX index
> query: [test1a1value*] (IndexSerializer:626)
> 2020-04-20 10:39:26,831 WARN - [etp851765426-201 -
> 7d11aa19-e517-4157-a86c-9ce25a19c1ab:] ~ Could not convert given VERTEX index
> query: [te*] (IndexSerializer:626)
> 2020-04-20 10:39:26,861 WARN - [etp851765426-201 -
> 7d11aa19-e517-4157-a86c-9ce25a19c1ab:] ~ Could not convert given VERTEX index
> query: [te*] (IndexSerializer:626)
> 2020-04-20 10:39:27,342 WARN - [etp851765426-160 -
> 66c8be42-f375-4707-bc51-5f0c592828dc:] ~ Could not convert given VERTEX index
> query: [test*] (IndexSerializer:626) {code}
> Attached screenshots.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
