From 3d6fc2dfd5ff2de3771baf96eec09264b1ccc64a Mon Sep 17 00:00:00 2001 From: Ruslan Iushchenko Date: Fri, 29 May 2020 09:10:53 +0200 Subject: [PATCH] #291 Add documentation for the new feature. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f8359063..cb87bb1c 100644 --- a/README.md +++ b/README.md @@ -1054,7 +1054,7 @@ Again, the full example is available at | .option("non_terminals", "GROUP1,GROUP2") | Specifies groups to also be added to the schema as string fields. When this option is specified, the reader will add one extra data field after each matching group containing the string data for the group. | | .option("generate_record_id", false) | Generate autoincremental 'File_Id' and 'Record_Id' fields. This is used for processing record order dependent data. | | .option("with_input_file_name_col", "file_name") | Generates a column containing input file name for each record (Similar to Spark SQL `input_file_name()` function). The column name is specified by the value of the option. This option only works for variable record length files. For fixed record length files use `input_file_name()`. | -| .option("debug", "false") | If true, each primitive field will be accompanied by a debug field specifying raw bytes in hexadecimal. | +| .option("debug", "hex") | If specified, each primitive field will be accompanied by a debug field containing raw bytes from the source file. Possible values: `none` (default), `hex`, `binary`. The legacy value `true` is supported and will generate debug fields in HEX. | ##### Variable record length files options