Re: [VOTE] Apache Ignite 2.1.0 RC3

Anton V, Would you mind closing the vote if it passes? Unfortunately, I won't do this, going offline for significant time. Denis On Friday, July 21, 2017, Semyon Boikov wrote: > +1 binding > > On Fri, Jul 21, 2017 at 1:09 PM, Yakov Zhdanov

[GitHub] ignite pull request #699: ignite-3098

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

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

Maxim, The issue is that it's currently assumed to support job mapping, but it actually doesn't. However, I agree that AffinityKeyMapped annotation doesn't fit the use case well. Let's fix documentation and JavaDoc then. As for the proposed API, it's overcomplicated, took me 15 minutes to

Re: SSL certificate for the CI server

I have never heard about this provider, and it is great they are donating their resources to the FOSS. I quick glance on their site has reveiled a couple of issues: - the page for the "Standard Agreement" returns 404 [1]. I won't be willing to agree to something I cannot read upfront. - the

Re: Timeouts in atomic cache

Any thoughts? -Val On Wed, Jul 19, 2017 at 4:21 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Folks, > > Do we currently have any way to set a timeout for an atomic operation? I > don't see neither a way to do this nor any related documentation. > > In the code there are

Re: "not null" constraint support

Guys, QueryEntity is already too complex. We will deprecate it soon in favor of brand new SQL API. No need to design FieldConstraint or something similar at the moment, let's just stick to "Set notNullFields". On Fri, Jul 21, 2017 at 7:08 PM, Sergey Chugunov wrote: >

Re: Ignite internal events tracing

Alex, That's a great idea. I would also add an option to dump information on demand, for case when operation hanged and can't complete. -Val On Fri, Jul 21, 2017 at 6:15 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Igniters, > > I've recently stumbled across a situation when

[GitHub] ignite pull request #2337: IGNITE-GG-12512 Introduced explicit ordering of c...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/2337 IGNITE-GG-12512 Introduced explicit ordering of caches start & stop. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: "not null" constraint support

Sergey, It may be a good idea to distinguish between field constraints (like "not null" one) which can be applied to only one field; and more complex constraints that involves more than one field. In case of field constraints it is better to simplify our model and allow only one field to appear

[GitHub] ignite pull request #2336: IGNITE-5770 Refactor PlatformProcessor to Platfor...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2336 IGNITE-5770 Refactor PlatformProcessor to PlatformTarget mechanism You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

Re: "not null" constraint support

Sergey, looks good to me! I thought of something a bit different, where there is a base class and each constraint type inherits it, but your design is actually better. Pavel On Fri, Jul 21, 2017 at 6:38 PM, Sergey Kalashnikov wrote: > Hi Pavel, > > Good point! What if

Re: "not null" constraint support

