1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
0
In your code snippet, the dynamodb.throughput.write.percent option is set to "1.0", which means you are using 1% of the provisioned write capacity of your DynamoDB table. This is why you're observing a consumption rate of 1 instead of 10,000.
To utilize the increased write capacity of 10,000, you need to update the dynamodb.throughput.write.percent option to "100.0". This will ensure that the Glue job utilizes the full provisioned write capacity of your DynamoDB table.
Here's the updated code snippet:
dynamodb_output_options = {
"dynamodb.region": "us-east-1",
"dynamodb.output.tableName": dynamodb_table,
"dynamodb.throughput.write.percent": "100.0"
}
# Write the DataFrame to DynamoDB
glueContext.write_dynamic_frame.from_options(
frame=ApplyMapping_node2,
connection_type="dynamodb",
connection_options=dynamodb_output_options
)
By setting the dynamodb.throughput.write.percent option to "100.0", the Glue job will fully utilize the provisioned write capacity of your DynamoDB table, which in this case is 10,000 write capacity units.
respondido hace un año
Contenido relevante
- ¿Cómo puedo resolver el error “Failed to start the job flow due to an internal error” en Amazon EMR?OFICIAL DE AWSActualizada hace un mes
- OFICIAL DE AWSActualizada hace un año