[
https://issues.apache.org/jira/browse/TINKERPOP-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060809#comment-15060809
]
stephen mallette commented on TINKERPOP-956:
--------------------------------------------
Lambda is good to go:
{code}
gremlin> :remote connect tinkerpop.server conf/remote-objects.yaml
==>Connected - localhost/127.0.0.1:8182
gremlin> :> g.addV()
==>v[0]
gremlin> :> g.V()
==>v[0]
gremlin> :> g.V().filter{it.get().id() == 0}
The provided traversal contains a lambda step: LambdaFilterStep(lambda)
Display stack trace? [yN] n
gremlin> :> g.V()
==>v[0]
{code}
> Connection errors tend to force a complete close of the channel
> ---------------------------------------------------------------
>
> Key: TINKERPOP-956
> URL: https://issues.apache.org/jira/browse/TINKERPOP-956
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver, server
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Minor
> Fix For: 3.1.1-incubating
>
>
> Would be nice if the channel could stay open if the error is recoverable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