Hi Pavel, Good point! What if we make it the following way? class QueryEntity { ... /** All constraints to be enforced on this QueryEntity. */ Set constraint; } /** Describes constraints that affect one or more fields. */ class QueryConstraint { /** Names of fields to be

Re: [VOTE] Apache Ignite 2.1.0 RC3

+1 binding On Fri, Jul 21, 2017 at 1:09 PM, Yakov Zhdanov wrote: > +1 binding > > Checked maven build, imported and built examples project in IDEA and run > several compute exampled and started 2 nodes with default config. > > --Yakov > > 2017-07-21 12:21 GMT+03:00 Anton

[GitHub] ignite pull request #2335: IGNITE-5806: removed assertion failing Ignite Cac...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2335 IGNITE-5806: removed assertion failing Ignite Cache 5 suite You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2334: IGNITE-5712: implementation of context switching ...

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/2334 IGNITE-5712: implementation of context switching for transactions. You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite

[GitHub] ignite pull request #2297: IGNITE-5752 Fixed GridDhtPartitionMap updateSeque...

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

[GitHub] ignite pull request #2313: IGNITE-5772

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

[GitHub] ignite pull request #2331: IGNITE-5786 .NET: Fix cache store session handlin...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2331 --- 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-5806) IgniteCache5 suite timed out, assertions in sessions close logic

Dmitriy Pavlov created IGNITE-5806: -- Summary: IgniteCache5 suite timed out, assertions in sessions close logic Key: IGNITE-5806 URL: https://issues.apache.org/jira/browse/IGNITE-5806 Project: Ignite

[GitHub] ignite pull request #2333: ignite-4181

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/2333 ignite-4181 You can merge this pull request into a Git repository by running: $ git pull https://github.com/x-kreator/ignite ignite-4181 Alternatively you can review and apply these

[GitHub] ignite pull request #2332: Ignite 1094

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2332 Ignite 1094 You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-1094 Alternatively you can review and apply these changes as

[GitHub] ignite pull request #2325: ignite-4181

Github user x-kreator closed the pull request at: https://github.com/apache/ignite/pull/2325 --- 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

Re: Cache start ordering during cluster activation

Agree, Since we rely on cache start order during the node start, the same order should be preserved during activation. 2017-07-21 15:24 GMT+03:00 Jokser : > Hello Igniters, > > Currently order of cache starts/stops operations is not determined during > cluster activation. >

Ignite internal events tracing

Igniters, I've recently stumbled across a situation when occasionally Ignite transactions commit may take up to several seconds while in general most of the transactions completed in a period of milliseconds. After a few attempts to analyze this situation with logs, I realized that this is a

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

Valentin, The author of tiket wants to see to provide some API allows to map ComputeJobs to partitions or keys. If we use @AffinityKeyMapped then you need to enter the cache name parameter, I think this is not convenient for the user. Therefore, I propose to extend the existing API. Having

Cache start ordering during cluster activation

Hello Igniters, Currently order of cache starts/stops operations is not determined during cluster activation. Some of the cache components can be depended on system or utility caches. If such component starts earlier than system cache on what it's depended, it can lead to unpredictable errors

[jira] [Created] (IGNITE-5804) ScanQuery transformer applies to first results page only.

Andrew Mashenkov created IGNITE-5804: Summary: ScanQuery transformer applies to first results page only. Key: IGNITE-5804 URL: https://issues.apache.org/jira/browse/IGNITE-5804 Project: Ignite

[GitHub] ignite pull request #2326: Ignite-5791: Block matrix introduction

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

[GitHub] ignite pull request #2331: IGNITE-5786 .NET: Fix cache store session handlin...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2331 IGNITE-5786 .NET: Fix cache store session handling for cross-cache transactions You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-5803) IgniteCacheTestSuite4: IgniteCacheInvokeReadThroughTest: 6 test failed, stable reproducible locally

Dmitriy Pavlov created IGNITE-5803: -- Summary: IgniteCacheTestSuite4: IgniteCacheInvokeReadThroughTest: 6 test failed, stable reproducible locally Key: IGNITE-5803 URL:

[jira] [Created] (IGNITE-5802) Fix all wrong TODO comments in component

Yury Babak created IGNITE-5802: -- Summary: Fix all wrong TODO comments in component Key: IGNITE-5802 URL: https://issues.apache.org/jira/browse/IGNITE-5802 Project: Ignite Issue Type: Bug

Re: Make Teamcity Green Again

> Green Again > Again As if it ever was green :) Of course +1 on this, let me know if you see any .NET-related failures. On Fri, Jul 21, 2017 at 1:06 PM, Николай Ижиков wrote: > Hello, Igniters. > > Also ready to help to #MakeTeamcityGreenAgain ! > > 21 июля 2017 г.

[jira] [Created] (IGNITE-5801) Externalization for offheap vectors/matrices

Yury Babak created IGNITE-5801: -- Summary: Externalization for offheap vectors/matrices Key: IGNITE-5801 URL: https://issues.apache.org/jira/browse/IGNITE-5801 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5800) Umbrella ticket for making Teamcity Green Again

Dmitriy Pavlov created IGNITE-5800: -- Summary: Umbrella ticket for making Teamcity Green Again Key: IGNITE-5800 URL: https://issues.apache.org/jira/browse/IGNITE-5800 Project: Ignite Issue

[jira] [Created] (IGNITE-5799) Caching for some intermediate calcs

Yury Babak created IGNITE-5799: -- Summary: Caching for some intermediate calcs Key: IGNITE-5799 URL: https://issues.apache.org/jira/browse/IGNITE-5799 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-5798) Logging Ignite configuration at startup

Alexandr Kuramshin created IGNITE-5798: -- Summary: Logging Ignite configuration at startup Key: IGNITE-5798 URL: https://issues.apache.org/jira/browse/IGNITE-5798 Project: Ignite Issue

Re: [VOTE] Apache Ignite 2.1.0 RC3

+1 binding Checked maven build, imported and built examples project in IDEA and run several compute exampled and started 2 nodes with default config. --Yakov 2017-07-21 12:21 GMT+03:00 Anton Vinogradov : > +1 (binding) > > On Fri, Jul 21, 2017 at 12:08 PM, Pavel

Re: Make Teamcity Green Again

Hello, Igniters. Also ready to help to #MakeTeamcityGreenAgain ! 21 июля 2017 г. 12:56 PM пользователь "Vyacheslav Daradur" < daradu...@gmail.com> написал: > Hi guys. > > I vote for #MakeTeamcityGreenAgain. :-) > > FYI: it had been described and supported previously[1] > > After the completion

Re: Fix for enum marshalling

Hi Nikita. Thanks for the contribution! If you are curious in BinaryMarshaler and want to continue improve it, please, take a look to a task [1] [1] https://issues.apache.org/jira/browse/IGNITE-3244 2017-07-21 12:53 GMT+03:00 Nikita Amelchev : > Hi, Igniters. > I fixed

Re: Make Teamcity Green Again

Hi guys. I vote for #MakeTeamcityGreenAgain. :-) FYI: it had been described and supported previously[1] After the completion of my current task I will try to help with this activity. [1] http://apache-ignite-developers.2346864.n4.nabble.com/Test-failures-td14353.html 2017-07-21 12:39

Fix for enum marshalling

Hi, Igniters. I fixed issue 5087 - Enum comparison fails after marshal-unmarshal with BinaryMarshaller. The solution is check superclass on enum. I created new public method isEnum(Class cls) for resolve enum mode in binary class descriptor. Also I get class name through getDeclaringClass() for

Re: Make Teamcity Green Again

Nikolay, That's also a big problem for me, as reviewer, to accept changes and merge them to master. Dmitriy, Currently we have some contributions *from community* blocked by red Teamcity. On Fri, Jul 21, 2017 at 12:47 AM, Nikolay Izhikov wrote: > +1 to Dmitry Pavlov

Re: [VOTE] Apache Ignite 2.1.0 RC3

+1 (binding) On Fri, Jul 21, 2017 at 12:08 PM, Pavel Tupitsyn wrote: > +1 > > Checked .NET: nodes start and join from exe file, bat file, NuGet, user > project. > > On Fri, Jul 21, 2017 at 11:49 AM, Vyacheslav Daradur > wrote: > > > +1 > > > > Build

Re: [VOTE] Apache Ignite 2.1.0 RC3

+1 Checked .NET: nodes start and join from exe file, bat file, NuGet, user project. On Fri, Jul 21, 2017 at 11:49 AM, Vyacheslav Daradur wrote: > +1 > > Build success now. Node starts without issues. > > 2017-07-21 11:38 GMT+03:00 Kozlov Maxim : > > >

Re: [VOTE] Apache Ignite 2.1.0 RC3

+1 Build success now. Node starts without issues. 2017-07-21 11:38 GMT+03:00 Kozlov Maxim : > +1 > > > 21 июля 2017 г., в 7:48, Valentin Kulichenko < > valentin.kuliche...@gmail.com> написал(а): > > > > +1 (binding) > > > > On Thu, Jul 20, 2017 at 9:35 PM, Sasha Belyak

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, >>> >>>

[jira] [Created] (IGNITE-5797) Add latency tracing capability for cache operations

Alexey Goncharuk created IGNITE-5797: Summary: Add latency tracing capability for cache operations Key: IGNITE-5797 URL: https://issues.apache.org/jira/browse/IGNITE-5797 Project: Ignite

Re: "not null" constraint support

Hi Sergey, This one looks not very good to me: > class QueryEntity { > ... > Set notNullFields; > } What if there are more constraints in future? UNIQUE, CHECK, etc etc? Instead we could do something like Set constraints; Which is easily extendable in future. Thoughts? Pavel