Re: One more round for PR review

Hi Alexey, thank you for review. Hi Igor, could you please merge this PR? вт, 15 мая 2018 г. в 11:18, Alexey Kuznetsov <akuznet...@apache.org>: > Looks good for me now. > > On Tue, May 15, 2018 at 12:38 AM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > &g

Re: Tests coverage report of Ignite 2.5 core module

Hi Alexander, I did not quite understand how this list of top tests was obtained. It does not look like sorted. Can you clarify? Sincerely, Dmitriy Pavlov пн, 14 мая 2018 г. в 20:48, Александр Меньшиков : > Vyacheslav, > I have made a simple ranking for your data for

Re: stopAllGrids() used by default and further steps

l=buildTypeStatusDiv_IgniteTests24Java8=pull%2F3844%2Fhead > Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-581 > JIRA: https://issues.apache.org/jira/browse/IGNITE-8266 > > Will you or others have to to review it? > > > > пт, 4 мая 2018 г. в 14:24, Dmitry P

Re: method arguments code style

.org/jira/browse/IGNITE-5698 > [2] > http://apache-ignite-developers.2346864.n4.nabble.com/abbrevation-rules-plugin-td19356.html > > On Tue, May 8, 2018 at 8:34 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > Folks, I've messed with another topic, where Vladimir

Re: IGNITE-6430 (Done) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically

Hi Dmitriy G, could you please pick up this review? Sincerely, Dmitriy Pavlov чт, 10 мая 2018 г. в 15:50, Александр Меньшиков : > Hi, > > I have fixed problem with the test > CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime. > > Please review and merge if

Re: One more round for PR review

Hi Alexey K, could you please check that all proposals were applied? Sincerely, Dmitriy Pavlov чт, 10 мая 2018 г. в 22:59, Igor Rudyak : > Hi guys, > > I addressed all the comments and need one more round of review for the PR: > https://github.com/apache/ignite/pull/3940 > >

Re: Transparent Data Encryption (TDE) in Apache Ignite

rting working on it and expecting to implement it in a couple > months. > > В Пн, 14/05/2018 в 17:33 +0300, Dmitry Pavlov пишет: > > Hi Nickolay, > > > > Thank you for sharing results. > > > > I would suggest to make phase 1 as small as possible, for example

Re: abbrevation rules plugin

is now published. Sincerely, Dmitriy Pavlov пн, 14 мая 2018 г. в 19:14, Anton Vinogradov <a...@apache.org>: > Jar already attached to issue :) > > see https://issues.apache.org/jira/browse/IGNITE-5698 > > пн, 14 мая 2018 г. в 19:05, Dmitry Pavlov <dpavlov@gm

Re: abbrevation rules plugin

Vyacheslav, > > > > I had discussion about this plugin. As GridGain representative I approve > > change of file headers and making this tool fully opensource. > > > > So please proceed with distributive build. > > > > Best Regards, > > Dmitriy Palvov &

Re: Transparent Data Encryption (TDE) in Apache Ignite

> > Other phases to be added. > > Thoughts or objections? > > В Пн, 07/05/2018 в 10:19 +, Dmitry Pavlov пишет: > > Hi, just 2 remarks, > > > > 1) We should somehow separate issue with disc corruption and incorrect > key. > > For incorrect key I s

Re: Tests coverage report of Ignite 2.5 core module

load and unpack the archive first: > > https://www.dropbox.com/s/rdgs1svvojm757x/ignite-2.5-core-module-tests-coverage-report-rev-d83f1ec.zip > > > On Mon, May 14, 2018 at 5:12 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > Hi Vyacheslav, > > > > > http

Re: Tests coverage report of Ignite 2.5 core module

Hi Vyacheslav, https://www.dropbox.com/s/rdgs1svvojm757x/ignite-2.5-core-module-tests-coverage-report-rev-d83f1ec.zip?dl=0_subpath=%2Fcoverage-report%2Findex.html says error 400 for me. Sincerely, Dmitriy Pavlov пн, 14 мая 2018 г. в 17:06, Vyacheslav Daradur : > Hi,

Re: async operation is not fair async

IMO you can complete async operations one before another if these operations are related to independent data. It is strange why Ignite users are not confused by current API. So I support Dmitriy's G. suggestion. пт, 11 мая 2018 г. в 20:24, Dmitriy Setrakyan : > Guys, > >

Re: Replace Cron4J with Quartz for ignite-schedule module.

solved at Upsource? > Changed state to IP. > > пн, 23 апр. 2018 г. в 20:00, Dmitry Pavlov <dpavlov@gmail.com>: > > > Hi Andrey, > > > > Could you please pick up review? > > > > Sincerely, > > Dmitriy Pavlov > > > > пн, 23 апр

Re: IGNITE-640: multimap initial implementation

Hi Amir, This is a very necessary contribution, the patch defenetely will not be ignored. Igniters, Who can make a review from the committers? Sincerely, Dmitriy Pavlov вт, 8 мая 2018 г. в 5:52, Amir Akhmedov : > Hi Igniters, > > Can someone take a look at this PR

Re: New committer: Ivan Rakov

Hi Ivan, please accept my sincere congratulations! Best Regards, Dmitriy Pavlov чт, 10 мая 2018 г. в 19:09, Denis Magda : > The Project Management Committee (PMC) for Apache Ignite > has invited Ivan Rakov to become a committer and we are pleased > to announce that he has

Re: Using GraalVM instead of standard JVM

Hi Peter, It seems it is one more argument to implement selectable VM for existing run-all chain instead of creating one more. Would it be easy to add one more option once JDK 9 run is ready? Sincerely, Dmitriy Pavlov чт, 10 мая 2018 г. в 15:58, Dmitriy Setrakyan : >

Re: Ticket review checklist

> > Dmitry, > > > > can you please perform an excercise of looking that piece of code up > > > > > (org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache), > > telling us how an ideal message should look like in this case? > > > > Thanks, > > > > -- > > Ilya Kasnacheev

Re: Ticket review checklist

gt; > > maintained > > > > > > > > when > > > > > > > > > operation makes sense on both platforms. If method cannot > be > > > > > > > implemented > > > > > > > > in > > > > &

Re: need review for PR

Hi Igor, I'll try to find a reviewer. We also need expert opinion about here https://issues.apache.org/jira/browse/IGNITE-6500 It is literally 1 line of code, but we need to be sure we can skip nulls. Could you please review? Sincerely, Dmitriy Pavlov ср, 9 мая 2018 г. в 8:01, Igor Rudyak

Re: method arguments code style

.n4.nabble.com/abbrevation-rules-plugin-td19356.html > > On Tue, May 8, 2018 at 8:34 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > Folks, I've messed with another topic, where Vladimir was going to update > > review check-list. > > > > Here I've updat

Re: method arguments code style

. Sincerely, Dmitriy Pavlov вт, 8 мая 2018 г. в 20:05, Dmitry Pavlov <dpavlov@gmail.com>: > I thought that Vladimir will update. > > By the way, Denis M, I propose to grant access to the wiki to Dmitry G. > WDYT? > > вт, 8 мая 2018 г. в 19:28, Dmitriy Govorukhin < >

Re: method arguments code style

> > them > > > > horizontally, or vertically (example 2). But with proposed code > style you > > > > have to do zigzag movements in general case because lines are not > aligned > > > > (example 1). > > > > Merge conflicts on multiliners are hardly of major co

Re: IGNITE-3999 review

the ticket, especially when the link is not even > > provided in the email. > > > > For example, the subject of this thread should have been: "IGNITE-3999: > > Support case insensitive search in SQL" > > > > D. > > > > On Tue, May 8, 2018 at 2:2

Re: Optimize GridLongList serialization

s created: >> https://issues.apache.org/jira/browse/IGNITE-8054 >> >> 2018-03-27 10:04 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: >> >>> Sorry, Dmitiry, I meant Ignite, not GridGain (memories of pre-apache >>> coding). I am assuming tha

