You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Cole Greer (Jira)" <ji...@apache.org> on 2025/10/30 17:20:00 UTC
[jira] [Closed] (TINKERPOP-2847) RequestId is case sensitive in JS GLV
[ https://issues.apache.org/jira/browse/TINKERPOP-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cole Greer closed TINKERPOP-2847.
---------------------------------
Assignee: Valentyn Kahamlyk
Resolution: Fixed
> RequestId is case sensitive in JS GLV
> -------------------------------------
>
> Key: TINKERPOP-2847
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2847
> Project: TinkerPop
> Issue Type: Improvement
> Components: javascript
> Affects Versions: 3.5.4
> Reporter: Cole Greer
> Assignee: Valentyn Kahamlyk
> Priority: Major
> Fix For: 3.5.5, 3.6.2
>
>
> There is a bug in the javascript GLV where overridden requestID's must be provided in lowercase form.
> For example:
> This code will run as expected:
> {code:java}
> client.submit("g.V()", null, {requestId: '6457272a-4018-4538-b9ae-08dd5ddc0aa1'}) {code}
> But this will never complete. The server replies with an all lower case UUID which the driver considers distinct from the upper case version. Therefore the driver acts as if no response is ever received.
> {code:java}
> client.submit("g.V()", null, {requestId: '6457272A-4018-4538-B9AE-08DD5DDC0AA1'}) {code}
> It appears the JS driver is matching UUID's by checking for exact string matches, where they should be matched as equal hex values. Exclusively using lower case request id's is a viable near-term workaround.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)