So what’s your proposal for the grammar of this feature?
Do you want carbon to do it silently without any configurations or choices from
user?
What I am concerned about is that the performance of compaction. If user use
auto-compaction, the loading will be more delayed if we do compaction using
Hi Xuchuanyin
The scope for this feature is to SORT the data during compaction when the
data is loaded using NO_SORT option during data load operation.
There are few users who want to maximize the data load speed and in turn
fine tune the data further during off peak time (time when system is
currently , what i have thought is, if all the loads involved for compaction
are no sort then only we will sort during compaction. So currently we have
table level, that is fine. So if the table has no_sort during compaction it
will be sorted , if local sort it will go to current compaction flow.
What’s your proposal for the corresponding grammar to do that?
Besides, if we only sort after compaction, will it be proper to keep the
sort_scope in table level? It should be in segment level in this situation and
keep it in table level will confuse the user. How do you consider this?
Sent
