e the one we're discussing in this thread...
>>
>>
>> I guess I'm stuck with the Compute-based approach for now. :(
>>
>> Thanks!
>> Andrey
>>
>> --
>> *From:* Semyon Boikov
>> *Sent:* Tuesday, August 29,
Hi,
If EntryProcessor returns null then null is not added in the result map.
But I agree that using invokeAll() will have a lot of unnecessary overhead.
Perhaps we need add new getAll method on API, otherwise best alternative is
use custom ComputeJob or affinityCall.
Thanks,
Semyon
On Tue, Aug 2
It looks like known issue https://issues.apache.org/jira/browse/IGNITE-2714
On Tue, Sep 13, 2016 at 11:13 AM, kromulan wrote:
> I've had same problem in the past but it was a memory leak in indexing
> code.
> Do you use indexing on your entities ?
>
>
>
> --
> View this message in context: http:
Here is JIRA issue: https://issues.apache.org/jira/browse/IGNITE-3606
On Fri, Jul 29, 2016 at 5:48 PM, Semyon Boikov wrote:
> Hi,
>
> I reproduced this issue, thank you for test! After quick debugging It
> seems that this is some problem with Ignite backpressure mechanism in
> co
Hi,
I reproduced this issue, thank you for test! After quick debugging It seems
that this is some problem with Ignite backpressure mechanism in
communication SPI, I'll create JIRA issue with more details.
As a workaround could you try to disable backpressure:
tcpCommunicationSpi.setMessageQueueLi
We already have similar issue reproduced in our benchmarks -
https://issues.apache.org/jira/browse/IGNITE-3300. I think this is related
to optimziation done in 1.6 to store key partition in the cache key. I
believe fix will be included in 1.7 release.
On Tue, Jul 26, 2016 at 2:13 AM, Valentin Kuli
As far as I know the only reason sources of Nullable are in Ignite - we did
not want to have any dependecy for 'core' module.
On Mon, Jun 13, 2016 at 10:04 AM, Denis Magda wrote:
> Hi Pete,
>
> CC-ing Ignite dev list to the thread as well.
>
> Igniters, up to today is there any reason why we nee
Issue is IGNITE-1232 (https://issues.apache.org/jira/browse/IGNITE-1232).
On Tue, Feb 16, 2016 at 10:07 AM, ght230 wrote:
> I see.
>
> Is there any Ignite issues related to this problem.
>
> If so, can you provide the ignite issue number to me for tracking?
>
>
>
> --
> View this message in cont
