New README.md for Github

Ladies and gents, While I was adding the Gitter badge I realised we don't have a nice README.md. So I created one. Let me know what you think: https://github.com/apache/ignite Regards, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging

Add H2 datasource bean in example-default.xml

Guys, While working on [https://issues.apache.org/jira/browse/IGNITE-2041] I found that we use deprecated code in JDBC cache store examples. Correct way to configure JDBC cache store is to use CacheJdbcPojoStoreFactory + specify dataSource bean name. So I would like to add following bean into

Re: New README.md for Github

Very nice! On Wed, Dec 2, 2015 at 7:07 AM, Alexey Kuznetsov wrote: > Looks really cool now. > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com >

Re: New README.md for Github

Looks really cool now. -- Alexey Kuznetsov GridGain Systems www.gridgain.com

Re: [VOTE] Apache Ignite 1.5.0-b1

Would be nice to specify binding vs. non-binding when voting. On Wed, Dec 2, 2015 at 5:32 AM, Sergi Vladykin wrote: > +1 > > Sergi > > 2015-12-02 16:30 GMT+03:00 Denis Magda : > > > +1 > > > > > > On 12/2/2015 3:16 PM, Yakov Zhdanov wrote: > > > >>

[jira] [Created] (IGNITE-2065) Need to get rid of 'Portable' word in internals

Alexey Goncharuk created IGNITE-2065: Summary: Need to get rid of 'Portable' word in internals Key: IGNITE-2065 URL: https://issues.apache.org/jira/browse/IGNITE-2065 Project: Ignite

Re: Disabling patch-validation mechanism on TC

Thanks, Denis! Disabled patch-based approach on TC. -- Artem -- On Tue, Dec 1, 2015 at 9:23 PM, Denis Magda wrote: > Removed patch-based information from the site. Placed a direct link to > wiki that describes how to contribute using pull-requests instead. > > — > Denis >

[jira] [Created] (IGNITE-2052) Need move $generatorXml to services

Dmitriyff created IGNITE-2052: - Summary: Need move $generatorXml to services Key: IGNITE-2052 URL: https://issues.apache.org/jira/browse/IGNITE-2052 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2054) need move $generatorJava to services

Dmitriyff created IGNITE-2054: - Summary: need move $generatorJava to services Key: IGNITE-2054 URL: https://issues.apache.org/jira/browse/IGNITE-2054 Project: Ignite Issue Type: Sub-task

hanging locks

Igniters, Does anyone know the severity of this issue? In which cases is it reproduced? https://issues.apache.org/jira/browse/IGNITE-2008 In my view, we already have support for it, so it should be just a bug. Anyone knows how hard it is to fix? D.

[jira] [Created] (IGNITE-2070) "Back to Clusters" link doesn't work on Security page

Pavel Konstantinov created IGNITE-2070: -- Summary: "Back to Clusters" link doesn't work on Security page Key: IGNITE-2070 URL: https://issues.apache.org/jira/browse/IGNITE-2070 Project: Ignite

[jira] [Created] (IGNITE-2068) Generation of separate metod for each metadata

Vasiliy Sisko created IGNITE-2068: - Summary: Generation of separate metod for each metadata Key: IGNITE-2068 URL: https://issues.apache.org/jira/browse/IGNITE-2068 Project: Ignite Issue

Re: [VOTE] Apache Ignite 1.5.0-b1

+1 On Wednesday, December 2, 2015 9:16 PM, Yakov Zhdanov wrote: Dear Sirs! We have uploaded release candidate to https://dist.apache.org/repos/dist/dev/ignite/1.5.0-b1-rc1/ This is very important release containing initial versions of Ignite.NET and Ignite C++ and many

Re: hanging locks

Thanks Semyon! On Wed, Dec 2, 2015 at 10:13 PM, Semyon Boikov wrote: > Dmitry, Valentin, > > I'll look at this issue today. > > On Thu, Dec 3, 2015 at 6:26 AM, Dmitriy Setrakyan > wrote: > > > Val, > > > > I think if lock futures are not complete,

Re: hanging locks

Val, I think if lock futures are not complete, then the issue remains, because it can cause hanging clients. Did you get an idea of what it would take to fix it? D. On Wed, Dec 2, 2015 at 7:25 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > I played with this and it seems

EntryProcessor invoked twice

Igniters, I noticed that when I execute cache.invoke() in transactional cache, it's invoked twice for the same old value on the primary node. First invocation is done on prepare step [1], the second one happens on commit [2]. Is this expected behavior? Why can't we reuse already calculated new

GridCacheIoManager.processFailedMessage() method

Igniters, Can someone please explain the purpose of GridCacheIoManager.processFailedMessage() method? I've already seen several reports on user@ about "Unsupported direct type" exception thrown from this method and each time we just add processing for one more message. In my opinion this

[jira] [Created] (IGNITE-2071) Download button on sammary page placed into wrong block

Pavel Konstantinov created IGNITE-2071: -- Summary: Download button on sammary page placed into wrong block Key: IGNITE-2071 URL: https://issues.apache.org/jira/browse/IGNITE-2071 Project: Ignite

Re: [ANNOUNCE] Apache Ignite official chatroom

Raul, Thanks a lot, gitter is great! It seems that the Ignite fork in GIT is not automatically updated. Specifically, your pretty Readme.md is not showing. Any ideas how to fix? D. On Wed, Dec 2, 2015 at 3:44 PM, Raul Kripalani wrote: > Hello users, Hello team! > > The

[jira] [Created] (IGNITE-2067) fix minimize build version

Dmitriyff created IGNITE-2067: - Summary: fix minimize build version Key: IGNITE-2067 URL: https://issues.apache.org/jira/browse/IGNITE-2067 Project: Ignite Issue Type: Sub-task

[GitHub] ignite pull request: IGNITE-2067 fixed minimize version, logout me...

GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/287 IGNITE-2067 fixed minimize version, logout method You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite ignite-2067 Alternatively

[jira] [Created] (IGNITE-2069) Top menu has no Gridgain item and sub-items

Pavel Konstantinov created IGNITE-2069: -- Summary: Top menu has no Gridgain item and sub-items Key: IGNITE-2069 URL: https://issues.apache.org/jira/browse/IGNITE-2069 Project: Ignite

[ANNOUNCE] Apache Ignite official chatroom

Hello users, Hello team! The Apache Ignite PMC is pleased to announce that the project now has an official chatroom on Gitter: https://gitter.im/apacheignite/ignite. Come join us there! All you need is a Github account. We've updated the Ignite website accordingly:

[ANNOUNCE] Apache Ignite official chatroom

Hello users, Hello team! The Apache Ignite PMC is pleased to announce that the project now has an official chatroom on Gitter: https://gitter.im/apacheignite/ignite. Come join us there! All you need is a Github account. We've updated the Ignite website accordingly:

[jira] [Created] (IGNITE-2056) Chart settings does not open by clicking on button with arrow

Pavel Konstantinov created IGNITE-2056: -- Summary: Chart settings does not open by clicking on button with arrow Key: IGNITE-2056 URL: https://issues.apache.org/jira/browse/IGNITE-2056 Project:

[jira] [Created] (IGNITE-2055) Implement ability to select version

Dmitriyff created IGNITE-2055: - Summary: Implement ability to select version Key: IGNITE-2055 URL: https://issues.apache.org/jira/browse/IGNITE-2055 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2058) need move $generatorDocker to services

Dmitriyff created IGNITE-2058: - Summary: need move $generatorDocker to services Key: IGNITE-2058 URL: https://issues.apache.org/jira/browse/IGNITE-2058 Project: Ignite Issue Type: Sub-task

Re: Ignite chat room

Here is the link: https://gitter.im/apacheignite/ignite#notifications --Yakov 2015-12-02 12:54 GMT+03:00 Yakov Zhdanov : > Raul, > > I think you created a chat room, but I cannot find anything for "glitter" > in my mailbox. Can you please advice and/or add chat room info

Re: [VOTE] Apache Ignite 1.5.0-b1

+1 On Wed, Dec 2, 2015 at 3:21 PM, Anton Vinogradov wrote: > +1 > > On Wed, Dec 2, 2015 at 3:16 PM, Yakov Zhdanov wrote: > > > Dear Sirs! > > > > We have uploaded release candidate to > > https://dist.apache.org/repos/dist/dev/ignite/1.5.0-b1-rc1/

[GitHub] ignite pull request: IGNITE-843-rc2 update gulp tasks, chage docum...

GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/285 IGNITE-843-rc2 update gulp tasks, chage documentation to run console You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite

[GitHub] ignite pull request: IGNITE-1692 Test Suite for DataStreamProcesso...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/286 IGNITE-1692 Test Suite for DataStreamProcessorSelfTest.testReplicated. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite 1692

Re: [VOTE] Apache Ignite 1.5.0-b1

+1 On Wed, Dec 2, 2015 at 3:16 PM, Yakov Zhdanov wrote: > Dear Sirs! > > We have uploaded release candidate to > https://dist.apache.org/repos/dist/dev/ignite/1.5.0-b1-rc1/ > > This is very important release containing initial versions of Ignite.NET > and Ignite C++ and

Re: [VOTE] Apache Ignite 1.5.0-b1

+1 Sergi 2015-12-02 16:30 GMT+03:00 Denis Magda : > +1 > > > On 12/2/2015 3:16 PM, Yakov Zhdanov wrote: > >> Dear Sirs! >> >> We have uploaded release candidate to >> https://dist.apache.org/repos/dist/dev/ignite/1.5.0-b1-rc1/ >> >> This is very important release containing

Re: [VOTE] Apache Ignite 1.5.0-b1

+1 Raúl. On Wed, Dec 2, 2015 at 12:16 PM, Yakov Zhdanov wrote: > Dear Sirs! > > We have uploaded release candidate to > https://dist.apache.org/repos/dist/dev/ignite/1.5.0-b1-rc1/ > > This is very important release containing initial versions of Ignite.NET > and Ignite C++

[jira] [Created] (IGNITE-2061) CPP: Implement obtaining of diagnostic information for ODBC driver.

Igor Sapego created IGNITE-2061: --- Summary: CPP: Implement obtaining of diagnostic information for ODBC driver. Key: IGNITE-2061 URL: https://issues.apache.org/jira/browse/IGNITE-2061 Project: Ignite

Re: [VOTE] Apache Ignite 1.5.0-b1

+1 -- Alexey Kuznetsov GridGain Systems www.gridgain.com

[jira] [Created] (IGNITE-2062) CPP: Implement support of Linux OS family for the ODBC driver.

Igor Sapego created IGNITE-2062: --- Summary: CPP: Implement support of Linux OS family for the ODBC driver. Key: IGNITE-2062 URL: https://issues.apache.org/jira/browse/IGNITE-2062 Project: Ignite

Re: OSGi integration ready for review

Guys, Should we try to review and merge the OSGI integration before the final release? it does sound like it is additive and should not affect other functionality. My preference would be to get it in, so other OSGI-related integrations (e.g. Camel) would not have to wait for 1.6. Thoughts? D.

[jira] [Created] (IGNITE-2066) Clean build process, add needed comments

Dmitriyff created IGNITE-2066: - Summary: Clean build process, add needed comments Key: IGNITE-2066 URL: https://issues.apache.org/jira/browse/IGNITE-2066 Project: Ignite Issue Type: Sub-task