Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.incubator.apache.org
Date: Thu, 18 Aug 2016 21:18:22 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: issues@geode.incubator.apache.org
Message-ID: <JIRA.12996997.1471021202000.349019.1471555102097@Atlassian.JIRA>
In-Reply-To: <JIRA.12996997.1471021202000@Atlassian.JIRA>
References: <JIRA.12996997.1471021202000@Atlassian.JIRA> <JIRA.12996997.1471021202087@arcas>
Subject: [jira] [Commented] (GEODE-1760) Custom ResultCollector on client
 does not receive partial results, but peer does
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 18 Aug 2016 21:18:28 -0000


    [ https://issues.apache.org/jira/browse/GEODE-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427165#comment-15427165 ] 

ASF subversion and git services commented on GEODE-1760:
--------------------------------------------------------

Commit dbf41d1facddb2e0f69657b3e0e1e82161f7fa33 in incubator-geode's branch refs/heads/feature/GEODE-420 from [~suranjan]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=dbf41d1 ]

GEODE-1760 Sending partial results to users ResultCollector

For non-HA functions on the client, results will now be passed to the
users result collector, even if some nodes fail due to a bucket movement
or cache close.

Signed-off-by: Dan Smith <upthewaterspout@apache.org>


> Custom ResultCollector on client does not receive partial results, but peer does
> --------------------------------------------------------------------------------
>
>                 Key: GEODE-1760
>                 URL: https://issues.apache.org/jira/browse/GEODE-1760
>             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
(v6.3.4#6332)