Hi Community, In JIRA 1014, we are adding Unsafe ColumnPage in data load process to reduce GC, and adding EncodingStrategy for Encoding Overriding features to make open up encoding interface for both usability and extensibility.
When implementing these new features, I found ColumnGroup feature creates unnecessary burden on data loading code and makes developer interfaces more complex to use. For example, since ColumnGroup can appear in any field in the table, even in SORT_COLUMNS, it forces developer to understand ColumnGroup concept and handle it in its encoding implementation. As far as I know, there is not much discussion on ColumnGroup in the mail list and I think it is high possibility that no one is using it. So I am proposing to remove this feature and it can enable carbon to make Encoding interface cleaner for developers. Please vote: A. Remove it B. Not remove it, and provide reason Thanks, Jacky Li
