You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Alberto Gomez (Jira)" <ji...@apache.org> on 2019/09/23 13:18:00 UTC
[jira] [Commented] (GEODE-7049) Add timeout parameter to Java
client Execution::execute() methods
[ https://issues.apache.org/jira/browse/GEODE-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935834#comment-16935834 ]
Alberto Gomez commented on GEODE-7049:
--------------------------------------
The final scope of this ticket has been defined here:
https://cwiki.apache.org/confluence/display/GEODE/Improvements+on+client+Function+execution+API
> Add timeout parameter to Java client Execution::execute() methods
> ------------------------------------------------------------------
>
> Key: GEODE-7049
> URL: https://issues.apache.org/jira/browse/GEODE-7049
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Alberto Gomez
> Assignee: Alberto Gomez
> Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> The Java client only allows to set a timeout to functions by means of a system property (gemfire.CLIENT_FUNCTION_TIMEOUT) while the C++ and C# native clients allow to pass a timeout parameter on a function execution basis.
> It will be good to have the same functionality on the Java client by means of having the following methods on the Execution interface:
>
> {code:java}
> ResultCollector<OUT, AGG> execute(Function function, int timeoutMs) throws FunctionException;
> ResultCollector<OUT, AGG> execute(String functionId, int timeoutMs) throws FunctionException;
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)