Re: Switching back to review-then-commit process

Branko, Personally, it's not clear to me why the decision on having RTC process for committers for most critical modules shows our immaturity in a sense of open source collaboration. As Raul properly noted below, the committers were always using RTC informally for most of the modules trying

Tuning number of partitions per cache

Igniters, Let's say I know the following parameters of my system and cluster: - number of nodes and their CPUs; - per node size and total size; - number of caches; - number of entries in the caches; - network bandwidth. And I want to tune a number of partitions per cache to gain much possible

Re: Switching back to review-then-commit process

On Mon, Mar 21, 2016 at 8:45 AM, Branko Čibej wrote: > On 05.03.2016 04:43, Konstantin Boudnik wrote: > > It saddens me to see this coming to it ;( > > Yeah. You guys are introducing red tape that's a barrier for new > committers and a bureaucratic trap for everyone else. > >

[GitHub] ignite pull request: IGNITE-2870 .NET: Fix index names for nested ...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/568 IGNITE-2870 .NET: Fix index names for nested fields in attribute-based SQL configuration You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-2870) .NET: Attribute-based SQL configuration handles nested indexed field incorrectly

Pavel Tupitsyn created IGNITE-2870: -- Summary: .NET: Attribute-based SQL configuration handles nested indexed field incorrectly Key: IGNITE-2870 URL: https://issues.apache.org/jira/browse/IGNITE-2870

Re: Switching back to review-then-commit process

On 05.03.2016 04:43, Konstantin Boudnik wrote: > It saddens me to see this coming to it ;( Yeah. You guys are introducing red tape that's a barrier for new committers and a bureaucratic trap for everyone else. For example: what happens when a module owner takes off for a couple months? Which is

Re: Switching back to review-then-commit process

I recommend to add Andrey Novikov as Visor maintainer. On Mon, Mar 21, 2016 at 10:16 PM, Denis Magda wrote: > Oops, a misprint. Fixed, thanks Pavel. > > -- > Denis > > > On 3/21/2016 6:14 PM, Pavel Tupitsyn wrote: > >> Suspicious entries: >> * C++ API Ivan Veselovsky >> *

Re: Switching back to review-then-commit process

Oops, a misprint. Fixed, thanks Pavel. -- Denis On 3/21/2016 6:14 PM, Pavel Tupitsyn wrote: Suspicious entries: * C++ API Ivan Veselovsky * Docker, Mesos, YARN integration Igor Sapego On Mon, Mar 21, 2016 at 6:08 PM, Sergi Vladykin wrote: Looks good. Sergi

Re: Switching back to review-then-commit process

Suspicious entries: * C++ API Ivan Veselovsky * Docker, Mesos, YARN integration Igor Sapego On Mon, Mar 21, 2016 at 6:08 PM, Sergi Vladykin wrote: > Looks good. > > Sergi > > 2016-03-21 16:37 GMT+03:00 Denis Magda : > > > Igniters, > > > > I've

Re: Switching back to review-then-commit process

Looks good. Sergi 2016-03-21 16:37 GMT+03:00 Denis Magda : > Igniters, > > I've prepared a draft of the maintainers list. > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers > > Please review it and/or adjust

[jira] [Created] (IGNITE-2869) IGFS: Optimize IgfsListingEntry write.

Vladimir Ozerov created IGNITE-2869: --- Summary: IGFS: Optimize IgfsListingEntry write. Key: IGNITE-2869 URL: https://issues.apache.org/jira/browse/IGNITE-2869 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-2868) IGFS: Investigate whether trash require further striping.

Vladimir Ozerov created IGNITE-2868: --- Summary: IGFS: Investigate whether trash require further striping. Key: IGNITE-2868 URL: https://issues.apache.org/jira/browse/IGNITE-2868 Project: Ignite

[jira] [Created] (IGNITE-2867) IgniteConsistencyException during running load test (cache-atomic-invoke-retry-validator)

Ilya Suntsov created IGNITE-2867: Summary: IgniteConsistencyException during running load test (cache-atomic-invoke-retry-validator) Key: IGNITE-2867 URL: https://issues.apache.org/jira/browse/IGNITE-2867

Re: Switching back to review-then-commit process

Igniters, I've prepared a draft of the maintainers list. https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers Please review it and/or adjust it whenever is needed. If you have any thoughts, concerns let's discuss them there. -- Denis

[GitHub] ignite pull request: IGNITE-1957 .NET: Collections, dictionaries, ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/302 --- 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 feature is

[jira] [Created] (IGNITE-2866) .NET: Automatic JAVA_HOME detection

Pavel Tupitsyn created IGNITE-2866: -- Summary: .NET: Automatic JAVA_HOME detection Key: IGNITE-2866 URL: https://issues.apache.org/jira/browse/IGNITE-2866 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-2865) Continuous query event passed to filter should be immutable for users.

Vladimir Ozerov created IGNITE-2865: --- Summary: Continuous query event passed to filter should be immutable for users. Key: IGNITE-2865 URL: https://issues.apache.org/jira/browse/IGNITE-2865

[GitHub] ignite pull request: Ignite 2806

Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/547 --- 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 feature

[jira] [Created] (IGNITE-2864) Need update local store from primary and backups

Semen Boikov created IGNITE-2864: Summary: Need update local store from primary and backups Key: IGNITE-2864 URL: https://issues.apache.org/jira/browse/IGNITE-2864 Project: Ignite Issue