Hi there Amit. Geode does also work for PRs.... We actually look forward to the community contributing to the product... :)
But on a more serious note... a streaming results collector does require more thought and potentially significant (positive) changes to the system behavior. --Udo On Tue, Nov 28, 2017 at 11:21 AM, Amit Pandey <[email protected]> wrote: > Thanks Dan. > > A Streaming Result Collector in Geode is needed now . This will be great > addition. I know we can make it, but its pretty error prone to do it > > On Wed, Nov 29, 2017 at 12:05 AM, Dan Smith <[email protected]> wrote: > >> Hi Amit, >> >> Looking at the code, it looks like if your annotated method returns an >> array, or an Iteratable (like a List), and you have batchSize set, then >> spring will send your data in batches back to the caller of the function. >> Underneath the covers is it using geode's ResultSender and passing the >> batches to the ResultSender sendResult method. >> >> So it looks like this would reduce the amount of data that gets sent to >> the client in a single message. >> >> -Dan >> >> On Sun, Nov 26, 2017 at 9:11 PM, Amit Pandey <[email protected]> >> wrote: >> >>> Hi John and everyone, >>> >>> How does Spring Data Geode Function annotation batch size work? >>> >>> So if we set it up like @GemfireFunction(id="lotMapService",HA=true, >>> batchSize =1000) >>> >>> >>> what are the implications ? What happens if there is a million data to >>> be streamed on the server as well as on the client side. >>> >>> Regards >>> >> >> > -- Kindest Regards ----------------------------- *Udo Kohlmeyer* | *Pivotal* [email protected] <http://www.gopivotal.com/> www.pivotal.io