Re: IGNITE_HOME for persistence

13, 2018 at 7:01 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Hi, > > > > do we have a task to print this warning message? > > > > It seems we don't print warning currently. > > > > I do not think we have a ticket. As AG mentioned, th

Re: IGNITE-6879: Support Spring Data 2.0

for PRs because of ignite-spring-data_2.0 module is absent in these branches. Sincerely, Dmitriy Pavlov вт, 8 мая 2018 г. в 15:55, Dmitry Pavlov <dpavlov@gmail.com>: > Hi Roman, > > now TC passes for 1.0. In the same time new suite is not executed on TC. > > I've asked P

Re: IGNITE-6879

As i may see localy problem with tests > was fixed > > пн, 7 мая 2018 г. в 17:24, Dmitry Pavlov <dpavlov@gmail.com>: > >> Hi, I've replied to ticket, seems old tests are now failing after >> applying patch locally. >> >> I've also added 2 su

Re: memory-only mode for Ignite indexes

Hi Igniters, I may repeat what was said early, but still: I prefer way of speeding up indexes proposed by Vladimir in addition to page replacement optimizations related to index pages. Also recently Ivan Rakov created issue intended to optimize findPageForReplacement method, it can also help

Re: IGNITE-3999 review

; On Tue, May 8, 2018 at 5:54 AM, Amir Akhmedov <amir.akhme...@gmail.com> > wrote: > > > Hi Nikolay, Dmitry Pavlov, > > Can you take a look at this PR or maybe you have an idea when it probably > > can be reviewed? > > > > Thanks, > > Amir > >

Re: Migration guide

+1 from me to approach (co-locating migration guide and main documentation). пн, 7 мая 2018 г. в 21:00, Denis Magda : > Guys, > > It's planned to migrate to new documentation engine within 2.6 timeframe, > thus, I would suggest us storing migration guides in Github (together

Re: MTCGA 5th mass run-all

ts day. Hope it is coming some time in future :) > > On Mon, May 7, 2018 at 3:38 AM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Hi Folks, > > > > I've started mass run-all last weekend. In short - 361 tests failed, and > > 12 suites were unable to

Re: Apache Ignite 2.5 release

t; On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > I did not understand process. > > > > Is it required to receive someone reply that issue is agreed to be > included > > into release? > > > > Or because there is no r

Re: Hello Ignite Community

Hi Radhu, Monil, Main place where Ignite docs live is https://apacheignite.readme.io/docs More deep and specific articles targetted to Ignite developers and committers can be found in wiki https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Home But readme.io is best place to

Re: IGNITE-6879

will check both integrations. Ideally we could run this suite one more time before merge. Sincerely, Dmitriy Pavlov пн, 7 мая 2018 г. в 15:46, Dmitry Pavlov <dpavlov@gmail.com>: > Hi Roman, > > Currently I'm checking the changes. Because of applying idea to copy all > changes an

Re: IGNITE-6879

rward for news >> сб, 28 апр. 2018 г. в 19:29, Dmitry Pavlov <dpavlov@gmail.com>: >> >>> I hope so! >>> >>> There was several posts related to review time, and AI community is now >>> trying to reduce it. Now it is about 70 tickets wai

MTCGA 5th mass run-all

Hi Folks, I've started mass run-all last weekend. In short - 361 tests failed, and 12 suites were unable to complete ( vs tests 309 suites 24 - 3 weeks early). We have markable positive dynamics in fixing existing tests. Current failed test count grow came from new ZookeeperDiscovery suites

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hi, just 2 remarks, 1) We should somehow separate issue with disc corruption and incorrect key. For incorrect key I suggest to adopt Key Check Value (KCV) techique. It is some heading bytes (e.g. 3 bytes) of encrypted 00...00 block using this key. KCV allow us to check key decrypted correctly and

Re: missing website info

Hi Maxim, I had similar idea to provide list of "Needed Contributions" from point of view of community/PMCs. Not all issues have equal pripority for product and it is easier to find reviewer for such wanted issues, than for low priority improvement. Sincerely, Dmitriy Pavlov пн, 7 мая 2018 г.

Re: missing website info

Hi Dmitriy Could you explain what is the difference between: - disk is a copy of the memory (only for recovery purposes) - disk is a data storage with memory used as a performant caching layer I assume it is all about DataRegionConfiguration.setPersistenceEnabled and there is no other options I

Re: Apache Ignite 2.5 release

org>: > Igniters, > > I got lost. Were all the bugs reported in this thread fixed and merged into > 2.5 branch? Is there any bug which fix is still in progress? > > Just want to know when the QA and bugs fixing stage is over. > > -- > Denis > > On Thu, May 3,

Re: stopAllGrids() used by default and further steps

Hi Maxim, I think next step can be creation of Junit4/5 IgniteAbstractTest and/or IgniteTestRunner. Would you like to contribute this prototype? Regarding TC run there is a number of suspicious tests (e.g. IgnitePdsNativeIoTestSuite2:

Re: Apache Ignite 2.5 release

Hi Andrey, Igniters, I propose to include https://issues.apache.org/jira/browse/IGNITE-8347 fix to 2.5. It is quite isolated. Memory leak can be reproduced if node in embedded mode is restarted under the same process (thread is alive and cleanup is not performed). Sincerely, Dmitriy Pavlov сб,

Re: method arguments code style

Hi Dmitriy, I like your proposal, so +1 from me. I think it would make code more readable and easy to understand. Sincerely, Dmitriy Pavlov чт, 3 мая 2018 г. в 11:31, Dmitriy Govorukhin : > Hi folks, > > I read >

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Hi Dmitriy, As far as I understand manual activation will not be required for in-memory mode (same for persistence). Change means we will change node state from 'joined-inactive' to 'joined-active' according to that user defined in policy (cluster grow policy). Default will be allow to rebalance

Re: IGNITE-6879

апр. 2018 г. в 18:24, Роман Меерсон <homich1...@gmail.com>: > Hi all! > > Soon we'll celebrate 2 months of my PR :) > Maybe it could be merged? > пн, 23 апр. 2018 г. в 18:52, Dmitry Pavlov <dpavlov@gmail.com>: > >> No, nothing yet. I'm going to look to new

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

I like AI 2.5 now, but then release AI 2.6 with (BL)AT fix. Probably we will find some more changes to be delivered to users. сб, 28 апр. 2018 г. в 17:56, Vladimir Ozerov : > Yakov, > > Messages would help users understand what is wrong earlier, but will not > protect them

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

reeze AI 2.5 scope > completely. Instead, we propose to add BLT fix to AI 2.5, but disallow > anything else. This way most contributors will continue working with master > as usual. > > On Sat, Apr 28, 2018 at 5:36 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > >

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

-0.9 from me, because I want users get performance fix https://issues.apache.org/jira/browse/IGNITE-7638 and 2 related fixes faster. сб, 28 апр. 2018 г. в 17:35, Dmitry Pavlov <dpavlov@gmail.com>: > Hi Vladimir, > > The fact that we will postpone the release will some

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Hi Vladimir, The fact that we will postpone the release will somehow allow users to receive fixes faster? What if we will fix (BL)AT it in 2.6 instead? It will be additional issue for all developers to maintain 2.5 & master branches. Sincerely, Dmitriy Pavlov сб, 28 апр. 2018 г. в 17:28,

Re: Ticket review checklist

gt; > > > > > > > > On Tue, Apr 24, 2018 at 4:51 PM, Eduard Shangareev < > > > > > eduard.shangar...@gmail.com> wrote: > > > > > > > > > > > Igniters, > > > > > > > > > > > > I don't understand

Re: Apache Ignite 2.5 release

t; > >> Branches will be compared and changes that should be included to AI > > >> 2.5 will be identified. > > >> > > >> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov <mr.wei...@gmail.com> > > wrote: > > >> > Possibly it is Andrey Gur

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

gt; This is unless you are OK with putting all these tests, most of > > >> which > > >> > are > > >> > > > red and some are hanging, in production test suites and > therefore > > >> > > breaking > > >> >

Re: IGNITE-8167

ute guide I was only need to run tests that > have been affected by my changes. So I used Persistent Data Store test > suite. > > https://ci.ignite.apache.org/viewLog.html?buildId=1187554=buildResultsDiv=IgniteTests24Java8_RunAllPds > > On Mon, Apr 23, 2018 at 9:16 PM Dmitry Pa

Re: IGNITE-8167

some time ago. Tests have been passed. I've changed > the state of Jira task to "Patch available" almost two weeks ago. The patch > is just one line of code, so I think it can be reviewed fast :) Thanks. > > On Mon, Apr 23, 2018 at 1:23 PM Dmitry Pavlov <dpavlov@

Re: Replace Cron4J with Quartz for ignite-schedule module.

Hi Andrey, Could you please pick up review? Sincerely, Dmitriy Pavlov пн, 23 апр. 2018 г. в 17:39, Dmitriy Setrakyan <dsetrak...@apache.org>: > Dmitriy, who is a good candidate within the community to review this > ticket? > > On Mon, Apr 23, 2018 at 6:10 AM, Dmit

Re: IGNITE-6879

t; >>> > > > After some time (probably on 3.0 release) we could change naming as >>> > Denis >>> > > > suggested. >>> > > > >>> > > > Anyway I leave this decision up to you, just tell me what is the >>>

Re: Replace Cron4J with Quartz for ignite-schedule module.

Hi Igniters, it seems ticket https://issues.apache.org/jira/browse/IGNITE-5565 is still in PA state. What are our next steps? Who did review of this patch? Sincerely, Dmitriy Pavlov ср, 28 июн. 2017 г. в 1:40, Denis Magda : > Yakov, > > No, the mentioned discussion didn’t

Re: Writing a helper for KafkaStreamer

Hi Igniters, It seems issue is still in PA state. Who can pick up https://issues.apache.org/jira/browse/IGNITE-5416 review? Sincerely, Dmitriy Pavlov вт, 6 июн. 2017 г. в 10:56, Dmitriy Setrakyan : > Thanks, Mike! Sounds great. > > On Tue, Jun 6, 2017 at 12:26 AM,

Re: Topology-wide notification on critical errors

Hi Igniters, +1 to idea of sending this failure to 3rd party monitoring tool. I also think most of users have its favorite monitoring tool and connect all systems to it. But I'm not sure it is easy to implement. Sincerely, Dmitriy Pavlov сб, 21 апр. 2018 г. в 13:09, Dmitriy Setrakyan

Re: IGNITE-8167

> As I mentioned above, first we will have only archiver thread crashed > and > > > absolute wal started from 0, but we will have alive ignite instance. > Logs > > > can be found in attach. > > > > > > > > > On Fri, Apr 6, 2018 at 5:

Re: Ticket review checklist

Hi Igniters, +1 to idea of checklist. +1 to refactoring and documenting code related to ticket in +/-20 LOC at least. If we start to do it as part of our regular contribution, code will be better, it would became common practice and part of Apache Ignite development culure. If we will hope we

Re: Is it time to move forward to JUnit4 (5)?

First of all it should be new way for testing without modificaitions in JUnit3-style tests and its base classes. Test would migrate one-by one. If old test is quite stable on 3 and no need to mute it/apply config variations (Parametrized annotation) we could keep it as is for some time. ср, 18

Is it time to move forward to JUnit4 (5)?

Hi Igniters, During MTCGA monitoring I’ve discovered a number of issues related to test framework itself. In addition it is not convinient to mute tests on TC, because in branches (e.g. 2.5 and in master) we can’t mute it separately. So some tests, which already fixed are shown as failed in our

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

> >> > > > sure I can't fix them all, not in one commit, not ever. Nobody can > >> do > >> > > that > >> > > > single-handedly. We need a plan here. > >> > > > > >> > > > Ilya. > >> >

Re: Docker deployment with EXTERNAL_LIBS environment variable

Hi Petr, I've mentioned you in the ticket. Is it obvious change so we could apply patch? Or could you advise maintainer/expert here? Sincerely, Dmitriy Pavlov ср, 18 апр. 2018 г. в 7:27, Roman Shtykh : > I had the same problem (pretty common not having -i option) and fixed

Re: [TEST ERROR] org.apache.spark.sql.AnalysisException: Path does not exist

Hi Nikolay, Could you please step in? Sincerely, Dmitriy Pavlov вт, 17 апр. 2018 г. в 18:19, Akmal Chaudhri : > I am running the Spark DataFrame tests on Java code locally. > > One test is failing because of a path issue. In the Java code is the line: > > *//Load

Re: Make TC Green in OSGI: IgniteKarafFeaturesInstallationTest

Kripalani <raul.kripal...@consensys.net>: > Hey Dmitry, > > Loving the name of the endeavour [make TC green again] ;-) > Feel free to do that for now. I'll take a look as soon as I have some > spare cycles. > > Cheers! > > On Fri, Apr 13, 2018 at 3:24 PM, Dmitry Pavlo

