[
https://issues.apache.org/jira/browse/ATLAS-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053837#comment-18053837
]
ASF subversion and git services commented on ATLAS-5192:
--------------------------------------------------------
Commit ba7b1797160df6acf3924209fe8ea9c11214f24c in atlas's branch
refs/heads/atlas-2.5 from Prasad Pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ba7b17971 ]
ATLAS-5192: Atlas React UI: Align Table tab relationship search with Classic UI
(#502)
( cherry-picked from 01f926bb3dd161d1b537120d188ea5f31ee28d5c)
> Atlas React UI: Align Table tab relationship search with Classic UI
> -------------------------------------------------------------------
>
> Key: ATLAS-5192
> URL: https://issues.apache.org/jira/browse/ATLAS-5192
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
> Affects Versions: 3.0.0
> Reporter: Prasad P. Pawar
> Assignee: Prasad P. Pawar
> Priority: Major
> Labels: atlas-react
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The React UI Table tab on entity detail pages (e.g., hive_db) was showing “No
> Records found” because it wasn’t issuing the same relationship search request
> as the Classic UI. Classic uses the /api/atlas/v2/search/relationship
> endpoint with specific query params and returns related tables; React was
> sending different payload fields and incorrect pagination.
> *Root Cause*
> React Table tab used inconsistent query parameters (order, sort_by) and
> incorrect pagination (offset = pageIndex + pageSize), which resulted in empty
> results.
> Server expects the Classic-style payload with sortBy, sortOrder, and offset =
> pageIndex * pageSize.
> *Fix Implemented*
> Updated React ProfileTab Table tab request to match Classic UI:
> Uses sortBy=name, sortOrder=ASCENDING
> Uses offset = pageIndex * pageSize
> Sends excludeDeletedEntities, includeSubClassifications, includeSubTypes,
> includeClassificationAttributes
> For hive_db, calls two relations (__hive_table.db, __iceberg_table.db) and
> merges results
> For hbase_namespace, calls one relation (__hbase_table.namespace)
> *Files Updated*
> dashboard/src/views/DetailPage/EntityDetailTabs/ProfileTab.tsx
> *Test/Validation*
> Open React UI → Entity Detail → Table tab for hive_db
> Confirm relationship API calls are issued with Classic‑style payload
> Verify tables appear and match Classic UI results
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
