Dmitriy,I don't believe it makes sense to have the action execute remotely. At
least I didn't think of it.In my mind, the action is always local (that's the
reason I suggested the Java's Callable in the API and not serializable
IgniteCallable, in the first place). What the action does is entirel
Yakov,
Any chance you can rerun the benchmarks to confirm your findings?
Would also be nice if someone else could run them as well. Is there a
branch that we can check out?
D.
On Fri, Jan 15, 2016 at 12:17 PM, Vladimir Ozerov
wrote:
> I also hardly believe that such change can give us such bi
Andrey,
In general this seems like a good addition. However, I do not understand
how you can specify an executor, given that execution could happen
remotely. Can you please clarify?
D.
On Fri, Jan 15, 2016 at 1:00 PM, Andrey Kornev
wrote:
> Hi there,
>
> The Semaphore feature was a great addit
Hi：
In the 1.5.0 version, I found that CacheTypeMetadata was abandoned and
replaced by QueryEntity.
I find that two classes of related instructions exist in the manual:
https://apacheignite.readme.io/docs/sql-queries
https://apacheignite.readme.io/docs/cache-queries
I suggest deleting the ins
Hi：
In a distributed environment, if use the spring AOP programming,
generated a class of byte code enhancement, then the error will be
reported as follows:
java.lang.ClassNotFoundException:
demo.computegrid.ComputeGridService$$EnhancerBySpringCGLIB$$7b44b192
This error I understand, this
