Re: query configuration design

Dmitriy, May be it makes sense to put the final design on the main page from comments? Sergi 2015-10-26 12:41 GMT+03:00 Dmitriy Setrakyan : > Igniters, > > I want to point out that there is an active discussion going on about query > configuration design here: > > >

Re: Remote job execution in C++

Job load without cluster restart is advanced feature. I think we should make basic API work first. On Mon, Oct 26, 2015 at 12:16 PM, Yakov Zhdanov wrote: > I think suggested approach should work. > > Any idea on how to add dynamic jobs loading (I would like it is added in >

[jira] [Created] (IGNITE-1787) Concurrent call of Cache.registerCacheEntryListener can fail with ConcurrentModificationException

Semen Boikov created IGNITE-1787: Summary: Concurrent call of Cache.registerCacheEntryListener can fail with ConcurrentModificationException Key: IGNITE-1787 URL: https://issues.apache.org/jira/browse/IGNITE-1787

[Ignite-429] facing problem with node startup

Hi igniters, i am starting two ignite node with same config file(Ignition.start("config/default-config.xml");). One node i am starting in onStart Method of test and another is in my streamer which close every time. So one node is always up and another is start-stop. By doing this i am getting

Re: Ignite vs Hazelcast

Thanks, Chandresh, for pointing this out. We also have benchmark results, which look very different: https://ignite.apache.org/benchmarks/ignite-vs-hazelcast.html The main issue here, is that the shown results are for HZ 3.6, which has not been released yet. I suspect that they have done some

query configuration design

Igniters, I want to point out that there is an active discussion going on about query configuration design here: https://cwiki.apache.org/confluence/display/IGNITE/Extendable+TypeConfiguration It gets a bit tricky to follow, so make sure to read the latest comments towards the end. D.

Re: query configuration design

On Mon, Oct 26, 2015 at 2:56 AM, Sergi Vladykin wrote: > Dmitriy, > > May be it makes sense to put the final design on the main page from > comments? > Good point. I have added a page for the final query entity design here:

Re: Hello

Hi Chokha, Please send an email to dev-subscr...@ignite.apache.org and follow the instructions in the reply. D. On Sat, Oct 24, 2015 at 9:00 PM, Chokha Palayamkottai < cho...@integralops.com> wrote: > Please subscribe me to this list. > > Thanks, > Chokha. >

Re: Ignite vs Hazelcast

My team uses Hazelcast for in memory data grid. i am also wanted to do comparison with ignite and publish result sometime in next month. On Mon, Oct 26, 2015 at 8:59 AM, Konstantin Boudnik wrote: > On Sun, Oct 25, 2015 at 07:36PM, Kostya Kulagin wrote: > > Was this in or off

[jira] [Created] (IGNITE-1788) Duplicate check of IGFS configuration

Vasiliy Sisko created IGNITE-1788: - Summary: Duplicate check of IGFS configuration Key: IGNITE-1788 URL: https://issues.apache.org/jira/browse/IGNITE-1788 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request: Ignite 1777

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

WebSockets with Apache Ignite

Hey guys, I'd like to gauge the interest in the community for a WebSockets client for Apache Ignite. Such a client would allow users to build browser-based real-time enterprise apps that interact with Apache Ignite directly, omitting the middleware for simple use cases. Browsers would be able to

Re: WebSockets with Apache Ignite

Raul, I think this is a great idea. I wonder if this can be covered by Ignite providing Node.js integration. To my knowledge, the work was started, but somehow got put on hold. I think Irina V. got started on it at some point. https://issues.apache.org/jira/browse/IGNITE-961 Perhaps we could

Re: [Ignite-429] facing problem with node startup

On Mon, Oct 26, 2015 at 9:23 AM, Saikat Maitra wrote: > Hi > > Quick questions on the node startup. > > 1. What is the port defined in default-config.xml ? > I believe that the default discovery port is 47500. You can specify a different port if you like. > 2. if a

Re: Data Snapshots in Ignite

On Mon, Oct 26, 2015 at 5:31 AM, Raul Kripalani wrote: > Hi, > > Thanks all for chiming in. It seems like this feature could be of interest > to the user community, so I've opened a ticket to continue maturing the > idea there: > >

[jira] [Created] (IGNITE-1789) Data Snapshots for Ignite caches

Raúl Kripalani created IGNITE-1789: -- Summary: Data Snapshots for Ignite caches Key: IGNITE-1789 URL: https://issues.apache.org/jira/browse/IGNITE-1789 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-1790) Implement an Apache Camel Data Streamer

Raúl Kripalani created IGNITE-1790: -- Summary: Implement an Apache Camel Data Streamer Key: IGNITE-1790 URL: https://issues.apache.org/jira/browse/IGNITE-1790 Project: Ignite Issue Type: New

Re: Account @ TeamCity, please

Ok, got it. But now I need to add new projects for JMS, MQTT, ZooKeeper with their corresponding test suites. Could someone please give me the admin role? Thanks, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer

Re: Account @ TeamCity, please

Done! Pay attention all Ignite builds based on "Maven" template. Please, base your new builds on the template too. Also, it's good idea to add new builds in "-> Run All" build as dependent builds. -- Artem -- On Mon, Oct 26, 2015 at 3:43 PM, Raul Kripalani wrote: > raulk > >

Questions about TeamCity CI organization

Hey guys, I have a few questions about the way our builds are organised in TeamCity. 1. All build configurations seem to be building the entire project tree. Is this correct? 2. The goal of the build configurations here is to partition the tests so that the test execution can be distributed

Re: Data Snapshots in Ignite

Hi, Thanks all for chiming in. It seems like this feature could be of interest to the user community, so I've opened a ticket to continue maturing the idea there: https://issues.apache.org/jira/browse/IGNITE-1789 We may need to create a Wiki page later to collaborate around specifics and

Re: query configuration design

Igniters, I added to https://cwiki.apache.org/confluence/display/IGNITE/Final+Query+Entity+Design final persistence design. Actually I've already implemented it in ignite-1753-1282 branch. Tests with POJOs passed. Now I'm working on tests with portables and backward compatibility. On Mon, Oct

[jira] [Created] (IGNITE-1793) [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes

Artem Shutak created IGNITE-1793: Summary: [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes Key: IGNITE-1793 URL: https://issues.apache.org/jira/browse/IGNITE-1793

[jira] [Created] (IGNITE-1792) ContinuousProcessor should use ALWAYS_TRUE predicate instead of null

Andrey Gura created IGNITE-1792: --- Summary: ContinuousProcessor should use ALWAYS_TRUE predicate instead of null Key: IGNITE-1792 URL: https://issues.apache.org/jira/browse/IGNITE-1792 Project: Ignite

Re: Remote job execution in C++

Agree, I am talking about some future releases. --Yakov 2015-10-26 14:06 GMT+03:00 Vladimir Ozerov : > Job load without cluster restart is advanced feature. I think we should > make basic API work first. > > On Mon, Oct 26, 2015 at 12:16 PM, Yakov Zhdanov

Re: [Ignite-429] facing problem with node startup

Hi Quick questions on the node startup. 1. What is the port defined in default-config.xml ? 2. if a listener is already running on that port then will the second node will automatically detect and start on another port? Regards Saikat On Mon, Oct 26, 2015 at 7:13 PM, Artem Shutak

[jira] [Created] (IGNITE-1794) Ignite should support Hibernate 5

Artem Shutak created IGNITE-1794: Summary: Ignite should support Hibernate 5 Key: IGNITE-1794 URL: https://issues.apache.org/jira/browse/IGNITE-1794 Project: Ignite Issue Type: Test