Send graphQL mutation based on DynamoDb stream with NodeJS

Question

I'm trying to update a GraphQL subscription when a DynamoDb table receives a new row. I got the following code working with only the RekognitionId, but I'm not trying to send the entire NewImage object, and I cannot make it work. I get all sorts of type problems, but with no real information to solve it with. The most telling was:

"Error: GraphQL error: Variable 'input' has an invalid value. Expected type 'Map' but was 'String'. Variables for input objects must be an instance of type 'Map'."

Unfortunately, I can't find a single reference to a GraphQL type called "map", so it's probably scrambled.

Does anyone have any experience of this? This is my Lambda function, like I said it worked with only RekognitionId formatted as a dynamoDb semi-json-string {"S": "id"}

global.WebSocket = require('ws');
require('es6-promise').polyfill();
require('isomorphic-fetch');
const AWS = require('aws-sdk');
const aws_exports = require('./aws-exports').default;
const AWSAppSyncClient = require('aws-appsync').default;

exports.handler = async (event, context, callback) => {
    if(!event.Records.length){
        console.log('no records');
        return false;
    }
    const AUTH_TYPE = require('aws-appsync/lib/link/auth-link').AUTH_TYPE;
    const url = aws_exports.ENDPOINT;
    const region = aws_exports.REGION;
    const type = AUTH_TYPE.AMAZON_COGNITO_USER_POOLS;

    AWS.config.update({
        region: aws_exports.REGION,
        credentials: new AWS.Credentials({
            accessKeyId: aws_exports.AWS_ACCESS_KEY_ID,
            secretAccessKey: aws_exports.AWS_SECRET_ACCESS_KEY
        })
    });
    const cognitoIdentityServiceProvider = new AWS.CognitoIdentityServiceProvider({ apiVersion: '2016-04-18' });

    const initiateAuth = async ({ clientId, username, password }) => cognitoIdentityServiceProvider.initiateAuth({
        AuthFlow: 'USER_PASSWORD_AUTH',
        ClientId: clientId,
        AuthParameters: {
            USERNAME: username,
            PASSWORD: password,
        },
    }).promise();
    const { AuthenticationResult } = await initiateAuth({
        clientId: '*******',
        username: '*******',
        password: '*******',
    });
    const accessToken = AuthenticationResult && AuthenticationResult.AccessToken;

    // Import gql helper and craft a GraphQL query
    const gql = require('graphql-tag');
    const query = gql(`
    mutation faceAdded($input: UpdateFaceInput!) {
        updateFace(input: $input) { 
            RekognitionId
            Emotions {
                Confidence
                Type
            }
            AgeRange
            Beard
            Mustache
            Gender
            Eyeglasses
        }
    }`);
    // Set up Apollo client
    const client = new AWSAppSyncClient({
        url: url,
        region: region,
        auth: {
            type: type,
            jwtToken: accessToken,
        },
        disableOffline: true      //Uncomment for AWS Lambda
    });
    return runMutationInClient(client, query, event.Records[0], (res) => {
        return res;
    });
}

const runMutationInClient = async (client, query, RekognitionObj, callback) => {
    await client.hydrated().then( async (client) => {
        console.log('Running mutation in Lambda: ', query, 'RekognitionId: ', RekognitionObj);

        var inputObj = AWS.DynamoDB.Converter.unmarshall(RekognitionObj.dynamodb.NewImage)

        await client.mutate({
            mutation: query,
            variables: {
                input: {
                    RekognitionId: {"S": inputObj.RekognitionId},
                    Emotion: {"L": []}
                }
            },
            fetchPolicy: 'no-cache'
        }).then(function logData(data) {
            console.log('LAMBDA results of query: ', data);
            callback(data);
        })
        .catch((error)=>{
            console.log('LAMBDA ERROR:', error);
            callback(error);
        });

    });
};

