ATLAS-5192: Atlas React UI: Align Table tab relationship search with Classic UI #502
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pawarprasad123
requested review from
chaitalicod,
mandarambawane and
pinal-shah
chaitalicod
approved these changes
Jan 22, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
