Feature Requests for RDS DataSource

I have a few feature requests for AppSync:

1) I see there is solution for the N+1 problem for Lambda resolvers here: https://docs.aws.amazon.com/appsync/latest/devguide/tutorial-lambda-resolvers.html#advanced-use-case-batching

Can we have a solution for the N+1 problem with RDS resolvers? There are suggestions to flatten the query to workaround this, but I don't think flattening is always a good solution.

2) I think it would also be good if the requested fields for a GraphQL query were passed down to the RDS resolver's RequestMappingTemplate. This would prevent the SQL query from having to query all the columns.

Example:
{
getMyData {
column_name1
column_name2
column_name3
}
}

The SQL query in the RDS Resolver RequestMappingTemplate can do this:
select column_name1, column_name2, column_name3 from my_table

Currently, the SQL query has to do this: select * from my_table

Start with the linked AWS AppSync Lambda batching documentation and the RDS resolver RequestMappingTemplate behavior described in the issue. Define how RDS resolvers would batch nested requests and receive selected GraphQL fields; done would require an agreed design for both capabilities, since no repository files or tests are identified.

Written by the indexing model from the issue text.