metadata-ingestion/docs/sources/dynamodb/dynamodb_post.md
Use the Important Capabilities table above as the source of truth for supported features and whether additional configuration is required.
schema_sampling_size configBy default, the connector samples 100 items from each table to infer the schema. You can adjust this using the schema_sampling_size configuration option if you need more comprehensive schema coverage:
# Sample 500 items instead of default 100
schema_sampling_size: 500
include_table_item configIf there are items that have most representative fields of the table, users could use the include_table_item option to provide a list of primary keys of the table in dynamodb format. We include these items in addition to the items sampled based on schema_sampling_size (default 100) when we scan the table.
Take AWS DynamoDB Developer Guide Example tables and data as an example, if a account has a table Reply in the us-west-2 region with composite primary key Id and ReplyDateTime, users can use include_table_item to include 2 items as following:
Example:
# The table name should be in the format of region.table_name
# The primary keys should be in the DynamoDB format
include_table_item:
us-west-2.Reply:
[
{
"ReplyDateTime": { "S": "2015-09-22T19:58:22.947Z" },
"Id": { "S": "Amazon DynamoDB#DynamoDB Thread 1" },
},
{
"ReplyDateTime": { "S": "2015-10-05T19:58:22.947Z" },
"Id": { "S": "Amazon DynamoDB#DynamoDB Thread 2" },
},
]
Module behavior is constrained by source APIs, permissions, and metadata exposed by the platform. Refer to capability notes for unsupported or conditional features.
If ingestion fails, validate credentials, permissions, connectivity, and scope filters first. Then review ingestion logs for source-specific errors and adjust configuration accordingly.