Dynamodb scan till end of segment
up vote
0
down vote
favorite
I have a large DynamoDB (not huge around 20GB) that holds items with expiry time stamps.
We are having 32 parallel scanner reading the database while other entries are added to database from other parts of the system.
This is the code that we have at the moment
val scanRequest = ScanRequest
.builder()
.tableName(tableName)
.filterExpression("expiryDate < :date")
.expressionAttributeValues(mapOf(":date" to expiredThreshold).asAttributeValueMap())
.totalSegments(totalSegments)
.segment(segment)
.limit(1000)
.exclusiveStartKey(lastEvaluatedKey)
.build()
val scanResult = client.scan(scanRequest).asDeferred().await()
lastEvaluatedKey = scanResult.lastEvaluatedKey()
I have several concerns regarding this pattern.
- Would we ever reach the end of each segment by having this in a while or not? If so, how can we know if the end has been reached or not?
- Would the items that are being added from other part go before the lastEvaluatedKey or everything would go after?
- What would be a good indication for starting reading again from the beginning of the segment?
amazon-dynamodb
add a comment |
up vote
0
down vote
favorite
I have a large DynamoDB (not huge around 20GB) that holds items with expiry time stamps.
We are having 32 parallel scanner reading the database while other entries are added to database from other parts of the system.
This is the code that we have at the moment
val scanRequest = ScanRequest
.builder()
.tableName(tableName)
.filterExpression("expiryDate < :date")
.expressionAttributeValues(mapOf(":date" to expiredThreshold).asAttributeValueMap())
.totalSegments(totalSegments)
.segment(segment)
.limit(1000)
.exclusiveStartKey(lastEvaluatedKey)
.build()
val scanResult = client.scan(scanRequest).asDeferred().await()
lastEvaluatedKey = scanResult.lastEvaluatedKey()
I have several concerns regarding this pattern.
- Would we ever reach the end of each segment by having this in a while or not? If so, how can we know if the end has been reached or not?
- Would the items that are being added from other part go before the lastEvaluatedKey or everything would go after?
- What would be a good indication for starting reading again from the beginning of the segment?
amazon-dynamodb
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a large DynamoDB (not huge around 20GB) that holds items with expiry time stamps.
We are having 32 parallel scanner reading the database while other entries are added to database from other parts of the system.
This is the code that we have at the moment
val scanRequest = ScanRequest
.builder()
.tableName(tableName)
.filterExpression("expiryDate < :date")
.expressionAttributeValues(mapOf(":date" to expiredThreshold).asAttributeValueMap())
.totalSegments(totalSegments)
.segment(segment)
.limit(1000)
.exclusiveStartKey(lastEvaluatedKey)
.build()
val scanResult = client.scan(scanRequest).asDeferred().await()
lastEvaluatedKey = scanResult.lastEvaluatedKey()
I have several concerns regarding this pattern.
- Would we ever reach the end of each segment by having this in a while or not? If so, how can we know if the end has been reached or not?
- Would the items that are being added from other part go before the lastEvaluatedKey or everything would go after?
- What would be a good indication for starting reading again from the beginning of the segment?
amazon-dynamodb
I have a large DynamoDB (not huge around 20GB) that holds items with expiry time stamps.
We are having 32 parallel scanner reading the database while other entries are added to database from other parts of the system.
This is the code that we have at the moment
val scanRequest = ScanRequest
.builder()
.tableName(tableName)
.filterExpression("expiryDate < :date")
.expressionAttributeValues(mapOf(":date" to expiredThreshold).asAttributeValueMap())
.totalSegments(totalSegments)
.segment(segment)
.limit(1000)
.exclusiveStartKey(lastEvaluatedKey)
.build()
val scanResult = client.scan(scanRequest).asDeferred().await()
lastEvaluatedKey = scanResult.lastEvaluatedKey()
I have several concerns regarding this pattern.
- Would we ever reach the end of each segment by having this in a while or not? If so, how can we know if the end has been reached or not?
- Would the items that are being added from other part go before the lastEvaluatedKey or everything would go after?
- What would be a good indication for starting reading again from the beginning of the segment?
amazon-dynamodb
amazon-dynamodb
asked Nov 13 at 9:44
Khashayar
98721326
98721326
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53278077%2fdynamodb-scan-till-end-of-segment%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown