dhavaljrajpara opened a new pull request, #1375:
URL: https://github.com/apache/ranger/pull/1375

   ## What changes were proposed in this pull request?
   
   **Problem Statement**
   
   Currently, columns in several listing tables rendered in the Apache Ranger 
UI (such as Audit Listing and User Listing) cannot be resized. When fields like 
User Name  contain long text values, the text gets truncated or wraps 
awkwardly, making the page difficult to read and use.
   
   **Proposed Solution**
   
   Enable column resizing in Ranger UI listing tables—starting with User Name  
columns across all tables (along with any additional columns identified)—so 
users can adjust column widths to view long text clearly.
   
   **Steps to Reproduce**
   
   Log in to the Ranger Admin UI.
   Navigate to Audit (Access Audits) or Settings -> Users/Groups/Roles (User 
Listing).
   Observe records with long User Name Values and attempt to resize the column 
header.
   
   **Acceptance Criteria**
   
   Users can drag and resize User Name columns across Ranger UI listing tables 
(e.g., Audit Listing, User Listing).
   Resizing a column adjusts its width smoothly without breaking table 
alignment, horizontal scrolling, or pagination controls.
   Long text values become fully readable when the column width is expanded.
   
   
   ## How was this patch tested?
   * Manually verified column resizing for *User Name*  columns across Ranger 
UI listing tables (Audit Listing, User Listing).
   * Confirmed long text values become fully readable upon widening the columns 
without breaking table alignment, horizontal scrolling, or pagination.
   * Verified that existing sorting, filtering, and pagination features 
continue to work without regressions.
   


-- 
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]

Reply via email to