Re: Deprecate CacheRebalanceMode.NONE

+1 вт, 17 апр. 2018 г. в 19:14, Pavel Kovalenko : > +1 > I also agree to remove this option in 3.0 > > 2018-04-17 19:00 GMT+03:00 Yakov Zhdanov : > > > +1 here > > > > Always wanted to remove ForceKeysRequest =) > > > > --Yakov > > >

Re: [jira] [Created] (IGNITE-8279) Clients can't operate on services after deactivation

Hi Raymond, I thought 2.5 is already freezed. Several days remained to release (vote), so it is not likely this issue can be done. Probably Denis M. or Andrey G. could correct me if I'm wrong. Sincerely, Dmitriy Pavlov пн, 16 апр. 2018 г. в 21:52, Raymond Wilson :

Re: Mass TC Run-All during this weekend

cult to analyze the report, I guess the things are moving > in a right direction. Probably, there is a clearer format you can come up > with. Thanks for keep driving it. > > -- > Denis > > On Mon, Apr 16, 2018 at 3:04 AM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > >

Re: Mass TC Run-All during this weekend

/confluence/pages/viewpageattachments.action?pageId=73631266 Sincerely, Dmitriy Pavlov вс, 25 мар. 2018 г. в 15:50, Dmitry Pavlov <dpavlov@gmail.com>: > Hi Igniters, > > We have the positive dynamics in the resolving MTCGA JIRA tasks, and I > must mention the contributions of

