Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <c531f3f8-5993-b16c-0a43-8218d0a95f4c@gridgain.com>
References: <8093e155-84fe-ba02-a55b-b40c6b9f40d3@gridgain.com>
 <CAGt6o8=gU+xPvt5LKC_cMAsswWR-oYi5Z0Y7OZh6XJ=pY=5Ekg@mail.gmail.com>
 <CAGcMBHggXjzFjj2K0A6qUnqj3Mmw5Pj-JzTdGduRm7xUK-cuSQ@mail.gmail.com>
 <CAFx+i-ZQnHD4xg+akMwQyk-VVaQfj3fmKv+Cz+eCix-a+VAJXQ@mail.gmail.com> <c531f3f8-5993-b16c-0a43-8218d0a95f4c@gridgain.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Thu, 7 Jul 2016 04:13:33 -0700
Message-ID: <CA+0=VoWwz3jJSjCZJZ7zhS1t3en7sBF87xBLK3v4P-KiwUuKyQ@mail.gmail.com>
Subject: Re: ignite-2310
To: Taras Ledkov <tledkov@gridgain.com>
Cc: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a1146dcb028e0bf053709c928
archived-at: Thu, 07 Jul 2016 11:14:15 -0000

--001a1146dcb028e0bf053709c928
Content-Type: text/plain; charset=UTF-8

Taras, it is very difficult to review API changes this way. Can you please
provide additional APIs in the ticket?

Also, we should add documentation about reserving partitions as well. To my
knowledge, this feature ensures that a partition will not be migrated while
affinityRun/Call is executed, right?

On Thu, Jul 7, 2016 at 3:02 AM, Taras Ledkov <tledkov@gridgain.com> wrote:

> Igniters,
>
> Please take a look at the next proposal of changes at
> IgniteCompute.affinityRun / affinityCall:
>
>
> https://github.com/gridgain/apache-ignite/commit/c57f009c44e07240fc8c8e6feed3271c63f31664#diff-b276b8e6e14915f9e5f2f5daeeddec8a
>
> So, two methods is added affinityRun and affinityCall. There is additional
> parameter Collection of extra caches names.
> An affinity job without the extra caches reserves only one partition (that
> contains affinity key) of the affinity cache.
> An affinity job with the extra caches parameter reserves the partitions
> (similar to affinity partition) of all extra caches.
>
>
> 06.07.2016 15:18, Semyon Boikov wrote:
>
>> I think we should detect such situation and throw exception. As I remember
>> for cross cache qieries we throw exception if caches have different
>> partitions distribution.
>>
>> On Wed, Jul 6, 2016 at 3:14 PM, Yakov Zhdanov <yzhdanov@apache.org>
>> wrote:
>>
>> Guys, this does not work in general case. If you provide more than one
>>> partition you can end up with a situation when they reside on more than
>>> one
>>> node.
>>>
>>> --Yakov
>>>
>>> 2016-07-06 13:50 GMT+03:00 Vladimir Ozerov <vozerov@gridgain.com>:
>>>
>>> If we add "partsToLock" to job execute request, then why we allow it only
>>>> for "affinity" methods? We can resort to "with" semantics instead:
>>>>
>>>> IgniteCompute.*withPartitionsToLock*(...).affinityRun();
>>>>
>>>> On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov <tledkov@gridgain.com>
>>>> wrote:
>>>>
>>>> Igniters,
>>>>>
>>>>> Lets discuss the changes of public API at the IgniteCompute.
>>>>> The new methods affinityRun & affinityCall is added by working on
>>>>> IGNITE-2310.
>>>>>
>>>>> https://issues.apache.org/jira/browse/IGNITE-2310
>>>>>
>>>>> Please take a look at the signature of the new methods:
>>>>>
>>>>>
>>>>>
>>>>>
>>> https://github.com/gridgain/apache-ignite/commit/991fb60f563ee1630152ca0159d04b4969f883bf#diff-b276b8e6e14915f9e5f2f5daeeddec8a
>>>
>>>> void affinityRun(@Nullable String cacheName, Object affKey,
>>>>>
>>>> IgniteRunnable
>>>>
>>>>> job, Map<String, int[]> partsToLock)
>>>>>
>>>>> The parameter Map<String, int[]> partsToLock is added.
>>>>> Map contains the pairs of the cache name and array of partitions that
>>>>>
>>>> must
>>>>
>>>>> be reserved on the target node before job execution.
>>>>>
>>>>> Dmitry, colleagues, please comment or approve.
>>>>>
>>>>> --
>>>>> Taras Ledkov
>>>>> Mail-To: tledkov@gridgain.com
>>>>>
>>>>>
>>>>>
> --
> Taras Ledkov
> Mail-To: tledkov@gridgain.com
>
>

--001a1146dcb028e0bf053709c928--