Re: IEP-4, Phase 2. Using BL(A)T for in-memory caches.

BLAT sounds good to me because it slightly funny in case you speak russian. "Node joined topology by BLAT (po blaty)" sounds reasonable :) чт, 24 мая 2018 г. в 1:15, Dmitriy Setrakyan : > Ed, > > Anyone speaking Russian would agree that BLAT is not a good name :) Let's >

Re: Upgrading Ignite to JCache 1.1

Corrected IEP URL: https://cwiki.apache.org/confluence/display/IGNITE/IEP-21%3A+JCache+1.1+support чт, 14 июн. 2018 г. в 12:48, Александр Меньшиков : > Igniters, > > I've prepared IEP-21 [1] for this JCache updating task. > It will help us to manage the issues and see the progress in one place.

Re: IGNITE-640: multimap initial implementation

che/ignite/pull/4207 > > Thanks, > Amir > > > On Wed, Jun 13, 2018 at 8:38 AM Anton Vinogradov wrote: > > > Amir, > > > > Thanks for attempt. > > As far as I can see you have all changes at this commit: > > > > > https://github.com/apache/ig

Re: IGNITE-640: multimap initial implementation

Amir, Thanks for attempt. As far as I can see you have all changes at this commit: https://github.com/apache/ignite/pull/3926/commits/cd0e50e05d3860788378ebf1a29dc0525460872a You can simply apply it to local branch based on master by patch

Re: IGNITE-4188, savepoints with atomic cache?

Vote for #2 since it can shed light on hidden bug at production. ср, 13 июн. 2018 г. в 18:10, Alexey Goncharuk : > Igniters, > > Bumping up this discussion. The fix has been implemented and it is fine > from the technical point of view, but since the fix did not make it to the > Ignite 2.0, the

Re: Ability to check and completely fill transactions on creation

, etc, etc. That is why we either should use the > existing event subsystem or come up with a holistic design that will work > across the whole project. > > D. > > On Thu, May 24, 2018 at 1:38 AM, Anton Vinogradov wrote: > > > Dmitriy, > > > > Yakov is ag

Re: Ability to check and completely fill transactions on creation

suggest that you create TransactionStateChangeEvent, which > would have previous and new transaction state and would cover all state > changes, not just the start of the transaction. This will make the design > consistent and thorough. > > D. > > On Tue, May 29, 2018 at 5:39 AM, Anton Vinogra

Re: OptimizedObjectInputStream#available() doesn't work as expected?

Folks, I checked and it's possible to use available() directly from stream encapsulated at GridDataInput, but I'm not sure it's a good idea to update almost obsolete classes. Catching EOFException hack looks as reasonable solution in current case. Thoughts? чт, 31 мая 2018 г. в 11:39, Pavel

Re: Ability to check and completely fill transactions on creation

vent to > EVT_TX_NEAR_STARTED/PREPARED/COMMITTED/etc/etc? In this case the "label()" > method will always provide required data, right? > > D. > > On Fri, Jun 1, 2018 at 7:19 AM, Anton Vinogradov wrote: > > > Dmitriy, > > > > 1) EVT_TX_PREPARED w

Re: Ability to check and completely fill transactions on creation

, EVT_CACHE_OBJECT_EXPIRED }; чт, 31 мая 2018 г. в 20:48, Dmitriy Setrakyan : > Anton, > > Why not just have one transaction event: EVT_TX_STATE_CHANGED? > > D. > > On Thu, May 31, 2018 at 9:10 AM, Anton Vinogradov wrote: > > > Dmitriy, > > > > Thanks for

Re: Ability to check and completely fill transactions on creation

ethod. Why >is the label not propagated to remote nodes? What happens when users > call >this "label()" method for other TX events, not the EVT_TX_STARTED event? > > D. > > On Fri, Jun 1, 2018 at 6:20 AM, Anton Vinogradov wrote: > > > Dmitriy, > > &

