Hello Flavio,
thank you for looking into the matter.
The 2nd Sequence given to RowTypeInfo has only informational value AFAICS.
It does not prevent the issue from happening, I'm afraid.
Martin
P.S.: The behavior is now reported as 'FLINK-4108'.
On Tue, Jun 21, 2016 at 12:16 PM Flavio Pomperma
Hi,
I am trying to use a ListState in a RichCoFlatMapFunction but when
calling: getRuntimeContext().getListState(descriptor) in the open-function
i am getting a "State key serializer has not .." exception. I am not sure
what i can do to avoid this exception - Are any of you able to provide some
he
Several new questions:
- Stoppable job
I read threads mentioning that a streaming job can be stopped [1][2].
However looks like it can only be called through command line. Is it
possible to programmatically stop the streaming job from within the
job itself? For instance, a Kafka consumer streaming
Thanks, this is exactly what I was looking for.
Cheers,
Omar.
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/TaskManager-information-during-runtime-tp7655p7665.html
Sent from the Apache Flink User Mailing List archive. mailing list archive
Thanks for clarifying that helps me identify the root cause. The
problem comes from my code which is not related to Flink. Now the
problem is solved. Thank you again for the advice!
On 16 June 2016 at 23:49, Till Rohrmann wrote:
> Hi Yan Chou Chen,
>
> Flink does not instantiate for each record a
Hi,
Chiwan is correct. The reason why we're (not yet) using managed memory in
the streaming API (DataStream) is that it was easier to get things up and
running by just using JVM heap. We're hoping to change this at some point
in the future, though.
Cheers,
Aljoscha
On Wed, 22 Jun 2016 at 14:05 Ch
Hi,
you can implement a RichSourceFunction. With this you can also implement
open() and close() methods that get called when your source is started on
the worker node and closed respectively. In there, you could determine the
hostname and send it to some centralized service so that it knows the
hos
Hi,
I’m not sure about the reason to use JVM heap instead of managed memory, but It
seems that the reason is using JVM heap makes development easier. Maybe Stephan
can give exact answer to you. I think managed memory still has benefit in terms
of GC time and memory utilization.
The Flink comm
Thank you for your answer to my question, Chiwan :)
Can I ask another question?
> On Jun 22, 2016, at 7:22 PM, Chiwan Park wrote:
>
> Hi Tae-Geon,
>
> AFAIK, spilling *data* to disk happens only when managed memory is used.
> Currently, streaming API (DataStream) doesn’t use managed memor
Hi Tae-Geon,
AFAIK, spilling *data* to disk happens only when managed memory is used.
Currently, streaming API (DataStream) doesn’t use managed memory yet.
`MutableHashTable` is one of representative usage of managed memory with disk
spilling. Note that some special structures such as `Compacti
10 matches
Mail list logo