Re: Ignite 1.4

2015-09-04 Thread Vladimir Ozerov
Please disregard p.2 and p.3 as they are out of Ignite scope. On Fri, Sep 4, 2015 at 3:23 PM, Vladimir Ozerov wrote: > Done. > 1) No changes from my side to Ignite. > 2) Added missing enterprise release notes for 7.3.3. > 3) Updated enterprise release notes for 7.4.1. > >

[GitHub] ignite pull request: IGNITE-1361: PingPong example fixed

2015-09-04 Thread ashutakGG
Github user ashutakGG closed the pull request at: https://github.com/apache/ignite/pull/61 --- 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: Ignite 1.4

2015-09-04 Thread Yakov Zhdanov
Of course, we will release ignite-1.4.0. Anton V, can you please fix? --Yakov 2015-09-04 12:50 GMT+03:00 Sergey Kozlov : > Igniters, > > Current version in released branch is 1.4.1 (there were issues related to > update notifier but it fixed now). Make sense to change to

Re: Ignite 1.4

2015-09-04 Thread Vladimir Ozerov
Done. 1) No changes from my side to Ignite. 2) Added missing enterprise release notes for 7.3.3. 3) Updated enterprise release notes for 7.4.1. On Fri, Sep 4, 2015 at 2:46 PM, Yakov Zhdanov wrote: > Guys, I have updated release notes (IGNITE_HOME/RELEASE_NOTES.txt). I think

[jira] [Created] (IGNITE-1374) Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration

2015-09-04 Thread Enrico Olivelli (JIRA)
Enrico Olivelli created IGNITE-1374: --- Summary: Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration Key: IGNITE-1374 URL:

Re: Ignite 1.4

2015-09-04 Thread Sergey Kozlov
Igniters, Current version in released branch is 1.4.1 (there were issues related to update notifier but it fixed now). Make sense to change to 1.4.0? On Fri, Sep 4, 2015 at 12:05 PM, Yakov Zhdanov wrote: > Guys, > > We need to postpone release due to TC state. I think it

[jira] [Created] (IGNITE-1375) Move CPP tests for "src/test" folder.

2015-09-04 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-1375: --- Summary: Move CPP tests for "src/test" folder. Key: IGNITE-1375 URL: https://issues.apache.org/jira/browse/IGNITE-1375 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-1378) Continuous processor doesn't remove message listener if continuous query failed to start

2015-09-04 Thread Valentin Kulichenko (JIRA)
Valentin Kulichenko created IGNITE-1378: --- Summary: Continuous processor doesn't remove message listener if continuous query failed to start Key: IGNITE-1378 URL:

Re: QueryProcessor and CacheProcessor start order

2015-09-04 Thread Sergi Vladykin
Agree, lets keep your fix then. Sergi 2015-09-04 9:05 GMT+03:00 Semyon Boikov : > Yes, I tried this fix, TC results are good. I run queries suite 5 times and > don't see anymore failuers in queries restarts tests. > > I agree that it does not fix issue with Cache.destroy,

Re: QueryProcessor and CacheProcessor start order

2015-09-04 Thread Semyon Boikov
Yes, I tried this fix, TC results are good. I run queries suite 5 times and don't see anymore failuers in queries restarts tests. I agree that it does not fix issue with Cache.destroy, but IMO it is not critical and I don't want to spend time on this now. On Thu, Sep 3, 2015 at 10:47 PM, Sergi

[GitHub] ignite pull request: IGNITE-1333 - fixed

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