Re: Make TC Green in OSGI: IgniteKarafFeaturesInstallationTest

Hi Igniters, I've created https://issues.apache.org/jira/browse/IGNITE-8254 and muted test. Second test in OSGI suite is also flaky, and probably we should remove OSGI build from Run-All at all. What do you think? Sincerely, Dmitriy Pavlov вт, 10 апр. 2018 г. в 19:54, Dmitry Pavlov <dpav

Re: Apache Ignite 2.5 release

I've changed my ticket version assignment, and a lot of Igniters changed. Filter for double-check tickets related to you

Re: Ignite documentation is broken

Hi Dmitriy, It seems attachment is not displayed, probaly image attachment is not allowed by dev.list. readme works for me too. Sincerely, Dmitriy Pavlov ср, 11 апр. 2018 г. в 11:56, Dmitriy Setrakyan : > This is what I see (attached) > > On Wed, Apr 11, 2018 at 1:52

Re: Remove cache groups in AI 3.0

Hi Igniters, Actually I do not understand both points of view: we need to (keep/remove) cache groups. Only one reason for refactoring I see : 'too much fsyncs', but it may be solved at level of FilePageStoreV2 with new virtual FS for partitions/index data, without any other changes. Sincerely,

Re: IGNITE-6827 - Review needed.

