[
https://issues.apache.org/jira/browse/TINKERPOP-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474627#comment-16474627
]
ASF GitHub Bot commented on TINKERPOP-1913:
-------------------------------------------
GitHub user ashwini-ms opened a pull request:
https://github.com/apache/tinkerpop/pull/868
Tinkerpop 1913
Adding support to de-serialize status attribute for gremlin dotnet. more
details
https://issues.apache.org/jira/browse/TINKERPOP-1913
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashwini-ms/tinkerpop TINKERPOP-1913
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/868.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #868
----
commit 3966453a0adefd5eeb0ff6fe6b150e335c2b1991
Author: Ashwini Singh <ashwini.mnnit@...>
Date: 2018-05-14T18:42:54Z
status attribute for gremlin dotnet
commit 27f71afbc8bd82a577fac7deaf7508dcc910e4ff
Author: Ashwini Singh <ashwini.mnnit@...>
Date: 2018-05-14T18:48:29Z
Adding comment
----
> 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, javascript, python, server
> Affects Versions: 3.3.1
> Reporter: Ashwini Singh
> Assignee: stephen mallette
> Priority: Major
>
> 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)
