The idea is great!
Also I would suggest an ability to run new (modified) tests 100 times in
loop on the CI server to make sure that they don't cause no sporadic
failures (we can include that as part of the requirements before review)
On Sat, Aug 26, 2017 at 6:16 PM, Dmitriy Setrakyan
Andrey,
Good to hear from you. Long time no talk.
I don't think invokeAll has only update semantics. You can definitely use
it just to look at the keys and return a result. Also, as you mentioned,
Ignite compute is a viable option as well.
The reason that predicates were removed from the get
Love the idea. Let's add Testing Ignite Apps page on Readme. Denis, I don't
think we need many snippets, just a few.
As far as Maven archetype, Yakov, is the only purpose of it to load a
project, so users can add tests to it?
D.
On Fri, Aug 25, 2017 at 8:51 AM, Denis Magda
Hi Alexey,
Sorry for delayed response.
For point 1, the reason i need is when a service fetches & returns pojos,
if the key is not a member of the pojo (in our case the keys are java
int/long type) how else will the client who consumes the pojos know their
id/keys.
On point 2, I will try as you
Hi Slava,
Yes but in that case, at least the default jvm options should definitely
work.
-Xms128m -Xmx128m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=D:\GC
-XX:OnOutOfMemoryError="kill -9 %p"
The process is not getting killed and neither the heap dump is getting
created. I have attached a
Hi Vasiliy,
Thanks for responding. I had figured that issue a few days back & have
already deployed ignite (not released in prod yet). I am sorry i should
have updated the team here. Sorry about that & thanks for helping.
I did find one other issue w.r.t to writing/reading to PostgreSQL json
Hi,
Consider the following situation
Machine M1-> Data Grid Server S1
Machine M2-> Data Grid Server S2
Machine M3-> Data Grid Server S3
I intend to use REPLICATED mode because data loss is something which my
application can't take.
QUESTIONS
QUESTION 1:
Is there a way, we can identify which