[
https://issues.apache.org/jira/browse/TINKERPOP-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676403#comment-17676403
]
ASF GitHub Bot commented on TINKERPOP-2847:
-------------------------------------------
kenhuuu opened a new pull request, #1940:
URL: https://github.com/apache/tinkerpop/pull/1940
Fixes https://issues.apache.org/jira/browse/TINKERPOP-2847.
Storing and comparing the request IDs in lower case prevents issues that
arise when the supplied ID and returned ID are using different cases to
represent the hex values of the UUID.
> 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.5
> Reporter: Cole Greer
> Priority: Major
>
> 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)
