dapr / dapr/components-contrib

[AWS DynamoDB] Support consistent vs eventual-consistent read

Open
#246 2 comments 0 reactions 0 assignees View on GitHub
area/runtime/state good first issue
Dominant language
Go
Stars
602
Forks
580
Avg merge
4d 9h
Merged PRs (30d)
6

Description

Support metadata indicating whether the read is consistent and eventual-consistent.

My recommendation is for default to be consistent read.

Contributor guide

Open the contributing guide

Research direction

Start by locating the AWS DynamoDB component and reading its read entry point to understand how read options are currently passed. Determine how consistency metadata should be represented and confirm whether the default should be consistent, then verify the behavior with the component's existing tests or add coverage if the repository provides it.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go
Domain
databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.