Abhishek Pal created ATLAS-4771:
-----------------------------------
Summary: [Atlas][UI] Extra columns in search page are persistent
across types when using search filters
Key: ATLAS-4771
URL: https://issues.apache.org/jira/browse/ATLAS-4771
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Reporter: Abhishek Pal
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:
# Search for any entity in basic search (say {*}hive_db{*})
# Select an extra attribute/column from the columns list (ex. *Location* for
{*}hive_db{*})
# Add any attribute filter for the search and perform the search (ex: filter
on *clusterName is not null* for hive_db)
# 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
