Fix typos on S3 sink documentation (#4862)

* Fix typos on S3 sink documentation

Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>

* Update _data-prepper/pipelines/configuration/sinks/s3.md

Co-authored-by: Chris Moore <107723039+cwillum@users.noreply.github.com>
Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>

---------

Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Co-authored-by: Chris Moore <107723039+cwillum@users.noreply.github.com>
This commit is contained in:
Naarcha-AWS 2023-08-23 12:49:46 -05:00 committed by GitHub
parent ed21ec74cf
commit 1250649984
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions

View File

@ -133,12 +133,12 @@ Option | Required | Type | Description
The `parquet` codec writes events into a Parquet file.
You must set the `buffer_type` to `multipart` when using Parquet.
The Parquet codec writes data using the Avro schema.
In general, you should define your own schema because it will most accurately reflect your needs.
The Parquet codec writes data using the Avro schema. However, we generally recommend that you define your own schema so that it can best meet your needs.
In cases where your data is uniform, you may be able to automatically generate a schema.
Automatically generated schemas are based on the first event received by the codec.
The schema will only have keys from this event, so you must have all keys present in all events for the auto-schema generation to produce a working schema.
Auto-generated schemas make all fields nullable.
The schema will only contain keys from this event. Therefore, you must have all keys present in all events in order for the automatically generated schema to produce a working schema.
Automatically generated schemas make all fields nullable.
Option | Required | Type | Description