geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-1760) Custom ResultCollector on client does not receive partial results, but peer does
Date Thu, 18 Aug 2016 21:18:22 GMT


ASF subversion and git services commented on GEODE-1760:

Commit 6a91b9d08c35bf3c3b7cc38e4a4a0d5906e21dbb in incubator-geode's branch refs/heads/feature/GEODE-420
from [~upthewaterspout]
[;h=6a91b9d ]

GEODE-1760, GEODE-1762: Tests of function exceptions from clients

Extending FunctionServiceBase with tests that use a client server
topology. Added tests of onRegion with PRs as well as onServers.

Adding tests of P2P onRegion with multiple members and PRs.

Adding a temporary workaround for GEODE-1762 to let the function service
tests pass even if a Execution.execute throws an exception. This lets us
at least run the same tests against these different topologies even
though they are throwing different exceptions.

Added a test that result collectors receive partial results even after a

> Custom ResultCollector on client does not receive partial results, but peer does
> --------------------------------------------------------------------------------
>                 Key: GEODE-1760
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: functions
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>             Fix For: 1.0.0-incubating
> If a non HA function is executed from a client and one or more servers throw an exception,
a custom ResultCollector on the client does not receive any data for the members that did
succeed. For some use cases we it would be helpful if the client received results from the
members that were successful.
> The currently client behavior is also inconsistent with the way that functions work between
peers, because a ResultCollector in a peer will receive all of the results from the members
that did succeed, even if some members fail.

This message was sent by Atlassian JIRA

View raw message