Posted by
Jacky Li on
URL: http://apache-carbondata-dev-mailing-list-archive.168.s1.nabble.com/Improving-show-segment-info-tp91874p91884.html
> 2020年2月16日 下午4:58，akashrn5 <
[hidden email]> 写道：
>
> Hi likun,
>
> Thanks for proposing this
>
> +1, its a good way and its better to provide user more info about segment.
>
> I have following doubts and suggestions.
>
> 1. You have mentioned DDL as Show segments On table, but currently it is
> show segments for table, i suggest not to change the current one,we can add
> more optional fields for more segment info.
Agree
>
> 1. Incase of multiple partiton columns,the partition info can be huge, in
> that case what is the format you are trying to show in sow segment with
> partition.
> Can we ask user to give partition column also as optional field in command?
> So that if there are multiple partition columns, we can reduce the info in
> output to make the info more clean.
>
> When the optional field of partiton column is not given, then we should have
> a better formatting to show the huge information.
>
> DDL should be something like
>
> SHOW SEGMENTS ON table1 PARTITION (workgroupcategory int)
>
> SHOW SEGMENTS ON table1 PARTITION (workgroupcategory int, empname String,
> designation String)
>
I got your point, but given the partition column by user does not help reducing the information. If we want to reduce the amount of the information, we should ask user to give the filter on partition column like example 3 in my original mail.
> 2. You have shown the comand which filter out the partition, i think its
> better if we can filter out the partition columns also as mentioned in above
> case, what do you say?
Do you mean skip the partition columns in the SHOW SEGMENTS result? For example 3.
>
> 3. already show segments have 9 columns as output and for show history its
> 10 columns, now to these basic info event time and load speed is getting
> added, if i am not wrong.
> in the sample output its shown that there is a spent column, i think its not
> required as we have throughput column.
No, by showing example 1, actually I want to change the default output of the SHOW SEGMENTS to those 6 fields only in example 1.
I suggest having both `spent` and `throughput` so that user does not need to calculate himself.
>
> One suggestion is, why cant we merge loadstart and endtime, event time min
> and max, data and index size as single columns with proper formatted data?
> With this we can
> reduce the size of output in cnsole size and include more columns in basic
> output.
In example 1, only 6 fields are shown, and some field name changed (like for SegmentSequenceId changed to ID) to make it shorter.
I have tested these 6 fields can fit in console in one line.