Re: IgniteSet implementation: changes required

+1 to removal in case there is no easy, fast and consistent way to restore setDataMap on node restart. I see that we'll gain some performance drop on size() or keys(), but these methods are rarely used. пн, 25 июн. 2018 г. в 16:07, Pavel Pereslegin : > Hello, Igniters. > > I tried to implement

Re: Ignite contibutors page

tribution > of code (it may be wiki, documenation, examples, popularization of Ignite, > etc, - literally any contribution), so it is more general way to maintain > contributors list as is. > > Sincerely, > > вт, 26 июн. 2018 г. в 15:24, Anton Vinogradov : > > > Wh

Re: IGNITE-640: multimap initial implementation

Sure, Hope it will be tomorrow ср, 27 июн. 2018 г. в 18:11, Amir Akhmedov : > Anton V, > I put some comments into jira ticket. Can you please take a look once you > have a chance? > > Thanks, > Amir > > On Mon, Jun 18, 2018, 7:54 AM Anton Vinogradov wrote: > > >

Re: Ignite contibutors page

Denis, could you please also fix Committers table? Seems it was broken on last append. пн, 25 июн. 2018 г. в 22:18, Denis Magda : > Done, thanks for your contributions! > > -- > Denis > > On Mon, Jun 25, 2018 at 6:13 AM Иван Федоров wrote: > > > Hi, Igniters! > > I'm contributor and I'm not

Re: IgniteSet implementation: changes required

gt; -- > Denis > > On Mon, Jun 25, 2018 at 6:20 AM Anton Vinogradov wrote: > > > +1 to removal in case there is no easy, fast and consistent way to > restore > > setDataMap on node restart. > > I see that we'll gain some performance drop on size() or keys(), but > t

Re: IgniteSet implementation: changes required

nite persistence this way. > > -- > Denis > > On Tue, Jun 26, 2018 at 1:53 AM Anton Vinogradov wrote: > > > >> Why don't we read data straight from the persistence layer warming RAM > > up > > >> in the background? > > Because it's not a trivial task

Re: Ignite contibutors page

Can we generate contributors page automatically? Git history tells me we missed more than one contributor :) вт, 26 июн. 2018 г. в 15:14, Pavel Kovalenko : > Igniters, > > I've just noticed that I also not mentioned in Contributors table. > > вт, 26 июн. 2018 г. в 12:11, A

Re: Ignite contibutors page

> > > I've just noticed that I also not mentioned in Contributors table. > > > > > > вт, 26 июн. 2018 г. в 12:11, Anton Vinogradov : > > > > > > > Denis, could you please also fix Committers table? > > > > Seems it was bro

Re: Ignite contibutors page

ср, 27 июн. 2018 г. в 6:09, Denis Magda : > Let's try your approach if you can embed it nicely into the site. > > -- > Denis > > On Tue, Jun 26, 2018 at 3:55 PM Anton Vinogradov wrote: > > > Anyway, > > > > I see 166 code contributors, event in case some p

Re: Ignite contibutors page

hat I was added to the Commiters table, but I'm not commiter, just > contributor :) > > ср, 27 июн. 2018 г. в 12:02, Anton Vinogradov : > > > Denis, > > > > I'm bad at html :) > > But my idea is to, at least, have such url [1] published at contributors > >

Re: Ability to check and completely fill transactions on creation

again. > > On Fri, Jun 1, 2018 at 12:59 PM, Anton Vinogradov wrote: > > > Dmitriy, > > > > Unfortunately, we have more than 2 types of txs, full list is > > > > GridDhtTxLocal > > GridDhtTxRemote > > GridNearTxLocal > > GridNearTxRem

Re: Set gitter aside

I fully agree with Konstantin and Denis. Gitter is a project without owner and we should find owner or get rid of it. User & dev lists seem to be enough to keep moving forward. On Thu, Oct 26, 2017 at 6:52 PM, Denis Magda wrote: > I share the same opinion as Konstantin. > >

