You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: open-source/ingestion/destination-connectors/s3.mdx
+18-16Lines changed: 18 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,22 +10,6 @@ import SharedS3 from '/snippets/dc-shared-text/s3-cli-api.mdx';
10
10
11
11
<SharedS3 />
12
12
13
-
Now call the Unstructured Ingest CLI or the Unstructured Ingest Python library. The source connector can be any of the ones supported. This example uses the local source connector.
14
-
15
-
This example sends files to Unstructured for processing by default. To process files locally instead, see the instructions at the end of this page.
## Create a pipeline that uses S3 as the destination
32
+
33
+
Now call the Unstructured Ingest CLI or the Unstructured Ingest Python library. The source connector can be any of the ones supported. This example uses the local source connector.
34
+
35
+
This example sends files to Unstructured for processing by default. To process files locally instead, see the instructions at the end of this page.
-[Editing object metadata in the Amazon S3 console](https://docs.aws.amazon.com/AmazonS3/latest/userguide/add-object-metadata.html)
10
+
11
+
Unstructured outputs any user-defined metadata that it finds for a file into the `metadata.data_source.record_locator.metadata` field of
12
+
the document elements' output for the corresponding file. For example, if Unstructured processes a file with the user-defined metadata
13
+
`x-amz-meta-mymetadata` name set to the value `myvalue`, Unstructured outputs the following into the `metadata.data_source.record_locator.metadata` field of
14
+
the document elements' output for the corresponding file:
0 commit comments