[
https://issues.apache.org/jira/browse/GEODE-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492778#comment-17492778
]
ASF subversion and git services commented on GEODE-10018:
---------------------------------------------------------
Commit 8825d95ea64d154d4349e1e74f75bc34833a4702 in geode's branch
refs/heads/WIP-GEODE-9892 from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8825d95 ]
GEODE-10018: Remove redundant TX flag from SetOptions (#7352)
Authored-by: Donal Evans <doev...@vmware.com>
> Remove tx flag from Redis SetOptions
> ------------------------------------
>
> Key: GEODE-10018
> URL: https://issues.apache.org/jira/browse/GEODE-10018
> Project: Geode
> Issue Type: Improvement
> Components: redis
> Reporter: Jens Deppe
> Assignee: Donal Evans
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> A recent change ([https://github.com/apache/geode/pull/7321)] consolidated
> the logic for transactional operations, avoiding the need for individual data
> structs and commands to take different code paths to account for delta
> changes vs tx contexts.
>
> The MSET command still contains this older approach which can now be removed.
> Practically, we can remove the {{SetOptions.inTransaction}} field and all
> logic surrounding this flag.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
