1. show partition enhanced
I think it's more useful to see the data volume of each partiton,
futhermore, the data volume of every day will an important metric which
cann't be count now.
Sum up, if the partition column is "day, hour"
Shall we focus on these two problem:
Q1: How can we find the data
The problem users concerned is more likely: What partitions do not have
completely loaded?
If wer just add partition-segment list in "show partitions", or
"min/max(timecolumn)" in "show segemnts", the above question can't be
answered clearly.
The recommendation is, add a new cammand "show partit
> 2020年2月17日 下午2:00，akashrn5 写道：
>
> Hi,
>
>>> *1. How about creating a "tableName.segmentInfo" child table for each main
>>> table?* user can query this table and easy to support filter, group by. we
>>> just have to finalize the schema of this table.
> We already have many things like index
> 2020年2月17日 下午2:03，akashrn5 写道：
>
> Hi Ajantha,
>
> I think event time comes into picture when the user has the timestamp
> column, like in timeseries. So only in that case, this column makes sense.
>
> Else it won't be there.
>
> @Likun, correct me if my understanding is wrong.
>
Yes, y
Hi Ajantha,
I think event time comes into picture when the user has the timestamp
column, like in timeseries. So only in that case, this column makes sense.
Else it won't be there.
@Likun, correct me if my understanding is wrong.
Regards,
Akash R Nilugal
--
Sent from:
http://apache-carbond
Hi,
>>*1. How about creating a "tableName.segmentInfo" child table for each main
>>table?* user can query this table and easy to support filter, group by. we
>>just have to finalize the schema of this table.
We already have many things like index tables, datamap tables, just to store
this metadata
3. And about event time. I don't think we need to keep it for every row. It
is a waste of storage size. can we keep in loadMetadetails or file level ?
On Mon, Feb 17, 2020 at 11:10 AM Ajantha Bhat wrote:
> Hi Likun,
>
> I think this display command is hard to maintain if we provide all these
> o
Hi Likun,
I think this display command is hard to maintain if we provide all these
options manually.
*1. How about creating a "tableName.segmentInfo" child table for each main
table?* user can query this table and easy to support filter, group by. we
just have to finalize the schema of this table
Hi,
>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.
1. my concern was if there are more partition co
> 2020年2月16日 下午4:58，akashrn5 写道：
>
> 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 segm
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 c
Hi community,
Currently for SHOW SEGMENT command, carbon will print:
+---+-+---+---+-+---+-+--++
|SegmentSequenceId |Status |Load Start Time|Load End Time
|Merged To|File Format|Data Size|Ind
12 matches
Mail list logo
