如何在App Sync查询中使用多个全局二级索引及验证查询表达式

1. Using Multiple Global Secondary Indexes (GSIs) in a Single Query #

First off, you cannot specify multiple GSIs in a single DynamoDB Query operation—each Query can only target one index (either a GSI, LSI, or the base table's primary key). This is because DynamoDB's Query is designed to work against a specific key structure (partition key + optional sort key) defined by either the base table or one of its GSIs.

Best Practices & Alternative Solutions #

• Align your GSI with your query pattern: If you have three filter conditions, design a GSI that prioritizes the most frequently used condition as the partition key, then use one or two others as sort keys (DynamoDB supports composite sort keys). For example:
  • If studentId is the most common filter, create a GSI with studentId as the partition key, chapterId as the first sort key, and isUserAudio as the second sort key. You can then use a KeyConditionExpression to match studentId and range conditions on the sort keys, with no need for extra filters.
  • If two conditions are always used together, combine them into a composite partition key (e.g., studentId#chapterId) and use isUserAudio as a sort key or filter.
• Use FilterExpressions for non-key conditions: If one of your conditions can't be part of the GSI's key structure, use a FilterExpression to apply it after the Query retrieves results matching the key conditions. Note that filtering happens post-Query, so it won't reduce the read capacity units consumed, but it will return only the matching items.
• Avoid Scan operations: While a Scan can apply multiple filters without an index, it's inefficient for large tables as it reads every item—reserve this for small datasets or infrequent operations only.

2. Validity of Your AppSync Query Expression & Multiple Indexes #

Expression Validity #

Your provided expression has a syntax error: the logic between chapterId = :chapterId and isUserAudio = :isUserAudio is missing a logical operator (AND/OR). Additionally, when using multiple conditions in a KeyConditionExpression, only the partition key can use an equality check, while sort keys can use range operators (e.g., =, <, >). If some conditions aren't part of the index's key structure, they belong in a FilterExpression instead of the KeyConditionExpression.

Can index Specify Multiple Values? #

No, the index field in an AppSync DynamoDB resolver can only accept a single index name. You can't list multiple indexes here—each resolver Query operation targets exactly one index (or the base table if index is omitted).

Corrected Resolver Example #

Here's a fixed version of your resolver, assuming we're using a GSI with studentId as the partition key, chapterId as the sort key, and filtering on isUserAudio:

{
  "version": "2017-02-28",
  "operation": "Query",
  "query": {
    "keyConditionExpression": "studentId = :studentId AND chapterId = :chapterId",
    "filterExpression": "isUserAudio = :isUserAudio",
    "expressionValues": {
      ":studentId": { "S": "${ctx.args.studentId}" },
      ":chapterId": { "S": "${ctx.args.chapterId}" },
      ":isUserAudio": { "BOOL": ${ctx.args.isUserAudio} }
    }
  },
  "index": "YourGSINameHere" // Replace with your actual GSI name
}

• keyConditionExpression targets the GSI's partition and sort keys (equality checks here since we're matching exact values).
• filterExpression applies the remaining condition (isUserAudio) to the Query results.
• Note: Removed quotes around ${ctx.args.isUserAudio} because it's a boolean value, not a string.

内容的提问来源于stack exchange，提问作者Naveen Vignesh