[druid] branch master updated: Document data format and example for featureSpec (#12394)

[te...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

techdocsmith pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git


The following commit(s) were added to refs/heads/master by this push:
     new e6229b76a6 Document data format and example for featureSpec (#12394)
e6229b76a6 is described below

commit e6229b76a68add5dd02165b5ade78a37189173eb
Author: Victoria Lim <vt...@users.noreply.github.com>
AuthorDate: Wed Apr 6 15:17:15 2022 -0700

    Document data format and example for featureSpec (#12394)
    
    * add data format and example for featureSpec
    
    * add second feature in example
    
    * Apply suggestions from code review
    
    Co-authored-by: Charles Smith <te...@gmail.com>
    
    Co-authored-by: Charles Smith <te...@gmail.com>
---
 docs/ingestion/data-formats.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/ingestion/data-formats.md b/docs/ingestion/data-formats.md
index 1587273408..dbce610c21 100644
--- a/docs/ingestion/data-formats.md
+++ b/docs/ingestion/data-formats.md
@@ -74,8 +74,8 @@ parsing data is less efficient than writing a native Java parser or using an ext
 
 ## Input format
 
-> The Input Format is a new way to specify the data format of your input data which was introduced in 0.17.0.
-Unfortunately, the Input Format doesn't support all data formats or ingestion methods supported by Druid yet.
+You can use the `inputFormat` field to specify the data format for your input data.
+> `inputFormat` doesn't support all data formats or ingestion methods supported by Druid yet.
 Especially if you want to use the Hadoop ingestion, you still need to use the [Parser](#parser).
 If your data is formatted in some format not listed in this section, please consider using the Parser instead.
 
@@ -89,7 +89,7 @@ Configure the JSON `inputFormat` to load JSON data as follows:
 |-------|------|-------------|----------|
 | type | String | Set value to `json`. | yes |
 | flattenSpec | JSON Object | Specifies flattening configuration for nested JSON data. See [`flattenSpec`](#flattenspec) for more info. | no |
-| featureSpec | JSON Object | [JSON parser features](https://github.com/FasterXML/jackson-core/wiki/JsonParser-Features) supported by Jackson library. Those features will be applied when parsing the input JSON data. | no |
+| featureSpec | JSON Object | [JSON parser features](https://github.com/FasterXML/jackson-core/wiki/JsonParser-Features) supported by Jackson, a JSON processor for Java. The features control parsing of the input JSON data. To enable a feature, map the feature name to a Boolean value of "true". For example: `"featureSpec": {"ALLOW_SINGLE_QUOTES": true, "ALLOW_UNQUOTED_FIELD_NAMES": true}` | no |
 
 For example:
 ```json
@@ -155,7 +155,7 @@ Be sure to change the `delimiter` to the appropriate delimiter for your data. Li
 
 Configure the Kafka `inputFormat` to load complete kafka records including header, key, and value. 
 
-> That Kafka inputFormat is currently designated as experimental.
+> That Kafka `inputFormat` is currently designated as experimental.
 
 | Field | Type | Description | Required |
 |-------|------|-------------|----------|
@@ -584,7 +584,7 @@ For example:
 
 ### FlattenSpec
 
-The `flattenSpec` bridges the gap between potentially nested input data (such as JSON, Avro, etc) and Druid's flat data model. It is an object within the `inputFormat` object.
+The `flattenSpec` object bridges the gap between potentially nested input data, such as JSON or Avro, and Druid's flat data model. It is an object within the `inputFormat` object.
 
 Configure your `flattenSpec` as follows:
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org