[GitHub] ignite pull request #3335: Ignite 7003 1

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/3335 Ignite 7003 1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7003-1 Alternatively you can review

Re: Hello!

Hello and welcome! Please get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Instructions on how to contribute

Re: Apache Ignite 2.4 release

Denis, I'll review https://issues.apache.org/jira/browse/IGNITE-6902 On Fri, Jan 12, 2018 at 11:45 PM, Denis Magda wrote: > Here is the page create before: > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 < >

[GitHub] ignite pull request #3409: IGNITE-6711 DataRegionMetrics#totalAllocatedPages...

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/3409 IGNITE-6711 DataRegionMetrics#totalAllocatedPages is not valid after … …node restart Signed-off-by: Anton Vinogradov <a...@apache.org> You can merge this pull r

KEYS.txt renaming

Igniters, I'm going to rename KEYS.txt [1] to KEYS, any objections? See issue [2] for details. [1] http://apache.org/dist/ignite/KEYS.txt [2] https://issues.apache.org/jira/browse/IGNITE-7543

Re: Weird FillFactor metric fluctuation.

Denis, Metrics listed at https://issues.apache.org/jira/browse/IGNITE-7491 are not relevant to FillFactor. On Thu, Jan 25, 2018 at 3:17 AM, Denis Magda wrote: > There will be a way to get used and free size in bytes in Ignite 2.4: >

Re: Orphaned, duplicate, and main-class tests!

single-handedly. We need a plan here. > > Ilya. > > > -- > Ilya Kasnacheev > > 2018-02-05 13:00 GMT+03:00 Anton Vinogradov <avinogra...@gridgain.com>: > > > Ilya, > > > > 1) I don't think it's a good idea to rename classes to *AbstractTest.java &

Re: Orphaned, duplicate, and main-class tests!

Ilya, 1) I don't think it's a good idea to rename classes to *AbstractTest.java since they already have abstract word at definition. We can perform such renaming only in case whole project will be refactored, but I see no reason to do this. 2) All not included test should be included to

Re: Obsolete build projects on CI server

No objections. 5 февр. 2018 г. 18:43 пользователь "vveider" написал: > Hi, Igniters. > > > Found (and marked obsolete) several build project on our CI server: > * [Obsolete] Assembly and Release [1] - previous release project on Java 7. > * [Obsolete] Ignite JDK

Re: Annoying extra steps for enabling metrics

Folks, .setEventsDisabled looks to be a good solution, since we will always call it like .setEventsDisabled(true). Calling .setEventsEnabled(false), since true is a default, looks odd to me. On Wed, Jan 31, 2018 at 11:02 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Alex, >

Re: Should we annotate @CacheLocalStore as @Depricated?

+1 On Tue, Jan 30, 2018 at 9:02 AM, Yakov Zhdanov wrote: > +1 for deprecation > > > > --Yakov > > 2018-01-30 1:06 GMT+03:00 Valentin Kulichenko < > valentin.kuliche...@gmail.com > >: > > > +1 > > > > On Mon, Jan 29, 2018 at 8:31 AM, Andrey Mashenkov < > >

Subject: new committer: Nikolay Izhikov

The Project Management Committee (PMC) for Apache Ignite has invited Nikolay Izhikov to become a committer and we are pleased to announce that he has accepted. Nikolay is an author of the Spark Data Frame API integration [1]. >From what I see, Nikolay one of the most strongest and active

Re: Continuous Query With Transformer are ready for merge

Looks like no one have objections. Nikolay, Let's merge. On Tue, Feb 6, 2018 at 8:45 PM, Nikolay Izhikov <nizhi...@apache.org> wrote: > Hello, Igniters. > > Improvement of Continuous Query public API are ready for merge. > AFAIK Anton Vinogradov and Yakov Zhdanov are happy wit

