carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jackylk <...@git.apache.org>
Subject [GitHub] carbondata pull request #1219: [CARBONDATA-1117]updated configuration-parame...
Date Thu, 03 Aug 2017 14:33:23 GMT
Github user jackylk commented on a diff in the pull request:

    https://github.com/apache/carbondata/pull/1219#discussion_r131159058
  
    --- Diff: docs/configuration-parameters.md ---
    @@ -143,5 +144,87 @@ This section provides the details of all the configurations required
for CarbonD
     |----------------------------------------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
     | spark.driver.memory | 1g | Amount of memory to be used by the driver process. |
     | spark.executor.memory | 1g | Amount of memory to be used per executor process. |
    -   
    - 
    +
    +##  Dynamic Configuration In CarbonData Using SET-RESET
    +
    +**SET/RESET** commands are used to add, update, display, or reset the carbondata properties
dynamically without restarting the driver.
    +
    +**Syntax**
    +
    +* **Add or Update :** This command adds or updates the value of parameter_name.
    +
    +```
    +SET parameter_name=parameter_value
    +```
    +
    +* Display Property Value: This command displays the value of the specified parameter_name.
    +
    +```
    +SET parameter_name
    +```
    +
    +* Display Session Parameters: This command displays all the supported session parameters.
    +
    +```
    +SET
    +```
    +
    +* Display Session Parameters along with usage details: This command displays all the
supported session parameters along with their usage details.
    +
    +```
    +SET -v
    +```
    +
    +* Reset: This command clears all the session parameters.
    +
    +```
    +RESET
    +```
    +
    + **Parameter Description:**
    +
    +| Parameter       | Description                                                     
                      |
    +|-----------------|----------------------------------------------------------------------------------------|
    +| parameter_name  | Name of the property whose value needs to be dynamically added, updated,
or displayed. |
    +| parameter_value | New value of the parameter_name to be set.                      
                      |
    +
    +<b><p align="center">Dynamically Configurable Properties of CarbonData</p></b>
    +
    +| Properties                               | Description                            
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                               |
    +|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
    +| carbon.options.bad.records.logger.enable | To enable or disable bad record logger.
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                               |
    +| carbon.options.bad.records.action        | This property can have four types of actions
for bad records FORCE, REDIRECT, IGNORE and FAIL. If set to FORCE then it auto-corrects the
data by storing the bad records as NULL. If set to REDIRECT then bad records are written to
the raw CSV instead of being loaded. If set to IGNORE then bad records are neither loaded
nor written to the raw CSV. If set to FAIL then data loading fails if any bad records are
found.                                                                                   
                                                                      |
    +| carbon.options.is.empty.data.bad.record  | If false, then empty ("" or '' or ,,) data
will not be considered as bad record and vice versa.                                     
                                                                                         
                                                                                         
                                                                                         
                                                                                         
                                                                            |
    +| carbon.options.sort.scope                | This property can have four possible values
BATCH_SORT, LOCAL_SORT, GLOBAL_SORT and NO_SORT. If set to BATCH_SORT, the sorting scope is
smaller and more index tree will be created,thus loading is faster but query maybe slower.
If set to 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. If set to GLOBAL_SORT, the sorting scope
is bigger and one index tree per task will be created, thus loading is slower but query is
faster. If set to NO_SORT data will be loaded in unsorted manner. |
    --- End diff --
    
    Description for GLOBAL_SORT is wrong, not per task


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message