FWIW, I really like this suggestion. There is some interaction with the `isHA()` behavior but I would love to have a reactive Function that returns a mono / flux [1].
Anthony [1] https://spring.io/blog/2016/04/19/understanding-reactive-types <https://spring.io/blog/2016/04/19/understanding-reactive-types> > On Nov 28, 2017, at 10:23 PM, Amit Pandey <[email protected]> wrote: > > Hey Guys, > > I filed this JIRA ticket :- https://issues.apache.org/jira/browse/GEODE-4027 > <https://issues.apache.org/jira/browse/GEODE-4027> > > Regards > > On Wed, Nov 29, 2017 at 2:01 AM, Amit Pandey <[email protected] > <mailto:[email protected]>> wrote: > Sure. > > On Wed, Nov 29, 2017 at 1:43 AM, Swapnil Bawaskar <[email protected] > <mailto:[email protected]>> wrote: > Amit, > Can you please file a JIRA? > > Thanks! > > On Tue, Nov 28, 2017 at 12:02 PM Amit Pandey <[email protected] > <mailto:[email protected]>> wrote: > Hey Udo, > > if I was confident I wouldn't have griped about the non availability. I think > though that it will be a good addition. Because for large data collections > it's not enough to batch it from the server side. > > Without a streaming result collector its futile > > On Wed, Nov 29, 2017 at 1:05 AM, Udo Kohlmeyer <[email protected] > <mailto:[email protected]>> wrote: > 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] > <mailto:[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] > <mailto:[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] > <mailto:[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] <mailto:[email protected]> > <http://www.gopivotal.com/> > www.pivotal.io <http://www.pivotal.io/> > > >
