mdedetrich commented on PR #12: URL: https://github.com/apache/pekko-persistence-dynamodb/pull/12#issuecomment-2419240377
> > This allows to make the choice between time and space efficiency, by selecting the projection strategy for the created index. Depending on the choice, setting this flag for retrieval will make either strategy work as efficient as intended. > > It is optional. You choose which strategy to follow by means of projection setting for the Dynamo index. > > https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html > > > ALL_ATTRIBUTES - Returns all of the item attributes from the specified table or index. If you query a local secondary index, then for each matching item in the index, DynamoDB fetches the entire item from the parent table. If the index is configured to project all item attributes, then all of the data can be obtained from the local secondary index, and no fetching is required. > > So if you configure your index like you had to before, it has no performance implications, but if you switch to keys-only mode, you get the space-time trade-off. Ah I think I am a bit confused here, just to clarify all of these settings are done server side on Amazon Dynamo and so this flag is going to make zero difference wrt behaviour unless you toggle something in AWS Dynamo? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
