Indhumathi27 commented on a change in pull request #3740:
URL: https://github.com/apache/carbondata/pull/3740#discussion_r419971435



##########
File path: docs/configuration-parameters.md
##########
@@ -206,21 +206,18 @@ RESET
 
 | Properties                                | Description                      
                            |
 | ----------------------------------------- | 
------------------------------------------------------------ |
-| carbon.options.bad.records.logger.enable  | CarbonData can identify the 
records that are not conformant to schema and isolate them as bad records. 
Enabling this configuration will make CarbonData to log such bad 
records.**NOTE:** If the input data contains many bad records, logging them 
will slow down the over all data loading throughput. The data load operation 
status would depend on the configuration in ***carbon.bad.records.action***. |
-| 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.bad.records.logger.enable  | To enable or disable a bad 
record logger. CarbonData can identify the records that are not conformant to 
schema and isolate them as bad records. Enabling this configuration will make 
CarbonData to log such bad records.**NOTE:** If the input data contains many 
bad records, logging them will slow down the overall data loading throughput. 
The data load operation status would depend on the configuration in 
***carbon.bad.records.action***. |                   |
+| carbon.options.bad.records.action         | This property has four types of  
bad record actions: 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.batch.sort.size.inmb       | Size of batch data to keep in 
memory, as a thumb rule it supposed to be less than 45% of 
sort.inmemory.size.inmb otherwise it may spill intermediate data to disk. |
 | carbon.options.bad.record.path            | Specifies the HDFS path where 
bad records needs to be stored. |
 | carbon.custom.block.distribution          | Specifies whether to use the 
Spark or Carbon block distribution feature.**NOTE: **Refer to [Query 
Configuration](#query-configuration)#carbon.custom.block.distribution for more 
details on CarbonData scheduler. |

Review comment:
       ```suggestion
   | carbon.custom.block.distribution          | Specifies whether to use the 
Spark or Carbon block distribution feature. **NOTE: ** Refer to [Query 
Configuration](#query-configuration)#carbon.custom.block.distribution for more 
details on CarbonData scheduler. |
   ```




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to