It looks more like VTL Template error. Are you sure the mutation works? Did you try to execute a mutation manually? — Shmygol
– Shmygol, Commented Mar 11, 2020 at 7:50
@Trilliput the error comes from the VTL template, but those were auto generated by AWS appsync and work from the appsync console. — Jesper Bylund
– Jesper Bylund, Commented Apr 29, 2021 at 6:13

David White · Accepted Answer · 2020-07-09 23:22:25Z

5

I have seen this error a lot (sadly!) and it is poorly worded as it bears no reference to mapping the way we might think. The error is that your graphql connection string is badly formed or it has a key piece of data missing.

There are two solutions. The first is to try out the graphql in a sandbox of some kind AWS Amplify and Apollo both have them in the console. In the case of AWS you can also mock your database and run it from your machine - although you need to create some data in your mocked environment - and clear it before you progress if you are developing on a local machine as the two sets of data - real and mock get intertwined! Yup, lost a few hours on that one!

The other solution is simply to console out the data string, whatever data you are relying on in the query to make sure the data is present. As occasionally it all looks good, but that error tends to occur when data is missing.

You can test the data. Get a good data string and then deliberately take the required! element out or another and you will at some point get the mapping error. This refers to the graphql not being able to map the data, rather than the javascript meaning of map.

answered Jul 9, 2020 at 23:22

David White

6641 gold badge11 silver badges24 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Jesper Bylund Over a year ago

This sounds like the solution, but could you provide some detail on what the malformed data looks like and what it should look like?

David White Over a year ago

the response I was working on at the time was as mentioned by the OP. I can't give more info as this was a long time ago.

Pete Duncanson · Accepted Answer · 2020-10-18 17:17:29Z

1

I had the same error this week and lots a lot of time. The cause for me was just checking what I was passing in as the variable to my GraphQL mutation. First of all I was passing in a number rather than an object (ie I was accidently passing the key while doing a for x in loop) and then secondly I was doing a JSON.stringify on the input variable for my mutation. Those together caused lots of head scratching. Adding it here just in case anyone else comes across this error. CHECK WHAT YOU ARE PASSING IN!

answered Oct 18, 2020 at 17:17

Pete Duncanson

3,2563 gold badges27 silver badges35 bronze badges

1 Comment

user2180794 Over a year ago

Stuck with the same issue .. lost right now.

Shmygol · Accepted Answer · 2021-05-01 10:57:21Z

0

It's a VTL template error. Hard to say without seeing the template, but "Map" and "String" are definitely the VTL types and looks like somewhere a string value is assigned to the input object, when it should have been a value of type map. Probably a json string were not converted to a map.

answered May 1, 2021 at 10:57

Shmygol

9537 silver badges16 bronze badges

Comments

thiago · Accepted Answer · 2021-06-28 18:44:59Z

0

I have had the exact same error in my implementation.

The cause for me was that my UpdateFaceInput did not have the same internal structure as my UpdateFace type.

So if anyone has this error come up, just wanted to hint that looking at you type updateFace and input updateFaceInput definitions might be also a good try.

answered Jun 28, 2021 at 18:44

thiago

231 silver badge5 bronze badges

Comments

Dharman · Accepted Answer · 2022-01-07 14:35:23Z

If you're trying to query or mutate based on conditions you need to use some condition clauses seen here. For example, your code should look something like this:

        await client.mutate({
            mutation: query,
            variables: {
                   input: {
                       RekognitionId: {eq: inputObj.RekognitionId},
                       Emotion: {eq: []}
                   }
            },
            fetchPolicy: 'no-cache'
        }).then(function logData(data) {
            console.log('LAMBDA results of query: ', data);
            callback(data);
        })
        .catch((error)=>{
            console.log('LAMBDA ERROR:', error);
            callback(error);
        });

The 'Map' error is kind of dumb in my opinion, it doesn't give you much to work with. This error may refer to other issues as well, but it seems that most of these issues are with the conditions.

Collectives™ on Stack Overflow

Send graphQL mutation based on DynamoDb stream with NodeJS

5 Answers 5

2 Comments

1 Comment

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

2 Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related