You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/13 12:50:00 UTC
[jira] [Commented] (TINKERPOP-1913) Expose metadata from Gremlin
Server to Clients
[ https://issues.apache.org/jira/browse/TINKERPOP-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648924#comment-16648924 ]
ASF GitHub Bot commented on TINKERPOP-1913:
-------------------------------------------
tec-goblin commented on issue #933: TINKERPOP-1913 Make status attributes available
URL: https://github.com/apache/tinkerpop/pull/933#issuecomment-429539267
This is a great step. Now that #922 - TINKERPOP-1959 has been closed, when would we expect to see ResultSets containing the necessary attributes in gremlin-javascript? That's super interesting for [surfacing performance stats to the various clients](https://github.com/Microsoft/vscode-cosmosdb/issues/814) :).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Expose metadata from Gremlin Server to Clients
> ----------------------------------------------
>
> Key: TINKERPOP-1913
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1913
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet, driver, python, server
> Affects Versions: 3.3.1
> Reporter: Ashwini Singh
> Assignee: stephen mallette
> Priority: Major
> Fix For: 3.4.0
>
>
> To summarize what we have discussed so far:
> 1. For API using GremlinRequest/QueryScript, expose response attribute as part of result. Using an approach to similar to Java client driver (using ResultSet) . [Priority0]
> -- We rely on the last message for response attributes.
> 2. For GLV, add response attribute as part of Traversal. [Priority 0]
> --Rely on the last message for attributes.
> 3. Expose other server details (like server setting). I would suggest to split this design discussion into two directions:
> a. Metadata for request execution: Only focuses on details related to request execution. Can be achieved through #1 and #2.
> b. Metadata for Gremlin Server: Focuses on overall metadata for the server. Could be a separate request and fetch the data once for a connection.
> Targeted drivers: dotnet, Java, python, javascript.
> More details: [https://lists.apache.org/thread.html/fd2208a2db827bc1eb479ad8c2f181bd2fa532553c97b3fe6994a7b6@%3Cdev.tinkerpop.apache.org%3E]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)