Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

InputDataConfig

import type { InputDataConfig } from "https://aws-api.deno.dev/v0.3/services/comprehend.ts?docs=full";

The input properties for an inference job.

interface InputDataConfig {
DocumentReaderConfig?: DocumentReaderConfig | null;
InputFormat?: InputFormat | null;
S3Uri: string;
}

§Properties

§
DocumentReaderConfig?: DocumentReaderConfig | null
[src]

The document reader config field applies only for InputDataConfig of StartEntitiesDetectionJob.

Use DocumentReaderConfig to provide specifications about how you want your inference documents read. Currently it applies for PDF documents in StartEntitiesDetectionJob custom inference.

§
InputFormat?: InputFormat | null
[src]

Specifies how the text in an input file should be processed:

  • ONE_DOC_PER_FILE - Each file is considered a separate document. Use this option when you are processing large documents, such as newspaper articles or scientific papers.
  • ONE_DOC_PER_LINE - Each line in a file is considered a separate document. Use this option when you are processing many short documents, such as text messages.
§
S3Uri: string
[src]

The Amazon S3 URI for the input data. The URI must be in same region as the API endpoint that you are calling. The URI can point to a single input file or it can provide the prefix for a collection of data files.

For example, if you use the URI S3://bucketName/prefix, if the prefix is a single file, Amazon Comprehend uses that file as input. If more than one file begins with the prefix, Amazon Comprehend uses all of them as input.