Re: Removing "fabric" from Ignite binary package name

m the editions’ names. > > > > As for the hadoop future, my personal position is to retire this > component > > and forget about it. I would restart the conversation again after we done > > with 2.4. > > > > — > > Denis > > > > > On Feb

Re: Request for contributor permissions

Hello and welcome! Please get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists <

Re: Orphaned, duplicate, and main-class tests!

ll the possible > broken tests in one go is not feasible. What is the proper way in your > view? What are you suggesting? > > -Val > > On Mon, Feb 5, 2018 at 2:18 AM, Anton Vinogradov <avinogra...@gridgain.com > > > wrote: > > > Ilya, > > > > 1) Still se

Re: IGNITE-4908 is ready for review (Ignite.reentrantLock looks much slower than IgniteCache.lock)

Nikolay, Could you please review changes? On Mon, Feb 12, 2018 at 3:23 PM, Александр Меньшиков wrote: > Hi, guys! I'm waiting (more than 2 months) for CR ignite-4908 ( > https://issues.apache.org/jira/browse/IGNITE-4908 all links inside). It's > about

Re: Ignite diagnostic (SQL system views)

n > constructor > > >> and must override method getRows for data retrieval (this method > called > > by > > >> H2-compatible table and index implementations for ignite system > views). > > >> Almost no fixes to existing parsing engine was made, except so

Re: Author in header of class

Anton, All listed info can be gained from git history. On Wed, Feb 14, 2018 at 1:01 PM, Дмитрий Рябов wrote: > For the first profit you should see maintainer table [1]. > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/How+ >

Re: Author in header of class

how we can solve these 2 issues without author tag. > > > > One more point: IMHO we should remove selection of 2+ mainterners or > > underline one (default) contact point for area. Necessity to choise may > > confuse newcomer. One main (default) mainteiner will redirect rev

Re: Removing "fabric" from Ignite binary package name

; — > Denis > > > On Feb 8, 2018, at 1:51 AM, Anton Vinogradov <avinogra...@gridgain.com> > wrote: > > > > Denis, > > > > "hadoop" and "fabric" words work on same engine. > > > > We have special assembly desctiptors, for

Re: Saving Spark Data Frames merged to master

Nikolay, 2.4 is almost ready to be released. We're fixing final issues to provide stable and fast release. Merging something to 2.4 except blockers is not possible at this phase of release process. Hope, 2.5, with your changes, will be released soon :) On Fri, Feb 9, 2018 at 7:19 AM, Nikolay

Re: Removing "fabric" from Ignite binary package name

view and merge of > IGNITE-7107 [1]. > >>> > >>> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-7107 > >>> > >>> > >>> > >>>> On 19 Dec 2017, at 22:55, Denis Magda <dma...@apache.org> wrote: > &

Re: Stop nodes after test by default - IGNITE-6842

Hi all, > I've made some research about this problem and i think that in general we > should move stopAllGrids method in GridAbstractTest class to > afterTestsStopped method with some changes. Am I right? Let's just add stopAllGrids(flase) to GridAbstractTest 's afterTestsStopped method body. >

Re: Stop nodes after test by default - IGNITE-6842

always better than hidding real problem under automatic > framework feature. > > ср, 7 февр. 2018 г. в 14:05, Anton Vinogradov <avinogra...@gridgain.com>: > > > Hi all, > > > > > I've made some research about this problem and i think that in general > we > >

Re: Apache Ignite 2.4 release

>> I had idea to name old default as FSYNC, but it would be too scientific. So, then it can be FSYNC, SYNC, BACKGROUND and NONE! On Fri, Feb 16, 2018 at 3:49 PM, Dmitriy Setrakyan wrote: > On Fri, Feb 16, 2018 at 6:26 AM, Dmitry Pavlov > wrote: >

Re: Apache Ignite 2.4 release

