[
https://issues.apache.org/jira/browse/TINKERPOP-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042288#comment-18042288
]
ASF GitHub Bot commented on TINKERPOP-3217:
-------------------------------------------
kenhuuu opened a new pull request, #3284:
URL: https://github.com/apache/tinkerpop/pull/3284
The added destroySessionPostGraphOp setting enables re-using the same
underlying connection for a different subsequent Session. This should increase
performance for cases where many short-lived Transactions are sent to the
server.
https://issues.apache.org/jira/browse/TINKERPOP-3217
<!--
Thanks for contributing! Reminders:
+ TARGET the earliest branch where you want the change
3.7-dev -> 3.7.6 (non-breaking only)
3.8-dev -> 3.8.1 (non-breaking only)
master -> 4.0.0
+ Committers will MERGE the PR forward to newer versions
+ ADD entry to the CHANGELOG.asciidoc for the targeted version
Do not reference a JIRA number there
+ ADD JIRA number to title and link in description
+ PRs requires 3 +1s from committers OR
1 +1 and 7 day wait to merge.
+ MORE details: https://s.apache.org/rtnal
-->
> Add mechanism to close session without closing connection on server
> -------------------------------------------------------------------
>
> Key: TINKERPOP-3217
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3217
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.8.0, 3.7.5
> Reporter: Ken Hu
> Priority: Major
>
> Currently, the Gremlin Server expects a closing of the underlying connection
> to signal that the corresponding Session tied to the connection should be
> closed. This is part of the [SessionOpProcessor
> reference|https://tinkerpop.apache.org/docs/current/dev/provider/#_session_opprocessor].
> An option should be added to the server so that alternative would be that
> the Session closes automatically if a successful commit or rollback occurs.
> This would only affect the Bytecode portion of the SessionOpProcessor that
> makes the Session act like a Transaction. This would allow connection re-use
> of connections for sessions and enable better performance for use cases that
> require large number of transactions to occur.
> This needs to be an option to prevent breaking changes in the server in 3.7.x
> and 3.8.x. In 4.x and later, this should probably be the default option.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
