Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/1550
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feat
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/1550
IGNITE-2310: additional docs for affinity jobs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-2310
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/919
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featu
Guys,
Please review the last version of the public API
https://issues.apache.org/jira/browse/IGNITE-2310?focusedCommentId=15407375&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15407375
Ambiguity will be fixed on the client side. Tests has been fixed.
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/919
IGNITE-2310 Lock cache partition for affinityRun/affinityCall execution
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/910
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featu
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/910
Ignite 2310
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2310
Alternatively you can review and apply
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/857
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featu
t.
On Thu, Jul 7, 2016 at 5:44 AM, Taras Ledkov
wrote:
Igniters,
The issue https://issues.apache.org/jira/browse/IGNITE-2310 is updated
with comment
about the changes at the IgniteCompute. Please comment the ticket.
The changed javadoc of the affinityRun/Call is available to review at the
bran
comments.
>
>
> 09.07.2016 4:22, Dmitriy Setrakyan пишет:
>
> Thanks Taras, I have added my comments in the ticket.
>>
>> On Thu, Jul 7, 2016 at 5:44 AM, Taras Ledkov
>> wrote:
>>
>> Igniters,
>>>
>>> The issue https://issu
t.
On Thu, Jul 7, 2016 at 5:44 AM, Taras Ledkov wrote:
Igniters,
The issue https://issues.apache.org/jira/browse/IGNITE-2310 is updated
with comment
about the changes at the IgniteCompute. Please comment the ticket.
The changed javadoc of the affinityRun/Call is available to review at the
bra
Thanks Taras, I have added my comments in the ticket.
On Thu, Jul 7, 2016 at 5:44 AM, Taras Ledkov wrote:
> Igniters,
>
> The issue https://issues.apache.org/jira/browse/IGNITE-2310 is updated
> with comment
> about the changes at the IgniteCompute. Please comment the ticket.
Igniters,
The issue https://issues.apache.org/jira/browse/IGNITE-2310 is updated
with comment
about the changes at the IgniteCompute. Please comment the ticket.
The changed javadoc of the affinityRun/Call is available to review at
the branch
https://github.com/gridgain/apache-ignite/blob
gt;>>> for "affinity" methods? We can resort to "with" semantics instead:
>>>>
>>>> IgniteCompute.*withPartitionsToLock*(...).affinityRun();
>>>>
>>>> On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov
>>>> wrote:
>>
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/857
Ignite 2310 Lock cache partition for affinityRun/affinityCall execution
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
thods? We can resort to "with" semantics instead:
IgniteCompute.*withPartitionsToLock*(...).affinityRun();
On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov
wrote:
Igniters,
Lets discuss the changes of public API at the IgniteCompute.
The new methods affinityRun & affinityCall is added
k*(...).affinityRun();
On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov
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
s 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 a
nges 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 metho
,
>
> 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 me
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/ap
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/769
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featu
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/769
IGNITE-2310 Lock cache partition for affinityRun/affinityCall execution
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
Valentin Kulichenko created IGNITE-2310:
---
Summary: Add lock/unlock partition operations on IgniteCache
Key: IGNITE-2310
URL: https://issues.apache.org/jira/browse/IGNITE-2310
Project: Ignite
24 matches
Mail list logo
