[
https://issues.apache.org/jira/browse/ATLAS-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brijesh Bhalala updated ATLAS-5333:
-----------------------------------
Attachment: Screenshot from 2026-06-30 15-10-02.png
> Atlas React UI: Clearing a Classification search filter triggers 400 Bad
> Request on empty parameters
> -----------------------------------------------------------------------------------------------------
>
> Key: ATLAS-5333
> URL: https://issues.apache.org/jira/browse/ATLAS-5333
> Project: Atlas
> Issue Type: Task
> Components: atlas-core
> Affects Versions: 2.5.0
> Reporter: Brijesh Bhalala
> Assignee: Brijesh Bhalala
> Priority: Major
> Labels: atlas-react
> Attachments: Screenshot from 2026-06-30 15-10-02.png
>
>
> When executing a Basic Search using only a Classification filter (e.g.,
> navigated via the Dashboard Overview cards), clearing that classification
> filter via the "X" button causes the UI to fire an empty search request to
> the backend. The backend rejects this with a {{400 Bad Request}} error.
> Notably, this issue is isolated strictly to the Classification filter;
> clearing a Type (Entity) or Term (Glossary) filter correctly handles the
> empty state without triggering the backend error.
> *Steps to Reproduce:*
> # Navigate to the Dashboard / Overview page.
> # Click on a Classification link inside the overview cards (e.g.,
> {{{}_ALL_CLASSIFICATION_TYPES{}}}).
> # You are navigated to the Search Results page (e.g.,
> {{{}/#/search/searchResult?searchType=basic&tag=_ALL_CLASSIFICATION_TYPES&type={}}}).
> # In the active filters section, click the "X" (clear) button on the
> {{Classification: _ALL_CLASSIFICATION_TYPES}} label.
> *Expected Behavior:* The UI should gracefully handle clearing the last active
> Classification filter exactly as it handles clearing a Type or Term filter.
> It should safely clear the results or prevent the API call from firing with
> entirely empty parameters.
> *Actual Behavior:* Unlike the Type or Term filters, clearing the
> Classification filter bypasses empty-state safety checks and fires a request
> with no parameters ({{{}typeName{}}}, {{{}classification{}}},
> {{{}termName{}}}, and {{queryText}} are all blank). The UI throws the
> following backend error:
>
> json
>
> {
> "errorCode": "ATLAS-400-00-047",
> "errorMessage": "No search parameter was found. One of the following MUST be
> specified in the request; typeName, classification, termName or queryText"
> }
> *Impact:* Inconsistent filter behavior and a poor user experience, resulting
> in a raw JSON backend error being displayed to the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
