You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two sets of dynamo integrations (where * are all of the dynamo query and mutate APIs):
table.*
$AWS.DynamoDB.*
Currently table.* uses a contract specific to AppSync:
table.query returns { items: [...], nextToken: "", scanCount: number }
But nextToken is a concept that appsync made up, it isn't something we easily recreate in functionless.
Could recreate by encrypting and encoding the token, but this assumes that appsync is the only integration that has a unique contract and that all other services must follow them
Could use the dynamo contract, but app sync cannot do that as the LastEvaluatedKey is obfuscated in the next token and not returned.
Options:
All integrations with dynamo tables conform to appsync's contract table.query
Breaking change that creates a set of table APIs for only app sync, leaving table.* for services that use dynamo's contract (ex: step functions, lambda)
The text was updated successfully, but these errors were encountered:
There are two sets of dynamo integrations (where
*
are all of the dynamo query and mutate APIs):table.*
$AWS.DynamoDB.*
Currently
table.*
uses a contract specific to AppSync:table.query
returns{ items: [...], nextToken: "", scanCount: number }
But
nextToken
is a concept that appsync made up, it isn't something we easily recreate in functionless.Options:
table.query
table.*
for services that use dynamo's contract (ex: step functions, lambda)The text was updated successfully, but these errors were encountered: