Sorry that I cannot access the document in jira. In my opinion, both for the SORT_COLUMNS in current implementation and for the LOCATION_COLUMNS in the proposal, carbondata tries to organize the data in some order.
So the kernel of the proposal is that, for the SORT_COLUMNS, we can specify a algorithm for the order of sort. By default it is MIN_MAX-INCREASE sort, and more sort can be introduced such as INVERSE_MIN_MAX-INCRESAE sort or Z-ORDER sort. For the implementation, we can define a sort factory and implement some, and also keep it open for the users' customization just like column_compressor we implemented before. -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
