pawarprasad123 opened a new pull request, #502: URL: https://github.com/apache/atlas/pull/502
## What changes were proposed in this pull request? 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 ## How was this patch tested? Manually <img width="1852" height="1127" alt="Screenshot from 2026-01-22 16-43-13" src="https://github.com/user-attachments/assets/4e6c9a0e-7ff9-435f-98fc-e134082b66ca"; /> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
