[GitHub] [druid] yuanlihan commented on pull request #9883: Remove payload field from table sys.segment

[GitBox <gi...@apache.org>]

yuanlihan commented on pull request #9883:
URL: https://github.com/apache/druid/pull/9883#issuecomment-645829640


   > But, I believe other fields such as shardSpec, dimensions, and metrics are still useful. What do you think about adding them instead of payload?
   
   Hi @jihoonson 
   I agree that these fields should be useful in some use cases. But I still have some concerns about performance of serializing these fields. Can we add fields when they are needed?
   Note that currently almost all sql queries that scan the `sys.segment` table have a sorting clause. And if there are a large number of segments(more than 1 million segments in my case), it will be really slow to load the `Segments` page of the console. And the frontend page already uses the point query API `/druid/coordinator/v1/datasources/{dataSourceName}/segments/{segmentId}` to get the `payload`.
   
   


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

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



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