flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fabian Hueske <fhue...@gmail.com>
Subject Re: [DISCUSS] Hold copies in HeapStateBackend
Date Wed, 23 Nov 2016 16:14:58 GMT
Hi Greg,

yes we could and as Aljoscha pointed out the proper solution would be to
serialize all objects (as done in the DataSet API) and not hold them as
objects on the heap.
This would be a major effort though and I am rather looking for a 'quick'
work around that does not have major side effects.

2016-11-23 17:07 GMT+01:00 Greg Hogan <code@greghogan.com>:

> On Wed, Nov 23, 2016 at 8:34 AM, Fabian Hueske <fhueske@gmail.com> wrote:
>
> > The ReduceFunction must be used in the right way and it is easy to get
> > wrong.
> >
>
> I'm likely highlighting my ignorance here, but if object reuse works
> properly for ReduceFunction in the batch API, can we do the same in the
> streaming API?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message