[
https://issues.apache.org/jira/browse/TINKERPOP-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476429#comment-16476429
]
ASF GitHub Bot commented on TINKERPOP-1913:
-------------------------------------------
Github user ashwini-ms commented on the issue:
https://github.com/apache/tinkerpop/pull/868
Thanks a lot !!
From: stephen mallette <[email protected]>
Sent: Tuesday, May 15, 2018 12:42 PM
To: apache/tinkerpop <[email protected]>
Cc: Ashwini Singh <[email protected]>; Author
<[email protected]>
Subject: Re: [apache/tinkerpop] Tinkerpop 1913 (#868)
btw, we really need to rebase the TINKERPOP-1913 branch so that it can get
up to the 3.3.4-SNAPSHOT. I'll handle that on merge.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Ftinkerpop%2Fpull%2F868%23issuecomment-389289005&data=02%7C01%7Cashwsing%40microsoft.com%7C215c07a591dc4ec4b2a308d5ba9bdc5d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636620100936047968&sdata=9AtUzRdMkWARvsQJArpGgBI9z07zX37bgpS8WsArvPY%3D&reserved=0>,
or mute the
thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAdcfcxYUYbtpjiyjP07kNPG1Rz2Ij4yEks5tyy9rgaJpZM4T-UoQ&data=02%7C01%7Cashwsing%40microsoft.com%7C215c07a591dc4ec4b2a308d5ba9bdc5d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636620100936057972&sdata=jEgePoKFni3ZVdu%2BFlIx6pw2EN0MvP5rAgAl9hHhh40%3D&reserved=0>.
> 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)
