Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
1.0.0
-
None
Description
In UI , When string attribute filter contains comma , it is taken as separate attribute filter.
For example basic search : hive_table , filter : description = a , b
POST request body :
{ "excludeDeletedEntities":true, "entityFilters":{ "condition":"AND", "criterion":[ { "attributeName":"description", "operator":"eq", "attributeValue":"a" }, { "attributeName":"b", "operator":"string" } ] }, "tagFilters":null, "attributes":[ ], "limit":25, "offset":0, "typeName":"hive_table", "classification":null }
The search throws 400 Bad request with error notification "Attribute b not found for type hive_table".
This is seen only in UI ,as when search is fired with attributeValue given as "a,b" using REST API , fetches correct results.
{ "excludeDeletedEntities":true, "entityFilters":{ "condition":"AND", "criterion":[ { "attributeName":"description", "operator":"eq", "attributeValue":"a,b" } ] }, "tagFilters":null, "attributes":[ ], "limit":25, "offset":0, "typeName":"hdfs_path", "classification":null }
Attachments
Attachments
Issue Links
- links to