Hi Pavel, thank you for bring up test questions. It seems my previous comments were not taken into account. Igniters, let me remind we should get passing TC suites before merge, https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers

Make TC Green in OSGI: IgniteKarafFeaturesInstallationTest

Hi Raúl, Igniters, Test related to OSGI/Karaf (IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled) is currently failing https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=451522206339372479=%3Cdefault%3E=testDetails with low success rate. Recently

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

; > was the cause of performance drop ( > 10% vs AI 2.4.0) on the following > > > benchmarks (LOG_ONLY): > > > > > >- atomic-put (16 %) > > >- atomic-putAll (14 %) > > >- tx-putAll (11 %) > > > > > > As I understand it

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

xes #3656. > > > was the cause of performance drop ( > 10% vs AI 2.4.0) on the following > benchmarks (LOG_ONLY): > >- atomic-put (16 %) >- atomic-putAll (14 %) >- tx-putAll (11 %) > > As I understand it is greater than initial assessment. > >

Re: IGNITE-6252

Hi, It seems your question is related to code of Cassandra cache store. According to git, author of this code is Igor Rudyak, and it seems Igor is also watcher of ticket, where you were asking. Igor, could you please advice? Sincerely, Dmitriy Pavlov вт, 10 апр. 2018 г. в 10:49,

Re: Remove cache groups in AI 3.0

Hi Vladimir, We can solve "too many fsyncs" or 'too many small files' by placing several partitions of cache group in one file. We don't need to get rid from cache groups in this case. It is not trivial task, but it is doable. We need to create simplest FS for paritition chunks inside one file.

Re: IGNITE-6879

Ignite2QueryGenerator or module removing? >> пн, 9 апр. 2018 г. в 23:40, Dmitry Pavlov <dpavlov@gmail.com>: >> >>> There are 2 classes IgniteQueryGenerator with same package name. Ignite >>> in Idea can't compile. >>> >>> >>> пн, 9 а

Re: IGNITE-6879

There are 2 classes IgniteQueryGenerator with same package name. Ignite in Idea can't compile. пн, 9 апр. 2018 г., 21:38 Роман Меерсон <homich1...@gmail.com>: > Hi Dmitry! > Could you specify where you find conflict? Because I don’t have any. > пн, 9 апр. 2018 г. в 21:09, Dmitry

Re: IEP-18: Transparent Data Encryption

Hi Nikolay, I would like to look to IEP. Please give me couple days. Sincerely, Dmitriy Pavlov пн, 9 апр. 2018 г. в 20:11, Nikolay Izhikov : > Hello, Igniters. > > I'm going to create tickets and start implementation of TDE in a few days. > > Any objections? > > В Пн,

Re: Rebalancing - how to make it faster

>> >> On Mon, Mar 26, 2018 at 8:04 PM, Anton Vinogradov < > > a...@apache.org > > > > > > > > > >> wrote: > > > > > >> >> > > > > > >> >> > >> It is impossible to disable WAL only for cer

Re: IGNITE-6879

Hi Denis, could we support just one version instead of leaving compatible module? Sincerely, Dmitriy Pavlov пн, 9 апр. 2018 г. в 20:08, Dmitry Pavlov <dpavlov@gmail.com>: > > > пн, 9 апр. 2018 г. в 20:07, Dmitry Pavlov <dpavlov@gmail.com>: > >> Hi Roman,

Re: IGNITE-6879

Hi Roman, I've applied PR locally and I have class name conflict at least for org.apache.ignite.springdata.repository.query.IgniteQueryGenerator How could we solve it? Is it better to rename class for new plugin version? Sincerely, Dmitriy Pavlov пт, 6 апр. 2018 г. в 17:38, Dmitry Pavlov

Re: Upsource update required

Hi Vitaliy, Thank you for your time and updating Upsource. It seems for PR branches with master merge into branch, Upsource still shows different changes with PR (github). Example https://reviews.ignite.apache.org/ignite/review/IGNT-CR-556 & https://github.com/apache/ignite/pull/3243 This

Re: Service grid redesign