What about FULL_SYNC SYNC -> default BACKGROUND NODE ? On Fri, Feb 16, 2018 at 3:09 PM, Ivan Rakov wrote: > From my point of view, STRICT is the best option. The name signalizes to > user that this mode provides optional strict guarantees. > FULL_SYNC can be messed with

Re: Apache Ignite 2.4 release

typo NODE -> NONE On Fri, Feb 16, 2018 at 3:21 PM, Anton Vinogradov <avinogra...@gridgain.com> wrote: > What about > FULL_SYNC > SYNC -> default > BACKGROUND > NODE > ? > > On Fri, Feb 16, 2018 at 3:09 PM, Ivan Rakov <ivan.glu...@gmail.com> wrote: >

[GitHub] ignite pull request #3558: IGNITE-6890 General way for handling Ignite failu...

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/3558 IGNITE-6890 General way for handling Ignite failures (NodeInvalidator… … should be replaced with IgniteFailureProcessor) Signed-off-by: Anton Vinogradov <a...@apache.org>

Re: Apache Ignite 2.4 release

Log only mode: flushes application buffers. So, in synced mode without fsync guarantee. That's why I propose to rename it as SYNC. On Fri, Feb 16, 2018 at 4:49 PM, Ilya Lantukh wrote: > I am OK with either FSYNC or STRICT variant. > > LOG_ONLY name means "log without

Re: IgniteDataStreamer silently fails on a server node

Nikolay, I checked your reproducer and it looks like retry helps data streamer to solve this. I set org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl#DFLT_MAX_REMAP_CNT to zero and see test fails now. Looks like second attempt is successful for such case. On Wed, Feb 21, 2018

[BENCHMARK REQUEST] IGNITE-8446

Dmitry, AFAIK, you're able to perform benchmarking of critical code. Could you please check https://issues.apache.org/jira/browse/IGNITE-8446? We have to check https://github.com/apache/ignite/tree/ignite-8446 vs https://github.com/apache/ignite/tree/ignite-8446-master Only one benchmark is

Re: [BENCHMARK REQUEST] IGNITE-8446

can assist. >> >> Hi Ilya, >> >> could you please run required benchmark? >> >> Sincerely, >> Dmitriy Pavlov >> >> пт, 3 авг. 2018 г. в 13:33, Anton Vinogradov : >> >>> Dmitry, >>> >>> AFAIK, you're able to perfor

Re: Removing "fabric" from Ignite binary package name

> wrote: > > > > > > > > Folks, > > > > > > > > Can you please explain the problem with TC and artifacts? Can we just > > > > rename final artifact at the end of a build phase just before > signing, > > > and > > > > l

Re: Service grid redesign

't encourage people to use services this way. > So, if it doesn't complicate the implementation too much, then a warning in > log will be enough, I think. > > Denis > > чт, 26 июл. 2018 г. в 19:56, Anton Vinogradov : > > > Folks, > > > > I don't think that it's a good ide

Re: Dirty Reads and READ_COMMITTED

Hi all, Let's initially agree we're discussing about PESSIMISTIC, since OPTIMISTIC provides no warranty on read before it commited. Also, we should have some reproducer to make sure we're discussing same issue. I guess it's possible to have dirty reads only in following case - first transaction

Re: Removing "fabric" from Ignite binary package name

> > > >>> > > > > > > >>> > > > > > > >>> On Thu, Jun 7, 2018 at 1:49 AM, Petr Ivanov < > > mr.wei...@gmail.com > > > > > > > > > > wrote: > > > > > > >>> &

Re: Removing "fabric" from Ignite binary package name

Since you proposing patch to the community, you are the very man :) ср, 1 авг. 2018 г. в 12:16, Petr Ivanov : > You are convincing the wrong person. > > > > > On 1 Aug 2018, at 12:05, Anton Vinogradov wrote: > > > > Peter, > > > > We had a discussion a

Re: Removing "fabric" from Ignite binary package name

