[
https://issues.apache.org/jira/browse/TINKERPOP-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwini Singh updated TINKERPOP-1913:
-------------------------------------
Description:
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.
More details:
[https://lists.apache.org/thread.html/fd2208a2db827bc1eb479ad8c2f181bd2fa532553c97b3fe6994a7b6@%3Cdev.tinkerpop.apache.org%3E]
was:
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.
> Expose metadata from Gremlin Server to Clients
> ----------------------------------------------
>
> Key: TINKERPOP-1913
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1913
> Project: TinkerPop
> Issue Type: Improvement
> Reporter: Ashwini Singh
> 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.
>
> 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)
