[
https://issues.apache.org/jira/browse/TINKERPOP-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1195.
---------------------------------------
Resolution: Won't Do
Don't think I will change this now - the preferred method for sending requests
now is over bytecode so this API will become less and less exposed as time goes
on. I don't think there's much point to changing it now.
> Client and ResultSet API changes
> --------------------------------
>
> Key: TINKERPOP-1195
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1195
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver
> Affects Versions: 3.1.1-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Major
> Labels: breaking
>
> Given discussion on a couple different threads:
> https://lists.apache.org/thread.html/Z424dvlo67k5np4
> https://lists.apache.org/thread.html/Z70ku3nckrkkgiy
> the idea to introduce a breaking change to the {{Client}} and {{Result}} API
> seems to be established. The basic changes involve:
> 1. Remove the return of {{CompletableFuture}} from a {{ResultSet}} thus
> allowing it to block for the {{some()}} and {{all()}} methods.
> 2. Change {{Client.submit()}} to return {{List<Result>}} rather than return a
> {{ResultSet}} - that method will basically block until all results are
> returned and then unwrap the {{List<Result>}} and return that.
> Unfortunately, there doesn't appear to be a way to make it so that these
> changes are non-breaking.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