> is > > >> implemented now. > > >> Hard way: full assembly refactoring and hadoop rejection. > > >> > > >> Anyway, after this is merged to master — complete automation systems > > >> revision (TeamCity for example) is required due to

Re: Upgrading Ignite to JCache 1.1

ntation > > > > and tests in 1.0. > > > > > > > > 2018-06-14 21:41 GMT+03:00 Denis Magda : > > > > > > > > > Guys, are you targeting this for the next big Ignite release? > Should be > > > > in > > > > > 3 m

Re: Async cache groups rebalance not started with rebalanceOrder ZERO

Maxim, 1) There is a typo at javadoc, feel free to fix it. 2) It's a bad idea to rebalance more than 1 cache simultaneously. - It's hard to determine error reason in that case when (not "if", but "when" :) ) we'll gain issue at prod (100+ caches case). - We should have limited rebalance load.

Re: ConcurrentLinkedHashMap works incorrectly after clear()

Is it possible to replace current implementation with google's [1] or some other? It a bad idea to have own CLHM and keep it outdated (this version based on CHM from java7!) and broken. [1] https://mvnrepository.com/artifact/com.googlecode.concurrentlinkedhashmap/concurrentlinkedhashmap-lru пт,

Re: Deprecating LOCAL cache

+1 for deprecation in 2.7 and removal in 3.0. (binding) :) I do not see any reason to use local cache instead of CHM, even for testing. чт, 26 июл. 2018 г. в 17:05, Pavel Kovalenko : > Stan, > > I don't think that it is a good way to spawn such crutches in the codebase > for extra rare cases of

Re: Service grid redesign

Real case is A/B testing. When you want to allow new service usage only to 0.1% of users. And only when you sure it works then replace all v1 with v2. So, I vote for versions. Let's do this in maven way (exact version, range, RELEASE or LATEST) чт, 9 авг. 2018 г. в 17:55, Dmitriy Setrakyan : >

Benchmarking

Igniters, All critical code changes should be covered by benchmarks. Currently, community have no dedicated benchmarking service. Everyone can run yandstick locally, but this seems to be useless. You have to run cluster on 4 clients and 4 servers, at least. Currently it is not possible for me

[GitHub] ignite pull request #4558: Ignite 9053

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/4558 Ignite 9053 You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite ignite-9053 Alternatively you can review and apply

Re: Removing "fabric" from Ignite binary package name

! We all owe you a jar of beer and chocolate > (?) > > ;) Send me an invoice and I'll pay for it :) > > > > -- > > Denis > > > > On Fri, Aug 3, 2018 at 7:32 AM Petr Ivanov wrote: > > > >> Yeap. When PR will be ready, I’ll start updating build configurati

Re: Removing "fabric" from Ignite binary package name

, Anton Vinogradov : > Assigned issue to myself. > Going to start implementation this week. > > сб, 4 авг. 2018 г. в 22:20, Petr Ivanov : > >> Thats all for Anton only, my role not worth mentioning. >> >> >> >> > On 4 Aug 2018, at 08:12, Denis Magda wro

Re: Service Grid new design overview

Vyacheslav. It looks like we able to restart all services on grid startup from old definitions (inside cache) in case persistence turned on. Se no problems to provide such automated migration case. Also, we can test it using compatibility framework. BTW, Is proposed solution provides the

Re: Release policy updates

Denis, Currently we provide md5 and sha512 [1]. Should we just get rid of md5? [1] https://www.apache.org/dist/ignite/2.6.0/ сб, 18 авг. 2018 г. в 3:51, Denis Magda : > Peter, Anton V, Igniters, > > The board communicated the following release policy changes: > -- for new releases : >

Re: Some problem with execution ignite.bat in master