Hi Igniters, I like automatic redeploy which can be disabled by config if user wants to control this process. What do you think? Sincerely, Dmitriy Pavlov пт, 6 апр. 2018 г. в 18:29, Denis Mekhanikov : > Val, > > I don't really like the idea of automatic redeployment of

Re: IGNITE-8167

Hi Pavel, Thank you. Could you please attach logs/stacktraces. Now it is not quite clear where Ignite has failed? Could you please share your JIRA ID? Hi PMCs, could you please add Pavel to contributor list so https://issues.apache.org/jira/browse/IGNITE-8167 issue can be assigned? Sincerely,

Re: IGNITE-6879

38c94=/ >> > > > modules/spring-data-2.0/src/main/java/org/apache/ignite/ >> > > > springdata/repository/query/IgniteQueryGenerator.java >> > > > > > >> > > > > >> > > > > Best regards, >> > > > > Slava. >> > > > > >> > > > > 2018-04-05 14:59 GMT+03:00 Роман Меерсон <homich1...@gmail.com>: >> > > > > >> > > > > > Ok, so waiting for accept and commit >> > > > > > >> > > > > > чт, 5 апр. 2018 г. в 15:29, Alexey Kukushkin < >> > > > kukushkinale...@gmail.com >> > > > > >: >> > > > > > >> > > > > > > Roman, >> > > > > > > >> > > > > > > Just pay commiter's (Dmitry Pavlov will most likely commit >> your >> > > code) >> > > > > > > attention to include the new test suite to TeamCity >> > configuration. >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > >> >

Re: Upsource update required

; > > On Fri, Apr 6, 2018 at 3:05 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > Hi Igniters, Anton, > > > > According to my experience upsource works well, except 1 suspicious case > > with my PR. > > > > So I'm not sure if there are Upsour

Re: Upsource update required

Hi Igniters, Anton, According to my experience upsource works well, except 1 suspicious case with my PR. So I'm not sure if there are Upsource problems, probably there are problems with some of our PRs? My example is https://github.com/apache/ignite/pull/3243 PR and

Re: Ability to check and completely fill transactions on creation

Hi Igniters, I also do not see any reasons against this solution. But I have concern about performance. How can you estimate impact to performance ? Sincerely, Dmitriy Pavlov чт, 5 апр. 2018 г. в 17:20, Nikolay Izhikov : > +1 from me. > > Let's have this events! > > I

Re: [jira] [Comment Edited] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy

.git;a=search;h=28304fdb5984eb426fbf6c20a71c2072a3339c6a;s=reed.sandb...@drawbridge.com;st=author> to contributor list so issue https://issues.apache.org/jira/browse/IGNITE-6815 can be assiged. Sincerely, Dmitriy Pavlov ср, 4 апр. 2018 г. в 19:08, Dmitry Pavlov <dpavlov@gmail.com>: > Hi Reed, > &

Re: [jira] [Comment Edited] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy

t; > > On Fri, Mar 30, 2018 at 11:44 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > Hi Igniters, > > > > Who could advice me how to create PR from these commits? Should PR be > > always created by commit author? > > > > Hi Ree

Re: Make TC issues seems to be hung up

gt; > > > Please respond here. > > > > D. > > > > On Tue, Apr 3, 2018 at 5:27 AM, Dmitry Pavlov <dpavlov@gmail.com> > > wrote: > > > > > Hi Igniters, > > > > > > Following issues for tests fixing seems

Re: IGNITE-6879

Hi Igniters, I am going to review these changes in 3-4 days. If everything is ok and if there is no objections, I will merge it. Hi Denis, are you agree with proposed change? Sincerely, Dmitriy Pavlov ср, 4 апр. 2018 г. в 14:26, Дмитрий Рябов : > I agree that

Re: abbrevation rules plugin

your notes I will fix them shortly. > > > > As far as I understand someone of GridGain employee should confirm the > > plugin's code's donation. It’d be great to confirm that by corporate > > email. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-

<    1   2   3   4   5   6   7   >