Hi
Agree, we don't need to add special constrain for one column be together
existing in partition key and SORT_COLUMNS.
But from actual case, don't suggest giving partition key is same as the
first column of SORT_COLUMNS, maybe we need to add the tips to partition
feature's document.
Regards
Lia
Hi Liang,
Currently the user cannot choose which segments should be merged or not.
We should give a DDL which supports both forceful minor and major
compaction separately.
Another point would be if the user can specify the segments which he needs
merged. Obviously the segments that can be given sh
Hi Kunal
Thank you for taking the good topic for discussion.
First , let us think about : why users want to do forceful minor compaction,
which cases?
Current "MAJOR compaction" whether can cover "forceful MINOR compaction"
scenarios ?
As we know, compaction is mainly for optimizing index effect
Raghunandan S created CARBONDATA-958:
Summary: Schema modified time not updated in modifiedtime.mdt when
dictionary column is updated to no-dictionary column due to high cardinality
Key: CARBONDATA-958
URL: ht
Hi William
+1 for improving CarbonLock Exception.
Do you have any proposed solution for this improvement, and can you raise
one PR for it.
Regards
Liang
Venkata Gollamudi wrote
> Yes, that can be more meaningful, detailing the exception type. Any
> related
> changes are welcome.
>
> On Wed, A
