Re: Add isPrimary() and isBackup() methods on CacheQueryEntryEvent

Igniters, What do you think about the new API? > 3 авг. 2017 г., в 15:56, Kozlov Maxim <dreamx@gmail.com> написал(а): > > Guys, > > I'm sorry for the misunderstanding, I was tired at the end of the day :-) > In the process of working on the task, I had to add

Re: Add isPrimary() and isBackup() methods on CacheQueryEntryEvent

Folks, > > As far as I see, Issue still in PatchAvailable state, what did you mean by > "solved"? > > On Wed, Aug 2, 2017 at 8:01 PM, Kozlov Maxim <dreamx@gmail.com> wrote: > >> Sure. >> >> CacheQueryEntryEvent: >> >> public abst

Re: Add isPrimary() and isBackup() methods on CacheQueryEntryEvent

> added to interface? > > On Wed, Aug 2, 2017 at 7:53 PM, Kozlov Maxim <dreamx@gmail.com> wrote: > >> Igniters, >> >> When you solved the 3878[1] ticket, two methods were added[2]: isPrimary() >> and isBackup() on the CacheQueryEntryEvent in a p

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 > 25 июля 2017 г., в 10:53, Николай Ижиков написал(а): > > +1 > > 2017-07-25 10:50 GMT+03:00 Vyacheslav Daradur : > >> +1 >> >> 2017-07-25 2:02 GMT+03:00 Valentin Kulichenko < >> valentin.kuliche...@gmail.com >>> : >> >>> +1 (binding) >>> >>>

Re: Changing public IgniteCompute API to improve changes in 5037 ticket

Max, > > This ticket doesn't assume any API changes, it's about broken > functionality. I would start with checking what tests we have > for @AffinityKeyMapped and creating missing one. From what I understand > functionality is broken completely or almost completely, so I guess testin

Re: [VOTE] Apache Ignite 2.1.0 RC3

+1 > 21 июля 2017 г., в 7:48, Valentin Kulichenko > написал(а): > > +1 (binding) > > On Thu, Jul 20, 2017 at 9:35 PM, Sasha Belyak wrote: > >> +1 >> >> 2017-07-21 5:34 GMT+07:00 Denis Magda : >> >>> Igniters, >>> >>>

Re: [VOTE] Apache Ignite 2.1.0 RC2

; >>> Hi guys. >>> I've downloaded apache-ignite-2.1.0-src.zip, unpack it and execute "mvn >>> package -DskipTests" >>> result is succes, but the folder "target" in the root directory is empty. >>> I've checked it at two diffrenet machines.

Re: [VOTE] Apache Ignite 2.1.0 RC2

+1 > 19 июля 2017 г., в 11:33, Semyon Boikov написал(а): > > +1 (binding) > > On Tue, Jul 18, 2017 at 9:45 PM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > >> +1 (binding) >> >> On Tue, Jul 18, 2017 at 11:40 AM, Denis Magda wrote:

Changing public IgniteCompute API to improve changes in 5037 ticket

Igniters, jira: https://issues.apache.org/jira/browse/IGNITE-5037 How do you look to solve this ticket by adding two methods to the public IgniteCompute API? @IgniteAsyncSupported public void affinityRun(@NotNull Collection cacheNames,

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

+1 > 13 июня 2017 г., в 14:14, Vyacheslav Daradur написал(а): > > +1 (I will attend) > > 2017-06-13 6:35 GMT+03:00 Roman Shtykh : > >> Denis, >> Can you please share slides (or video) after the webinar? I would like to >> attend it but it's

IGNITE-532 ready for review

Hi guys! Review please - https://github.com/apache/ignite/pull/1998 https://issues.apache.org/jira/browse/IGNITE-532 I'm add Akka Stream and Akka Actor integration, please see the solution. There

Re: IGNITE-2558 PR is ready to review (NearCacheConfiguration should not extend MutableConfiguration)

Create ticket https://issues.apache.org/jira/browse/IGNITE-4910 <https://issues.apache.org/jira/browse/IGNITE-4910> and fix PR. > 4 апр. 2017 г., в 17:06, Kozlov Maxim <dreamx@gmail.com> написал(а): > > Valentin, of course. I'll let you know how I'll do it. > &g

Re: IGNITE-2558 PR is ready to review (NearCacheConfiguration should not extend MutableConfiguration)

will be ignored. Basically, it's a new > feature and I'm OK if we do this as a separate task sometime later (e.g. in > 2.1). Can you create a ticket and remove the property for now? > > -Val > > On Tue, Apr 4, 2017 at 3:04 AM, Kozlov Maxim <dreamx@gmail.com> wrote: >

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

