[GitHub] [pinot] jayeshchoudhary commented on issue #10504: Optimize controller UI for large cluster/tables

["jayeshchoudhary (via GitHub)" <gi...@apache.org>]

jayeshchoudhary commented on issue #10504:
URL: https://github.com/apache/pinot/issues/10504#issuecomment-1490928042

   I think this is more related to the backend. Currently, UI calls idealState and externalView APIs to show segments. 
   If there are 100 segments the API response will be faster, if there are 100k segments the API response will be slow. so UI can't do anything here to compensate for the slowness.
   
   IMO we should have some pagination/search in the API, which UI can leverage to only show a subset of the segments. 
   But, I don't know the userflow here. maybe we always want to look at all the segments? or if we show only a subset of segments how do we consume them?
   
   We can think about the common workflows here and decide based on user behavior. After this, there will be backend + UI changes.


-- 
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: commits-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org