geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dick Cavender (Jira)" <j...@apache.org>
Subject [jira] [Closed] (GEODE-6798) Refactoring client function execution logic
Date Thu, 26 Sep 2019 18:04:07 GMT

     [ https://issues.apache.org/jira/browse/GEODE-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dick Cavender closed GEODE-6798.
--------------------------------

> Refactoring client function execution logic
> -------------------------------------------
>
>                 Key: GEODE-6798
>                 URL: https://issues.apache.org/jira/browse/GEODE-6798
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server, functions
>            Reporter: Anilkumar Gingade
>            Assignee: Anilkumar Gingade
>            Priority: Major
>              Labels: GeodeCommons
>             Fix For: 1.10.0
>
>          Time Spent: 8h 20m
>  Remaining Estimate: 0h
>
> While working on GEODE-6677; issue with client function retry semantic, we came across
duplicating the fix on many places; as the function execution is supported in many ways:
> onServer(pool)
> onServers(pool)
> onRegion()
> onRegions()
> onServer(regionService)
> onServers(regionService)
> Additional methods when data affinity is provided.
> In all of these cases, the execution is done by having execute() and reExecute(); and
copies of it to support, execution using function object and function id, repeating the same
logic.
> The code can be refactored to remove the duplicating logic and make it easier to add
any changes/fixes.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message