[
https://issues.apache.org/jira/browse/ATLAS-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054781#comment-18054781
]
ASF subversion and git services commented on ATLAS-5196:
--------------------------------------------------------
Commit 9a0559d4b721697d350a9606f208e427a634ada3 in atlas's branch
refs/heads/ATLAS-5196 from Prasad Pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9a0559d4b ]
ATLAS-5196: React UI Table tab: Force ascending sort for relationship results
> React UI Table tab: Force ascending sort for relationship results
> -----------------------------------------------------------------
>
> Key: ATLAS-5196
> URL: https://issues.apache.org/jira/browse/ATLAS-5196
> Project: Atlas
> Issue Type: Sub-task
> Components: atlas-webui
> Affects Versions: 3.0.0
> Reporter: Prasad P. Pawar
> Assignee: Prasad P. Pawar
> Priority: Major
> Labels: atlas-react
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The React UI Table tab on entity detail pages (e.g., hive_db) sometimes sends
> sortOrder=DESCENDING, which differs from Classic UI (always ASCENDING). This
> causes mismatched results and empty tables in some cases.
> h3. Scope
> React UI only. Classic UI already uses sortBy=name and sortOrder=ASCENDING.
> h3. Fix Required
> Ensure the relationship search payload always uses:
> * sortBy=name
> * sortOrder=ASCENDING
> and is not overridden by client-side sorting state.
> h3. Files
> * dashboard/src/views/DetailPage/EntityDetailTabs/ProfileTab.tsx
> h3. Validation
> ** Open React UI → entity detail → Table tab
> ** Confirm relationship API request includes sortOrder=ASCENDING
> ** Results match Classic UI ordering
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
