Aaron S.

> It seems that partitionKey in KinesisAnalyticsEvent should be optional? Can you provide more information about why it should be optional? Do you have any sample code? Are you encountering...

related to #6935

I have confirmed that updating to the latest version of `@aws-amplify/data-schema` on the sample repo above resolves the type errors. Based on this, I am closing out this issue.

I believe this is possible, but I'm not certain what the best practice is for pipeline resolvers. I'm going to reassign this to the backend repository so that team can...

Looking at the proposed PRs these appear to assume that both data and errors are returned in the case where there are errors, but I don't think that is the...

You've got this working using custom resolvers. In order to automatically offer batch deletion for models, we would need to have this behavior generated in the backend. Once it is...

Hello @Aldo-Garza, Looking over your use-case, we do not currently support building a matrix of elements in the way that you are attempting to do. Could you structure the data...

The schema definition syntax issue that mistakenly allowed for fields of arrays within arrays has been fixed with the latest version of the library. As a bug, this is resolved,...

We looked into that. The graphql schema we're running codegen against isn't finalized until the [cdk artifacts are being composed](https://github.com/aws-amplify/amplify-backend/blob/b7ac6a303a85a306d375b4ef55a375e4aac45ab6/packages/backend-data/src/factory.ts#L229-L232), which supports having multipe schema's [combined into a single API...

You could write customer resolvers that would achieve this, but to be efficient you would be writing a resolver directly against the dynamodb table. This is interesting as a feature...