Hi,
I opened this:
https://issues.apache.org/jira/browse/FLINK-4992
With this users can implement practically anything depending how they use
the parameter so changing the state access logic is not necessary.
Cheers,
Gyula
Aljoscha Krettek ezt írta (időpont: 2016. nov. 1., K,
16:39):
> Hi,
> y
Hi,
yes, I think exposing a simple form of namespaces as String would be good.
By the way, do we also need access to state with namespaces then?
@Gyula: Please go ahead and open the Jira issue.
Cheers,
Aljoscha
On Sat, 29 Oct 2016 at 17:28 Gyula Fóra wrote:
> Thanks for the feedback guys,
>
>
Thanks for the feedback guys,
I think exposing the namespace in a simplified form in the user facing API
is I think a very good idea, that already let's the users implement
practically anything they want. Maybe doing it as a simple string as Jamie
suggested would be a nice way to do it and that wo
Hi guys,
Good points, Gyula. I think it would be much easier on a user if there
could be multiple timers in flight per key. I prefer the second approach,
though, where a user associates some bit of metadata with the timer and we
pass it back to them in the onTimer() callback, otherwise they are
Hi Gyula,
if you look at the internal API you'll notice that it is pretty much like
your second proposal. Just for reference, the interface is roughly this:
public interface InternalTimerService {
long currentProcessingTime();
long currentWatermark();
void registerProcessingTimeTimer(N names
Hello,
I was thinking about the methods provided by the timely functions and the
timerservice and I am wondering if it makes sense to change them a little
so they can cover a wider set of use case. Maybe I missed something
completely obvious so please shoot me down in that case :)
Currently the u
