Github user zzcclp commented on a diff in the pull request: https://github.com/apache/carbondata/pull/1205#discussion_r130581766 --- Diff: docs/dml-operation-on-carbondata.md --- @@ -149,6 +149,50 @@ You can use the following options to load data: * If this option is set to TRUE, then high.cardinality.identify.enable property will be disabled during data load. +- **SORT_SCOPE:** This property can have four possible values : + + * BATCH_SORT : The sorting scope is smaller and more index tree will be created,thus loading is faster but query maybe slower. + + * LOCAL_SORT : The sorting scope is bigger and one index tree per data node will be created, thus loading is slower but query is faster. + + * GLOBAL_SORT : The sorting scope is bigger and one index tree per task will be created, thus loading is slower but query is faster. + + * NO_SORT : Feasible if we want to load our data in unsorted manner. + + For BATCH_SORT: + + ``` + OPTIONS ('SORT_SCOPE'='BATCH_SORT') + ``` + + You can also specify the sort size option for sort scope. + + ``` + OPTIONS('SORT_SCOPE'='BATCH_SORT', 'batch_sort_size_inmb'='7') + ``` + + Note : + + * batch_sort_size_inmb : Size of data in MB to be processed in batch. By default it is the 45 percent size of sort.inmemory.size.inmb(Memory size in MB available for in-memory sort). + + For GLOBAL_SORT : --- End diff -- I mean that if SORT_SCOPE=GLOBAL_SORT,single_pass must be false
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---