+ Denis > 30 марта 2017 г., в 12:14, Kozlov Maxim <dreamx@gmail.com> написал(а): > > Denis, > > CacheAtomicWriteOrderMode enum already removed. > >> 30 марта 2017 г., в 7:38, Denis Magda <dma...@apache.org> написал(а): >> >> Maxim

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

to keep it for the only one option left - PRIMARY. > > Any objections? > > — > Denis > >> On Feb 27, 2017, at 8:09 AM, Kozlov Maxim <dreamx@gmail.com> wrote: >> >> Hi Igniters, >> >> After remove CLOCK mode, CacheAtomicWriteOrderMode

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

AM, Alexey Kuznetsov <akuznet...@apache.org> >> wrote: >> >>> Maxim, >>> >>> Could you merge master to your PR? >>> I failed to review Web Console files due to conflicts. >>> >>> Thanks. >>> >>> On Fri, Mar 10, 20

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

> 13 марта 2017 г., в 19:44, Denis Magda <dma...@apache.org> написал(а): > > Weird, can you edit any other page? I can’t find any configuration parameters > that should prevent you from editing. > > — > Denis > >> On Mar 13, 2017, at 9:14 AM, Kozlo

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Denis, I can not edit this page. confluence username: dreamx > 13 марта 2017 г., в 19:01, Kozlov Maxim <dreamx@gmail.com> написал(а): > > Denis, > > ok > >> 13 марта 2017 г., в 18:59, Denis Magda <dma...@apache.org >> <mailto:dma...@apache.org

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

che.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide> > > You need to say that the parameter has been discontinued and the users can > use CacheAtomicWriteOrderMode.PRIMARY instead. > > Agreed? > > — > Denis > >> On Mar 10, 2017, at 12:06 AM, Koz

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Andrey, or better remove GridTimeSyncProcessorSelfTest class? > 7 марта 2017 г., в 12:21, Kozlov Maxim <dreamx@gmail.com> написал(а): > > Andrey, in GridTimeSyncProcessorSelfTest class methods: testTimeSync() and > testTimeSyncChangeCoordinator() also removed? > >

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

return new IgniteUuid(new UUID(nodeOrderDrId, topVer), order); >>> } >>> >>> >>> Serialization/deserialization of GridCacheVersion.globalTime field >>> should be removed. >>> >>> On Fri, Mar 3, 2017 at

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

entation will be good enough: > > public IgniteUuid asGridUuid() { >return new IgniteUuid(new UUID(nodeOrderDrId, topVer), order); > } > > > Serialization/deserialization of GridCacheVersion.globalTime field > should be removed. > > On Fri, Mar 3, 2017 at

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

igh and low >> parts of the embedded UUID. >> >> --AG >> >> 2017-03-02 12:39 GMT+03:00 Kozlov Maxim <dreamx@gmail.com>: >> >>> Andrey, >>> >>> When removed parameter globalTime, in method: >>> >>> public

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Andrey, When removed parameter globalTime, in method: public IgniteUuid asGridUuid() { return new IgniteUuid(new UUID(((long)topVer << 32) | nodeOrderDrId, globalTime), order); } globalTime parameter replaced by something or remove this method? > 2 марта 2017 г., в 12:07, Koz

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Andrey, Please review PR again. > 1 марта 2017 г., в 18:47, Andrey Gura <ag...@apache.org> написал(а): > > I think that it is ok. > > On Wed, Mar 1, 2017 at 6:34 PM, Kozlov Maxim <dreamx@gmail.com> wrote: >> Ok. What do you say for the rest? >> &g

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

the CLOCK mode, I think we should remove the enum too, as > well as configuration properties and other code using this enum. Having > enum with one value doesn't make sense to me. > > -Val > > On Mon, Feb 27, 2017 at 5:09 AM, Kozlov Maxim <dreamx@gmail.com> wrote: &

Remove CacheAtomicWriteOrderMode.CLOCK mode.

Hi Igniters, After remove CLOCK mode, CacheAtomicWriteOrderMode enum contains now only one value PRIMARY. Andrey Gura, proposition remove CacheAtomicWriteOrderMode enum. Will there be something special for this purpose is enum? jira: https://issues.apache.org/jira/browse/IGNITE-4587

Implement IgniteZeromqStreamer to stream data from ZeroMQ

Hello Igniters, Please review and comment implementation ZeroMQ streamer. PR: https://github.com/apache/ignite/pull/1532 Jira: https://issues.apache.org/jira/browse/IGNITE-533 -- Best Regards, Max