Romain, I am not sure what you mean by not having access to TCK. Are you
talking about validating compatibility with JCAche using the TCK [1]? In
this case, Apache Ignite does pass the TCK. Moreover, the TCK seems to be
licensed under Apache 2.0 [2]. Can you please explain?
[1]
Alpha cause asf doesnt have oracle tck so we cant validate binary compat
but it targets jcache 1.0. More a legal thing than anything else. If you
have access to tck and can validate the binaries we can move on 1.0
Le 27 mars 2016 00:21, "Dmitriy Setrakyan" a écrit :
> Hi
Yakov, I've seen your comments, can you please check the jira again?
On Wed, Mar 23, 2016 at 4:46 PM, Yakov Zhdanov wrote:
> Vlad, can you please check my comments again?
>
> --Yakov
>
> 2016-03-18 17:57 GMT+03:00 Vladisav Jelisavcic :
>
> > Hi Yakov,
Dmitriy,
Honestly I was thinking only of window processing to cover only this specific
area. But I think looking at reactive streams makes sense and window processing
can be implemented within reactive streams with all three delivery guarantee
semantics (starting with the easiest two).
Also I