AWS neptune gremlin 3.4.x javascript/node.js valueMap() Not returning map

Question

>I upgraded a lambda (node.js 10.x) from gremlin 3.2.9 to 3.4.4 and
 `valueMap()`
 no longer returns data.  values() does as do most other >functions (though cap() with multiple columns does not).  The return often appears to have data, e.g.
 `JSON.stringify(data)`
 will show a >structure but no data --  the array is blank.  I have tried dozens of independent queries (none now work though they do in 3.2.9) as well as >those same queries from the command line (all work!).  Any help is greatly appreciated!

Accepted Answer

Hi,  
  
I've seen similar issues before related to GraphSON v3 not being returned from Lambda.  Starting in Gremlin 3.3.5, the default serialization format for Gremlin is now GraphSON v3.  Before that, it was GraphSON v2.  Do you mind trying to change your serialization format to v2 and seeing if that fixes the issue?  
  
More details in the StackOverflow post here:  https://stackoverflow.com/questions/54226192/issue-with-project-by-in-gremlin-js-3-4-0

Answer

Thanks!  This was exactly the solution!!  
  
altering the connection to fall back to GraphSON v2 was the charm

```
const dc = new DriverRemoteConnection(
  `ws://my-neptune-cluster.us-east-1.neptune.amazonaws.com:8182/gremlin`,
  *{ mimeType: "application/vnd.gremlin-v2.0+json" } // Fall back to GraphSON v2*
);
```

Really appreciate the help!  
  
Edited by: gcolclough on Dec 12, 2019 8:22 PM

AWS neptune gremlin 3.4.x javascript/node.js valueMap() Not returning map

Relevanter Inhalt