[ATLAS-4771] [UI] Extra columns in search page are persistent across types when using search filters

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: atlas-webui
• Assignee: Farhan Khan
• Reporter: Abhishek Pal
• Created: 11/Jul/23 10:22
• Updated: 10/Aug/23 10:34
• Resolved: 10/Aug/23 10:34

Description

When we are using basic search, we can select extra columns which reflect several extra attributes that are associated with the data-type.
If we select an extra column, and search for a new type, search works correctly.
But if we select an extra column for some data type, and add an attribute filter for the search - then change the search type, it gives error, saying the extra column is not present.

Steps:

1. Search for any entity in basic search (say hive_db)
2. Select an extra attribute/column from the columns list (ex. Location for hive_db)
3. Add any attribute filter for the search and perform the search (ex: filter on clusterName is not null for hive_db)
4. Now change the type and perform the search (ex. change to hive_table)

It will give an error saying the extra column is not present for the new type.

Upon inspecting the network requests, when applying search filter along with the extra selected columns, the columns are passed in the new search for a different type