I have the following data in my dynamoDB table.
Here is my code:
const userStatusParams = {
TableName: process.env.USERSTATUS_TABLE,
KeyConditionExpression: "loggedIn = :loggedIn",
ExpressionAttributeValues: {
":loggedIn": true
}
};
var usersResult;
try {
usersResult = await dynamoDbLib.call("query", userStatusParams);
console.log(usersResult);
}catch (e) {
console.log("Error occurred querying for users belong to group.");
console.log(e);
}
Amazon returns back this error:
{ ValidationException: Query condition missed key schema element: userId
at Request.extractError ...
How do I have it return all records where loggedIn == true?
My database is currently structured like this via my serverless.yml config.
phoneNumberTable: #This table is used to track phone numbers used in the system.
Type: AWS::DynamoDB::Table
Properties:
TableName: ${self:custom.phoneNumberTable}
AttributeDefinitions: #UserID in this case will be created once and constantly updated as it changes with status regarding the user.
- AttributeName: phoneNumber
AttributeType: S
KeySchema:
- AttributeName: phoneNumber
KeyType: HASH
ProvisionedThroughput:
ReadCapacityUnits: ${self:custom.dynamoDbCapacityUnits.${self:custom.pstage}}
WriteCapacityUnits: ${self:custom.dynamoDbCapacityUnits.${self:custom.pstage}}
I did a little research into this via other answers but could not figure out for my situation. In other answers they had sort keys but I do not use a sort key here.
If you are doing query
then you have to pass the primary key which in your case is userId
. If you do not have primaryKey
and if you want all the logged in = true
fields then you can do scan
with filterExpression
like this
const userStatusParams = {
TableName: process.env.USERSTATUS_TABLE,
FilterExpression: 'loggedIn = :loggedIn',
ExpressionAttributeValues: {
":loggedIn": true
}
};
var usersResult;
try {
// Do scan
usersResult = await dynamoDbLib.call("scan", userStatusParams);
console.log(usersResult);
}catch (e) {
console.log("Error occurred querying for users belong to group.");
console.log(e);
}
Update: Since the scan
operation is less efficient, the other way to solve this problem is to create a GSI
, with primary key loggedIn
. But the problem here is that you cannot make any field primary key which have boolean
data type.. It has to be number, string, binary
. So to create a gsi
you need to store accepted data type in loggedIn
field instead of boolean
.
Though I am not sure how much performance impact it will have for a table of thousand records but the good thing about gsi
is that you can create them later even on the existing table if in future you find out some performance impact. Also, the number of gsi
you can create on table is limited to 5
. So utilise gsi
wisely.