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

0

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!

已提問 4 年前檢視次數 486 次
2 個答案
0
已接受的答案

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

profile pictureAWS
已回答 4 年前
0

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

已回答 4 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南