Skip to content

Commit

Permalink
Merge pull request #1245 from kris-watts-gravwell/next-patch
Browse files Browse the repository at this point in the history
clean up some wording
  • Loading branch information
ashnwade authored Nov 6, 2024
2 parents f84bbd3 + bcc54be commit 2cb70cb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion ingesters/preprocessors/jsonextract.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ The JSON Extraction preprocessor Type is `jsonextract`.

* `Extractions` (string, required): This specifies the field or fields (comma-separated) to be extracted from the JSON. Given an input of `{"foo":"a", "bar":2, "baz":{"frog": "womble"}}`, you could specify `Extractions=foo`, `Extractions=foo,bar`, `Extractions=baz.frog,foo`, etc.
* `Force-JSON-Object` (boolean, optional): By default, if a single extraction is specified the preprocessor will replace the entry contents with the contents of that extension; thus selecting `Extraction=foo` will change an entry containing `{"foo":"a", "bar":2, "baz":{"frog": "womble"}}` to simply contain `a`. If this option is set, the preprocessor will always output a full JSON structure, e.g. `{"foo":"a"}`.
* `Drop-Misses` (boolean, optional): If set to true, the preprocessor will drop entries for which it was unable to extract the requested fields. By default, these entries are passed.
* `Drop-Misses` (boolean, optional): If set to true, the preprocessor will drop entries for which it was unable to extract any of the requested fields. By default, these entries are passed if any field is extracted.
* `Strict-Extraction` (boolean, optional): By default, the preprocessor will pass along an entry if at least one of the extractions succeeds. If this parameter is set to true, it will require that all extractions succeed.

## Common Use Cases
Expand Down

0 comments on commit 2cb70cb

Please sign in to comment.