Dmitry, Not sure I understand the issue, but I see no reason to rollback anything. In case we have some issues, let's just fix them. сб, 25 авг. 2018 г. в 0:53, Dmitriy Pavlov : > Hi Anton, > > Do you have objections about a partial rollback of changes? > > Sincerely, > Dmitriy Pavlov > > пт, 24

Re: Release policy updates

Issue [1] created. [1] https://issues.apache.org/jira/browse/IGNITE-9346 пн, 20 авг. 2018 г. в 17:27, Denis Magda : > Yes, let’s just remove md5. Will you create the ticket and handle this for > 2.7? > > Denis > > On Monday, August 20, 2018, Anton Vinogradov

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

ild. > > > > > > > >>>>>> > > > > > > > >>>>>> > > > > > > > >>>>>> [1] > > > > > > > >>>>>> > > > > > > > >>>>> > > > > > >

[GitHub] ignite pull request #4364: IGNITE-8783

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/4364 IGNITE-8783 Signed-off-by: Anton Vinogradov You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite ignite-8783 Alternatively

Re: Ability to check and completely fill transactions on creation

it is not OK to allow synchronous > rollback from a filter or a listener. The only action you can do from a > listener is setRollbackOnly() which will cause the transaction to be rolled > back eventually. I think it achieves the same purpose. > > D. > > On Mon, Jul 9, 2018 at

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

Seems, it works. Cancelled hanged suites, they hangs because of problems fixed at master. вт, 24 июл. 2018 г. в 15:20, Anton Vinogradov : > Started more [1] Data Structures tasks to make sure fix works. > > [1] > https://ci.ignite.apache.org/viewType.html

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

Started more [1] Data Structures tasks to make sure fix works. [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures_IgniteTests24Java8=pull%2F4415%2Fhead=buildTypeStatusDiv вт, 24 июл. 2018 г. в 14:59, Alexey Goncharuk : > I will merge the fix once the TC

Re: IGNITE-640: multimap initial implementation

l through gitter/Skype to discuss the > > details? Sometimes 5 minutes of chat can be more productive than long > > running email chains. Please, do not hesitate to directly email me if you > > mind to have a chat/call. > > > > On Wed, Jun 27, 2018 at 11:26 AM Anton

Re: Unknown known issue on cache rebalancing delayed

we should perform exactly 1000 executions, hopefully, we will > stop adding to the queue new tasks at some point. > > On Tue, 4 Sep 2018 at 12:59 Anton Vinogradov wrote: > > > Maxim, > > 20 is not 1k :) > > Also, you forgot to check GridCacheRebalancingAsyncSelfTest

Re: Ticket review checklist

; > > > > > >>>>> > > > > > > > > > >>>>> I'm really confused how we can implement 1.6 and 1.7 > > when > > > > > > dealing > > > > > > > > > with > > > > > > &

Re: [VOTE] Apache Ignite 2.6.0 RC1

wrote: > > > > I thought these steps are to be run automatically within chain and no > > manual steps are required. > > > > Petr, please step in. > > > > ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov : > > > >> I do NOT see that

Re: [VOTE] Apache Ignite 2.6.0 RC1

