Re: Jira Process Change

Cos and all, I changed column title to "Maintainer". This fits better. Now we need to agree on release manager for 1.6. I think I can do it for 1.6, then we can try rotating between PMCs. Agree? --Yakov

Re: MS VS 2010 for platforms

Thanks for explanations! On Wed, Jan 13, 2016 at 2:00 PM, Pavel Tupitsyn wrote: > Hi Sergey, > > You can build C++/.NET with any VS (2010+), you just have to click "upgrade > VC++ compilers" on C++ projects. I use VS2015 Community, everything works > just fine. > > Why

[jira] [Created] (IGNITE-2371) ODBC driver does not return any data with SQLColumns and SQLTables calls.

Igor Sapego created IGNITE-2371: --- Summary: ODBC driver does not return any data with SQLColumns and SQLTables calls. Key: IGNITE-2371 URL: https://issues.apache.org/jira/browse/IGNITE-2371 Project:

MS VS 2010 for platforms

Hi Igniters I found that build of platforms (both .Ner and C++) requires Visual Studio 2010 Professional. Could someone explain: - Why we do not suggest to use Visual Studio Community? - VS 2010 seems a bit outdated.What's about VS 2015? -- Sergey Kozlov

Re: MS VS 2010 for platforms

Hi Sergey, You can build C++/.NET with any VS (2010+), you just have to click "upgrade VC++ compilers" on C++ projects. I use VS2015 Community, everything works just fine. Why do we support .NET 4 / VS2010? The lower the better. Some companies have weird software policies, so we have wider

[GitHub] ignite pull request: IGNITE-2324 .NET: Code analysis

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/400 IGNITE-2324 .NET: Code analysis You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-2324 Alternatively you can review

[jira] [Created] (IGNITE-2372) GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail sometimes

Artem Shutak created IGNITE-2372: Summary: GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail sometimes Key: IGNITE-2372 URL: https://issues.apache.org/jira/browse/IGNITE-2372

Re: MS VS 2010 for platforms

I would say that it is good that we cannot use 6.0 features even if we want so. Otherwise users with earlier versions will not be able to build the product from sources. 13 янв. 2016 г. 14:01 пользователь "Pavel Tupitsyn" написал: > Hi Sergey, > > You can build C++/.NET

about AtomicConfiguration

Hi： About AtomicConfiguration, I found the following issue: Configuration of node 1: AtomicConfiguration atomicCfg = new AtomicConfiguration(); atomicCfg.setBackups(1); atomicCfg.setAtomicSequenceReserveSize(0); IgniteConfiguration cfg = new IgniteConfiguration();

New method in IgniteCache API.

Igniters! Since we are going to add stronger data loss check IGNITE-1605 I'm about to add new method for the manual resetting state of the lost partition in IgniteCache IgniteFuture *resetLostPartitions*(); just near #rebalance(). And would

Re: Why Ignite JIRA shows 1.5 as unreleased?

I have released 1.5 in Jira. Agree, we should be disciplined to do this right after release. Is the post-release check list on the Wiki? On Wed, Jan 13, 2016 at 8:05 AM, Alexey Kuznetsov wrote: > Why Ignite JIRA shows 1.5 as unreleased version? > > Who could update

Re: New method in IgniteCache API.

Of course! 1. Yes, it is a part of the task. Documentation is about to be placed at readmeIo under 1.6 version. 2. No, but both those calls are near in the GridDhtTopologyExchangeFuture#validateCache. 3. Yes, sure. As far as I understand, main purpose of the IGNITE-1605

Re: New method in IgniteCache API.

Hello, How often will end users invoke this functionality? It sounds somewhat like an administrative function. If it won't be invoked frequently, and its function is not on par with get(), put(), etc., I would propose to add the method to IgniteCacheEx instead, to avoid excessively polluting

Re: New method in IgniteCache API.

I am still not sure why this is not a Topology Validator with more context. Why do we need to add yet another concept here? On Wed, Jan 13, 2016 at 12:28 PM, Vladimir Ershov wrote: > Of course! > > 1. Yes, it is a part of the task. Documentation is about to be placed at >

Re: about AtomicConfiguration

Hi, This behavior is correct and unfortunately your suggestion is not going to work. We create only one cache for all atomic structures, so you can't pass new configuration for each created atomic. It makes perfect sense to define all parameters that are not specific for a particular atomic

Binary ID mapper that uses a simple name of classes.

Igniters, I'm working on https://issues.apache.org/jira/browse/IGNITE-2191 (Binary marshaller: support user classes with the same simple name) bug. The fix expects new BinaryIdMapper that uses a simple name of classes. It is required for supporting of platforms (.Net. C++). I would be glade to

Why Ignite JIRA shows 1.5 as unreleased?

Why Ignite JIRA shows 1.5 as unreleased version? Who could update JIRA? Also, it seems we should add this step into our post-release checklist. -- Alexey Kuznetsov GridGain Systems www.gridgain.com

[jira] [Created] (IGNITE-2373) Revisit server side error handling logic

Alexey Kuznetsov created IGNITE-2373: Summary: Revisit server side error handling logic Key: IGNITE-2373 URL: https://issues.apache.org/jira/browse/IGNITE-2373 Project: Ignite Issue

[GitHub] ignite pull request: TESTING BRANCH, DO NOT MERGE Ignite 2343 temp...

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/401 TESTING BRANCH, DO NOT MERGE Ignite 2343 temp do not merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite

Re: Jira Process Change

On Wed, Jan 13, 2016 at 2:46 AM, Yakov Zhdanov wrote: > Cos and all, > > I changed column title to "Maintainer". This fits better. > > Now we need to agree on release manager for 1.6. I think I can do it for > 1.6, then we can try rotating between PMCs. > I think, any

Re: New method in IgniteCache API.

Vladimir, Can you please describe what this method will be doing? I am note sure I understand what resetting state of the lost partition means. D. On Wed, Jan 13, 2016 at 5:23 AM, Vladimir Ershov wrote: > Igniters! > > Since we are going to add stronger data loss check

Re: New method in IgniteCache API.

Dmitriy, I've added new GridDhtPartitionState.LOST state for partitions that were lost, and also new CacheConfiguration property - DataLossPolicy. If DataLossPolicy is FAIL_OPS, then all lost partitions get LOST state, and all actions for any keys on those lost partitions throw exception, until