Prasad P. Pawar created ATLAS-5192:
--------------------------------------
Summary: 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
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)
