Hi Max, This ticket doesn't assume any API changes, it's about broken functionality. I would start with checking what tests we have for @AffinityKeyMapped and creating missing one. From what I understand functionality is broken completely or almost completely, so I guess testing coverage is very weak there.
-Val On Wed, Jul 12, 2017 at 4:27 PM, Kozlov Maxim <dreamx....@gmail.com> wrote: > Igniters, > > jira: https://issues.apache.org/jira/browse/IGNITE-5037 < > https://issues.apache.org/jira/browse/IGNITE-5037> > How do you look to solve this ticket by adding two methods to the public > IgniteCompute API? > > @IgniteAsyncSupported > public void affinityRun(@NotNull Collection<String> cacheNames, > Collection<Object> keys, IgniteRunnable job) > throws IgniteException; > > @IgniteAsyncSupported > public <R> R affinityCall(@NotNull Collection<String> cacheNames, > Collection<Object> keys, IgniteCallable<R> job) > throws IgniteException; > > There is also a question of how to act when changing the topology during > the execution of the job. > 1) complete with an exception; > 2) stop execution and wait until the topology is rebuilt and continue > execution; > > I think the second way, do you think? > > -- > Best Regards, > Max K. > > > > >