I do NOT see that API was checked [1] and automated check [2] performed [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__ [2]

Re: [VOTE] Apache Ignite 2.6.0 RC1

try, > > These steps should be outside the chain. > > 2018-07-11 14:49 GMT+03:00 Anton Vinogradov : > > > Automation possible, but it's hard to determine previous version > > automatically (especially when you have 2.x and 3.x releasing > concurrently) > > for API check

Re: [VOTE] Apache Ignite 2.6.0 RC1

s/core/src/main/java/org/apache/ignite/internal/pagemem/wal/record/BaselineTopologyRecord.java > > - > modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/serializer/BaselineTopologyRecordSerializer.java > > > Other changes are tests that were added. >

Re: Ignite 2.6 emergency release suggestion

Igniters, Ignite version still 2.6.0-SNAPSHOT at master, It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a special branch. Some issues affecting backward compatibility can not be merged while version not incremented. ср, 4 июл. 2018 г. в 20:59, Andrey Gura : > Igniters, > >

Re: Ability to check and completely fill transactions on creation

m a remote filter? > Are you planning to call setRollbackOnly()? Calling rollback() or commit() > from any filter or listener should not be allowed. > > D. > > On Tue, Jul 3, 2018 at 1:55 AM, Anton Vinogradov wrote: > > > Dmitriy, Yakov, > > > > I've finaliz

Re: Ignite 2.6 emergency release suggestion

> > > > while version number is frequently used in Ignite code base I believe > > that it's bad approach. See my comment to IGNITE-7823 [1] issue. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-7823 > > On Fri, Jul 6, 2018 at 4:08 PM Anton Vinogradov wrot

Re: Ignite 2.6 emergency release suggestion

Thank you! пн, 9 июл. 2018 г. в 18:57, Andrey Gura : > POM is updated in master branch. > > And no more commits to ignite-2.6 branch. > On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov wrote: > > > > Andrey, > > > > Answered at the same [1] issue. > > An

Re: Apache Ignite 2.4 release

sense to create > a > >> branch to stabilize the release and finalize outstanding tickets. I > created > >> the branch *ignite-2.4*. Please follow the rules below when merging new > >> commits to master: > >> 1) If ticket is targeted for 2.4 release, p

Re: Ignite diagnostic (SQL system views)

I've created IEP-13 [1] to cover all cases. Feel free to create issues. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75962769 On Wed, Jan 24, 2018 at 6:10 PM, Vladimir Ozerov wrote: > Let's start with a single and the most simple view, e.g. >

Re: [VOTE] Apache Ignite 2.4.0 RC1

+1, great work! 2018-03-07 19:34 GMT+03:00 Andrey Gura : > +1 > > Checked compilation under Java 8/9, examples, binaries checksums. > > On Wed, Mar 7, 2018 at 6:45 PM, Yury Babak wrote: > > +1 > > > > Checked Ignite ML: sources and binaries. > > > > Regards,

Re: Race on IgniteAtomicLong#close

Anton, dsMap allows you to share any datastructure between local node's threads without requesting it using retryTopologySafe method (which is heavy). T dataStructure = cast(dsMap.get(key), cls); if (dataStructure != null) return dataStructure; return retryTopologySafe( ... I see no

Re: Maven. Issues with flatten plugin

Nikolay, Sure, I think we have to create IEP "Assembly and Release cleanup and simplification". I see some issues can be attached to this IEP - Fabric word removal - Flatten plugin removal (in possible) - Ignite should be assemblied using package phase, not install in case you want only to

Re: Upsource update required

e Upsource problems, probably there are > > problems > > > with some of our PRs? > > > > > > My example is https://github.com/apache/ignite/pull/3243 PR and > > > https://reviews.ignite.apache.org/ignite/review/IGNT-CR-513 ,- it is > > quite > > > old PR, so I c

Re: Ability to check and completely fill transactions on creation

03:00 Denis Magda <dma...@apache.org>: > Guys, > > Sorry for a dumb question but how the user is expected to use this event? > > -- > Denis > > On Thu, Apr 5, 2018 at 6:06 AM, Anton Vinogradov <a...@apache.org> wrote: > > > Igniters, > > > > As f

Upsource update required

Igniters. Who is responsible for Upsource [1]? I see some strange things at reviews, a lot of fake changes inside reviews. I don't see such changes at PRs. Could you please check we're using stable version and update if necessary? [1] https://reviews.ignite.apache.org

Re: Rebalancing - how to make it faster

we confirm it's stable. Until it > > happens it should be treated as an experimental feature that is turned on > > manually with a parameter like Ilya is suggesting. > > > > Ilya, the name sounds good to me. > > > > -- > > Denis > > > > On Mon

<    1   2   3   4   5   6   7   8   9   >