Re: Ignite-1.5 Release

s/com/hazelcast/hazelcast/3.6-EA/ > > > > > > On Mon, Nov 30, 2015 at 9:39 PM, Raul Kripalani > wrote: > > > > > On Mon, Nov 30, 2015 at 5:23 PM, Yakov Zhdanov > > > wrote: > > > > > > > 1. I see nothing wrong in having EA perpet

Re: Ignite-1.5 Release

unreleased. --Yakov 2015-11-30 20:17 GMT+03:00 Raul Kripalani : > On Mon, Nov 30, 2015 at 5:05 PM, Yakov Zhdanov > wrote: > > > Raul, every build submitted for vote is RC (so, on first iteration this > > will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get >

Re: Ignite-1.5 Release

Dmitry, it will be 1.5.0-EA. --Yakov 2015-11-30 20:10 GMT+03:00 Dmitriy Setrakyan : > On Mon, Nov 30, 2015 at 9:09 AM, Yakov Zhdanov > wrote: > > > Guys, common practice when dealing with EA builds is to have EA (or EA1), > > EA2, etc versions. So, I would prefer t

Re: Ignite-1.5 Release

If so we will have EA2. --Yakov 2015-11-30 20:13 GMT+03:00 Dmitriy Setrakyan : > On Mon, Nov 30, 2015 at 9:12 AM, Yakov Zhdanov > wrote: > > > Dmitry, it will be 1.5.0-EA. > > > > How about 1.5.0-EA1? We may have more than one EA release.

Re: Ignite-1.5 Release

Guys, common practice when dealing with EA builds is to have EA (or EA1), EA2, etc versions. So, I would prefer to follow this process. --Yakov 2015-11-30 20:04 GMT+03:00 Dmitriy Setrakyan : > On Mon, Nov 30, 2015 at 8:57 AM, Raul Kripalani wrote: > > > On Mon, Nov 30, 2015 at 4:

Re: Ignite-1.5 Release

30, 2015 at 4:30 PM, Yakov Zhdanov > wrote: > > > Please let me know your opinion. If community agrees I will submit > 1.5.0-EA > > for vote in a few hours. > > > > Would this be an EA or a RC? > > Regards, > > *Raúl Kripalani* > PMC & Committer @

Re: Ignite-1.5 Release

I will submit 1.5.0-EA for vote in a few hours. --Yakov 2015-11-28 13:57 GMT+03:00 Yakov Zhdanov : > Guys, > > Small update. We are very close to submit Ignite-1.5-RC1. We currently > fixing TeamCity in ignite-1.5 branch. > > --Yakov > > 2015-11-25 3:39 GMT+03:00 Dmitriy

Re: OSGi integration ready for review

Raul, as far as commits - they are mostly fixes for functionality, but do not add new features. Can someone create 1.6 space and move OSGi articles there? Perhaps, Anton V. can do it? --Yakov 2015-11-30 16:42 GMT+03:00 Raul Kripalani : > Dmitriy, > > I'm not going to judge if the communication

Re: URGENT: Can we merge OSGi for 1.5?

Raul, great news! But I would better do 1.6 in a week or two since there are still a lot of stuff to check - maven uploads, binary packaging, javadocs builds, etc. --Yakov 2015-11-27 20:15 GMT+03:00 Raul Kripalani : > Hello, > > We had created the expectation of OSGi being available for 1.5. > >

Re: Communication exception handling

> > > On Sat, Nov 28, 2015 at 3:37 PM, Yakov Zhdanov > wrote: > > > Guys, > > > > I see the following code > > > > > (org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java:1129): > > > >

Communication exception handling

Guys, I see the following code (org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java:1129): try { cctx.io().send(n, req, tx.ioPolicy()); } catch (ClusterTopologyCheckedException

Re: Ignite-1.5 Release

Guys, Small update. We are very close to submit Ignite-1.5-RC1. We currently fixing TeamCity in ignite-1.5 branch. --Yakov 2015-11-25 3:39 GMT+03:00 Dmitriy Setrakyan : > On Wed, Nov 25, 2015 at 3:09 AM, Raul Kripalani wrote: > > > It's integrated, i.e. it deploys on an OSGi container. And the

Re: IGNITE-1355 Potential NPE in CacheAffinityProxy

backward compatibility. But as I see from > the methods implementation, they can throw IgniteException in some cases > now, so a user should already have processing of the exception. So, I think > we can do these changes. > > Thoughts? > > [1] https://github.com/apache/ignite/pull/263

Re: Necessity to have MBeanServerResource annotation

annotation to get > Ignite instance and getting MBeanServer. > > ignite.configuration().getMBeanServer() > > Thanks, > -- Artem -- > > On Wed, Nov 25, 2015 at 12:19 PM, Yakov Zhdanov > wrote: > > > Guys, I don't think we should delete this since it is not

Re: Necessity to have MBeanServerResource annotation

Guys, I don't think we should delete this since it is not hard at all to fix injection properly. --Yakov 2015-11-25 11:40 GMT+03:00 Denis Magda : > Igniters, > > There is MBeanServerResource annotation available as a part of Ignite. > However, according to this JIRA issue [1] its never processed

Re: Check Ignite code base with Findbugs.

Alex, if you have already run this test, can you please share the report or, even more, fix vivid trivial issues right away and let us review? --Yakov 2015-11-24 6:50 GMT+03:00 Alexey Kuznetsov : > Igniters, > > I've installed FindBugs plugin for Idea and run it on ignite-core module. > > Well i

Re: Ignite-1.5 Release

Guys! Let's update status info. 1. Data grid performance optimizations. Most of the optimizations have been merged. However, there are several pending ones 2. Direct marshalling compactions: communication optimization - Valentin My understanding is that this will be merged in nearest hours. V

Re: Ignite-1.5 Release

Hey guys! We are getting closer to the release! Thanks to everyone making this closer! Let's update status info. My understanding is that the following major parts are still not merged. Can everyone mentioned provide ticket number(s) and estimates on when the functionality will be merged. 1. Da

Re: Branch deletion prohibited

elop in > Github. > On 19 Nov 2015 09:13, "Yakov Zhdanov" wrote: > > > Disagree. This means none but committer can contribute. > > > > --Yakov > > > > 2015-11-19 12:08 GMT+03:00 Raul Kripalani : > > > > > I disagree. > > > >

Re: Branch deletion prohibited

e formality. > > Raúl. > On 19 Nov 2015 08:57, "Yakov Zhdanov" wrote: > > > Guys, therefore, let's develop new functionality in personal forks, test > on > > TC with pull requests and then merge to apache git as described here - > > https://cwiki.apa

Re: Branch deletion prohibited

Guys, therefore, let's develop new functionality in personal forks, test on TC with pull requests and then merge to apache git as described here - https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute We should create new branches only if this is really necessary. Thanks! --

Re: Ignite-1.5 Release

1. Understood 2. Well, I understand that object gets deserialized on get from cache and this most probably should not cause any issue. However, code does not look healthy and someone may think that there is an issue - field is not volatile, initialized in constructor, has sync setter, but is access

Re: Ignite-1.5 Release

Vladislav, I started to review the latest changes and have couple of questions: 1. latest changes are here - https://github.com/apache/ignite/pull/120? Is that correct? 2. org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.Sync#nodeMap is accessed in both sync and unsync

Re: Ignite-1.5 Release

> > > new test approach. > > > > > > > > > > > >> I am still using partitioned cache, does it make sense to use > > replicated > > > >> cache instead? > > > >> > > > >> Yeah, you should support this as we

Re: Custom ThreadFactory

Andrey, I closed (with proper relation) https://issues.apache.org/jira/browse/IGNITE-1899 since we already had https://issues.apache.org/jira/browse/IGNITE-10 --Yakov 2015-11-13 2:40 GMT+03:00 Andrey Kornev : > There you go: > https://issues.apache.org/jira/browse/IGNITE-1898 > and > https://iss

Re: Implement IgniteMultimap data structures

Amir, you are welcome! It would be cool if we can get it to 1.6 --Yakov 2015-11-13 13:50 GMT+03:00 Amir Akhmedov : > Hi, > > If no objections then I would like to start to work on this ticket ( > IGNITE-640 ) > > -- > Sincerely Yours Amir Akhmedo

Re: IGNITE-1355 Potential NPE in CacheAffinityProxy

Any cache can be destroyed after proxy is created, so any cache may become unexistent at any moment. So, I would still allow proxy creation for unexistent caches, but throw an exception if cache does not exist at the moment of proxy method call. --Yakov 2015-11-12 16:01 GMT+03:00 Artem Shutak :

Blog topics wiki page

Guys, I have created wiki page to put and discuss ideas for blog topics - https://cwiki.apache.org/confluence/display/IGNITE/Blog+Topics --Yakov

Re: Ignite-1.5 Release

r agreement we arrive to in mailing lists and Wiki) > > -- https://issues.apache.org/jira/browse/IGNITE-1527 > > -- https://issues.apache.org/jira/browse/IGNITE-1877 > > -- I'm working actively on these two features. > > > > *Raúl Kripalani* > > PMC & Committer @

Re: Ignite-1.5 Release

v 2, 2015 at 4:39 PM, Anton Vinogradov < > > > avinogra...@gridgain.com > > > > > > > > > wrote: > > > > > > > > > I assume that correct link at 10th feature is > > > > > https://issues.apache.org/jira/browse/IGNITE-6

Re: About the newbie bug #IGNITE-881

Hi Ken! My idea was to quit using distributed atomic long, but switch to invokes that change values atomically. In most cases this can work over atomic cache and provide faster performance. Does anyone in community have comments? --Yakov 2015-11-10 10:49 GMT+03:00 Ken Cheng : > Hi Ya

[jira] [Created] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup

Yakov Zhdanov created IGNITE-1864: - Summary: Cannot configure jndiNames for CacheJndiTmLookup Key: IGNITE-1864 URL: https://issues.apache.org/jira/browse/IGNITE-1864 Project: Ignite Issue

Re: Naming: Binarylizable

Agree with Pavel. --Yakov 2015-11-05 16:48 GMT+03:00 Pavel Tupitsyn : > Igniters, > > We have recently renamed PortableMarshalAware to Binarylizable. > I think it should be "Binarizable" instead, according to word derivation in > English language. > > "Binarylizable" yields 0 results in google,

Re: Confluence comment / write restriction

I cannot find the place where to do this. Can anyone advice how can I add Romain so he can contribute? Thanks! -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com 2015-11-05 13:40 GMT+03:00 Romain Gilles : > Hi Igniters, > I would like to provide some feadbacks on the

Re: Integration with Spring Transaction Manager

Amir, please go ahead! I have granted the necessary permissions to you. --Yakov 2015-11-04 16:48 GMT+03:00 Amir Akhmedov : > Hi Denis, > > No, my account has not been granted permissions. If you have a permission > could you grant me them. My jira account: aakhmedov > > Thanks. > > 2015-11-04 15

Re: java.lang.NullPointerException or java.lang.IllegalMonitorStateException

seems to be too trivial to file ticket for. fixed in master. --Yakov 2015-11-04 11:49 GMT+03:00 Dmitriy Setrakyan : > On Wed, Nov 4, 2015 at 12:14 AM, Yakov Zhdanov > wrote: > > > Guys, > > > > We are still facing issues with quiet logging mode. Can anyone > >

Re: HTTP-REST sql query ID problem

We can use IgniteUuid qryId = IgniteUuid.fromUuid(clientId); and restrict page requests for queries submitted from other clients. I.e. throw exception if qryId.globalId() != clientId --Yakov 2015-11-04 12:21 GMT+03:00 endian675 : > Alexey, > > No problem, here is a link that is relatively simpl

Fwd: java.lang.NullPointerException or java.lang.IllegalMonitorStateException

Guys, We are still facing issues with quiet logging mode. Can anyone add information on java runtime and OS to quiet mode? --Yakov -- Forwarded message -- From: Andrey Gura Date: 2015-11-04 0:10 GMT+03:00 Subject: Re: java.lang.NullPointerException or java.lang.IllegalMonitorSt

Ignite-1.5 Release

Guys, I think we can start preparation to Ignite-1.5 release which will include many interesting features: 1. Portable object API https://issues.apache.org/jira/browse/IGNITE-1486 2. Ignite.NET and Ignite C++ https://issues.apache.org/jira/browse/IGNITE-1282 3. Optimistic serializable transacti

Re: Request add me to development list

Done! --Yakov 2015-11-02 14:53 GMT+03:00 Denis Magda : > Yakov, Dmitriy or anyone else from the community with administrative > rights please provide Prabhat's JIRA account with all required permissions. > > -- > Denis > > On 11/2/2015 1:49 PM, Prabhat Ranjan wrote: > >> Thanks Denis. >> >> Plea

Re: OSGi migration may require a special marshaller

! Thanks! -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com 2015-11-02 12:56 GMT+03:00 Gilles, Romain : > Hi all, > > I'm really interested in this issue: > https://issues.apache.org/jira/browse/IGNITE-1270 . We some stuff to make > it work in our osgi env

Re: Contributing to Ignite

Dmitry, I have added you to contributors. You are welcome! --Yakov 2015-11-02 11:11 GMT+03:00 Дмитрийфф : > I would like to work on this issue > https://issues.apache.org/jira/browse/IGNITE-1831 > > please assign this issue to me, my account on jira @Dmitriyff > > 2015-11-02 14:59 GMT+07:00 Alex

[jira] [Created] (IGNITE-1811) Get from backup in Dht cache can be optimized

Yakov Zhdanov created IGNITE-1811: - Summary: Get from backup in Dht cache can be optimized Key: IGNITE-1811 URL: https://issues.apache.org/jira/browse/IGNITE-1811 Project: Ignite Issue Type

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 > wrote: > >

Re: Remote job execution in C++

I think suggested approach should work. Any idea on how to add dynamic jobs loading (I would like it is added in one of nearest releases)? I.e. I copy new library to each server then load it with Ignite API and have new jobs available without restarting cluster. --Yakov 2015-10-20 18:46 GMT+03:0

[jira] [Created] (IGNITE-1783) Remove GridBoundedConcurrentLinkedHashMap and replace its usages with ConcurrentLinkedHashMap

Yakov Zhdanov created IGNITE-1783: - Summary: Remove GridBoundedConcurrentLinkedHashMap and replace its usages with ConcurrentLinkedHashMap Key: IGNITE-1783 URL: https://issues.apache.org/jira/browse/IGNITE-1783

Re: MQTT Streamer Code Style and Javadoc fixes (IGNITE-1747)

t; Regards, > > *Raúl Kripalani* > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and > Messaging Engineer > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitter: @raulvk > > On Thu, Oct 22,

Re: MQTT Streamer Code Style and Javadoc fixes (IGNITE-1747)

Hi Raul! Thank you very much for addressing my comments! I like the code however there are still a couple of points (I committed everything to ignite-1747): 1. Please take a look at https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-StringOutput 2. org.apache.i

Re: Do we need "IgniteCache.randomEntry()" method?

This behavior should definitely be fixed - exception should be thrown on client node. I will update ticket. William, thanks for pointing this out. --Yakov 2015-10-15 20:33 GMT+03:00 William Kemper : > I never filed a ticket, but for what it's worth, I tried using this method > in a test scenario

Re: Optimistic/serializable transactions implementation

Agree with Sam here - we also reduce network calls since we don't need to notify for each failed tryLock, but only for cases when tx will definitely loose. Thanks! -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com 2015-10-16 10:22 GMT+03:00 Semyon Boikov : > >

Re: A Future with intermediate progress?

I don't think this makes sense. How would you measure progress of cache put? Does anyone need that? On the opposite, I agree that it would be nice to have future that is able to notify user on primaries updated, then on backups update, but again there were no requests for that. --Yakov 2015-10-1

Re: IgniteEvents.remoteListen() semantics

It uses similar approach as continuous query - remoteFiltering and localListener notification. Thanks! -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com 2015-10-14 16:45 GMT+03:00 Vladimir Ozerov : > Yakov, I'm not sure whether there are any problems or not. T

Re: [VOTE] Establishing duration of Apache Ignite Chair rotation

+1 (binding) --Yakov 2015-10-14 1:30 GMT+03:00 Konstantin Boudnik : > Hi! > > As discussed in the "[DISCUSS] PMC Chair rotation" thread last month, I > propose > that we adopt a rule allowing for a Apache Ignite Chair rotation on a > yearly > basis. The proposed policy is this: > - a position

Re: IgniteEvents.remoteListen() semantics

Pavel, this is source node ID which is already in the event, as you mentioned. Vladimir, can you please file a ticket? --Yakov 2015-10-13 14:11 GMT+03:00 Pavel Tupitsyn : > Related question: > > What does first UUID arg mean in "IgniteBiPredicate locLsnr"? > It can either be event source node id

Re: Which thread is used to run IgniteFuture continuations?

Not sure if I get the point. You can do exactly the same inside your listener. final Executor executor = ...; // Bla-bla cache.future().listen(() => { executor.execute(new Runnable() { latch.await(); /** Do something useful. */ } }); --Yakov 2015-10-09 17:22 GMT+03:00 V

Re: .Net: separate methods for async operations.

> 2 lines of code instead of one is not a big deal in my view. >It is 2 times too much, sometimes even more. Imagine a situation where you >need to perform multiple async operations: >cache.Get(1); >var res = await cache.GetFuture().ToTask(); >compute.Call(new MyCallable(res)) >var res2 = await

Re: .Net: separate methods for async operations.

Is current thread blocked until "await" instruction is completed in parallel thread? --Yakov 2015-10-12 10:41 GMT+03:00 Vladimir Ozerov : > Example with Get() operation: > > async Task GetAndMultiply() { > // This line is executed in current thread. > Task res = cache.GetAsync(1); > >

Re: ignite-1.4 version is still "unreleased" in Jira

I renamed "ignite-1.5" and "ignite-1.6" to 1.5 and 1.6 --Yakov 2015-10-08 17:38 GMT+03:00 Yakov Zhdanov : > This is very easy. > > --Yakov > > 2015-10-08 17:35 GMT+03:00 Dmitriy Setrakyan : > >> On Thu, Oct 8, 2015 at 7:31 AM, Yakov Zhdan

Re: ignite-1.4 version is still "unreleased" in Jira

This is very easy. --Yakov 2015-10-08 17:35 GMT+03:00 Dmitriy Setrakyan : > On Thu, Oct 8, 2015 at 7:31 AM, Yakov Zhdanov wrote: > > > I released "ignite-1.4". > > > > And also removed "1.5". Who created it? Why not rename "ignite-1.5"?

Re: ignite-1.4 version is still "unreleased" in Jira

I released "ignite-1.4". And also removed "1.5". Who created it? Why not rename "ignite-1.5"? --Yakov 2015-10-07 19:28 GMT+03:00 Konstantin Boudnik : > Techically it should be the RM. I am looking through the website and wiki > and > I can not find the description of the release procedure. Unle

Re: Cluster group affinity

2015-10-07 15:14 GMT+03:00 Andrey Kornev : > Thanks, Yakov! I'm going to use your code (I hope it's Apache2 licensed:))) > You are welcome! No warranties, btw. I did not test this code :) > > As for the use case, it's quite simple. I have a group of compute nodes > that are being sent a stream

Re: Cluster group affinity

Andrey, probably it is, but I am not sure if I have ever had a thought for mentioned scenario. I think you should get existing implementation and use it like this. Make sure to cache assignments as this may be quiet expensive operation. Ignite ignite = Ignition.start(cfg); Cluste

Re: Why portable marshaller handle Date and Timestamp in the same way?

2015-10-06 12:45 GMT+03:00 Dmitriy Setrakyan : > On Tue, Oct 6, 2015 at 2:42 AM, Vladimir Ozerov > wrote: > > > This doesn't answers the question. First, Java Timestamp has greater > > precision than .Net DateTime, so silent data loss could happen in this > case > > as well. Second, "use timestam

[jira] [Created] (IGNITE-1605) Provide stronger data loss check

Yakov Zhdanov created IGNITE-1605: - Summary: Provide stronger data loss check Key: IGNITE-1605 URL: https://issues.apache.org/jira/browse/IGNITE-1605 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-1604) Provide ability to get notification on rebalancing finish

Yakov Zhdanov created IGNITE-1604: - Summary: Provide ability to get notification on rebalancing finish Key: IGNITE-1604 URL: https://issues.apache.org/jira/browse/IGNITE-1604 Project: Ignite

Re: Introducing "compatibility level" concept.

>> 6) Node A restarts and meets unknown B-protocol. 6.1 Node A throws exception on start 6.2 Or node A invalidates persistent store (ignores the prev state) 6.3 Or user should have ability to specify converter somehow. Converter logic should be provided with release of new protocol (with more rece

Re: New 'Deployment tasks' article on readme.io

I am looking at this page - https://apacheignite.readme.io/docs/deployment-spi. Correct? Good job! However, I have minor comments: 1. SPI parameters explanations and code example should be before scanners (scanner is SPI config as well, just more detailed info) 2. code example should include all

Re: LGPL in 1.4 examples

We can. --Yakov 2015-09-30 10:29 GMT+03:00 Dmitriy Setrakyan : > On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov > wrote: > > > I filed the ticket: > > Build examples failed from binary fabric package > > > > > > > I think the reason is that we

Re: Switched main version to 1.4 on readme.io

done. --Yakov 2015-09-29 20:34 GMT+03:00 Dmitriy Setrakyan : > Yakov, > > The javadoc link on Ignite documentation still points to 1.3. Can you make > the switch? > > Thanks, > D. > > On Mon, Sep 28, 2015 at 3:24 PM, Yakov Zhdanov > wrote: > > > subj > > > > --Yakov > > >

Re: Sergey Evdokimov Tickets

:44 GMT+03:00 Dmitriy Setrakyan : > On Tue, Sep 29, 2015 at 4:45 PM, Yakov Zhdanov > wrote: > > > Hi! > > > > I want to ask if Sergey is going to continue working on tickets assigned > to > > him? If not, we will reassign them in 72 hours. > > > > I

Re: Ignite 1.5 plans

Igniters, Given we somehow agreed on most of the scope, can everyone please cleanup JIRA queues accordingly? --Yakov

Re: Ignite 1.5 plans

> >> > Let me know if you agree. > >> > Regards, Gianfranco > >> > > >> > 2015-09-28 18:50 GMT+02:00 Dmitriy Setrakyan : > >> > > >> > > I would like to add one more: > >> > > 10. OSGI integration - Raul Kripalani &g

Sergey Evdokimov Tickets

Hi! I want to ask if Sergey is going to continue working on tickets assigned to him? If not, we will reassign them in 72 hours. Thanks! --Yakov

Re: TCP Loopback Fast Path on Windows 8/2012

Good catch, Pavel! --Yakov 2015-09-29 11:57 GMT+03:00 Pavel Tupitsyn : > Hi Sergey, > > As I understand, since we use standard Java sockets, SIO_LOOPBACK_FAST_PATH > control code usage is up to JDK. > For example, OpenJDK supports it: > https://bugs.openjdk.java.net/browse/JDK-8060170 > > Thanks

Re: TCP Loopback Fast Path on Windows 8/2012

I would not mess with this - this works only on 2012 server and win8 and requires some native coding. Let's postpone this until we need to optimize some windows server deployment. Thoughts? --Yakov 2015-09-29 9:07 GMT+03:00 Sergey Kozlov : > Hi Igniters > > I found the intersting article: > > >

Re: Ignite 1.5 plans

> I'd like to add several things. > 1) It looks like fix for IBM JVM will brake backward compatibility because > the problem is caused by missing serialVersionId, right? If we add default UUIDS as calculated by hotspot everything seems to be fine then. > 2) HP-UX users are also concerned, see las

Re: Replace incubator-ignite to ignite

fixed. Thanks! -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com 2015-09-29 10:25 GMT+03:00 chandresh pancholi < chandreshpancholi...@gmail.com>: > Hi, > > I was going through ignite coding guidelines and saw this line. > >- copy incubator-ignite\

Re: Coding Guidelines: zookeeper IP finder and mqtt streamer

> #1 Yakov, how exactly are you reading the Git history? WIP commits were > never on master, they were in a feature branch which was merged into master > on this commit: You can check the history of the streamer. I see more than one entry. Probably, that was mistake on merge - commits were not squ

Re: Write Access To Wiki

I think any contribution should require ICLA. Moreover, it is not a big deal :) --Yakov 2015-09-28 19:31 GMT+03:00 Raul Kripalani : > Hey Igniters, > > Is an ICLA necessary for Wiki contributions at Ignite? > > Branko at [1] said "Any non-trivial documentation change requires an ICLA > just like

Ignite 1.5 plans

Guys! We have finalized 1.4 release! Thanks to everyone involved! That was very important release for our project. Let's discuss scope for 1.5. I think the main focus areas should be: 1. Optimized marshaller rework - Alex Goncharuk works on this. 2. .Net and Cpp API release (depends on 3) - Vla

Switched main version to 1.4 on readme.io

subj --Yakov

[RESULT] [VOTE] Apache Ignite 1.4.0 Release (RC1)

Hello! Apache Ignite 1.4.0 release (RC1) has been accepted. 9 "+1" votes received. Here are the votes received: - Denis Magda (binding) - Anton Vinogradov (binding) - Alexey Kuznetsov (binding) - Sergi Vladykin (binding) - Gianfranco Murador (binding) - Vladimir Ozerov (bindin

Coding Guidelines: zookeeper IP finder and mqtt streamer

Guys, I have just reviewed the code and have some comments. 1-2 are very serious from my point of view. 1. Code is in master. Did anyone checked tests on TC? Moreover, are there suites for those tests? 2. It seems that work on streamer has been done directly in master. I see WIP commits, but I th

Re: version names

hat's the problem > with the proposed names fix. > > Cos > > On Sun, Sep 27, 2015 at 01:06PM, Yakov Zhdanov wrote: > > Cos, believe me there will be efforts. How about maven poms and automated > > procedures? This will need to be fixed and retested. I want to avoi

Re: version names

Cos, believe me there will be efforts. How about maven poms and automated procedures? This will need to be fixed and retested. I want to avoid it unless it's absolutely needed. Thanks! Yakov On Sep 27, 2015 12:24, "Konstantin Boudnik" wrote: > On Sun, Sep 27, 2015 at 12:1

Re: version names

I would leave it as is for now. Just to avoid any extra efforts. Another point is - what if we decide to release products like accelerator for hadoop or data fabric for .net separately at some point? We will need to somehow distinguish. --Yakov 2015-09-26 23:23 GMT+03:00 Raul Kripalani : > Agree

Re: IGNITE-534 JMS 1.1 Streamer - Work completed

Raul, Here are my comments on jms streamer readme io article. Can you please fix them? 1. "Features supported" and "Instantiating a JMS Streamer" sections both contain description of streamer parameters. It seems to be a better approach to organize all streamer properties as table with descripti

[VOTE] Apache Ignite 1.4.0 Release (RC1)

Dear Sirs! We have uploaded release candidate to https://dist.apache.org/repos/dist/dev/ignite/1.4.0-rc1/ I am very glad to mention that this is the first Ignite release as top level project! Thanks everyone for help this to happen! Tag name is ignite-1.4.0-rc1 1.4.0 changes: * Added SSL suppor

Re: Optimizing portable protocol.

Vova, very good points! --Yakov 2015-09-25 14:28 GMT+03:00 Vladimir Ozerov : > Igniters, > > Thorough analysis of portable object format lead me to conclusion that > significant part of transferred data is either zeros, several constants > (e.g. 0, 1, -1, true, false) or some redundant informati

Re: [NOTICE] TeamCity is down

Cos, is it ok that none of the domain names mentioned in ticket responds? Even those with "dig" output. Created ticket for Ignite - https://issues.apache.org/jira/browse/INFRA-10484 --Yakov 2015-09-22 21:01 GMT+03:00 Konstantin Boudnik : > Something like this could be arranged with INFRA >

Re: ignite 1.4 status

x27;re pretty close to get this issue fixed :) > > 2015-09-22 9:43 GMT-07:00 Yakov Zhdanov : > > > Alex, I spent some time debugging this today. > > > > I noticed that we do not verify that topology version of the custom > message > > is identical to current ring ve

Re: IGNITE-534 JMS 1.1 Streamer - Work completed

Dmitriy, Can you please check that I am still admin in readme io? I cant review the documentation for 1.4 --Yakov 2015-09-20 21:55 GMT+03:00 Raul Kripalani : > Hey guys, > > I've documented this feature on readme.io, on branch 1.4: > https://apacheignite.readme.io/v1.4/docs/jms-data-streamer. >

Re: ignite 1.4 status

h >leads to this assertion > > I committed my pending debug code to ignite-1171-debug branch, if any of > you guys is up to debugging this issue while I'm asleep - great, if not - > I'll continue digging into it tomorrow. > > 2015-09-21 10:55 GMT-07:00 Yakov

Re: ignite 1.4 status

Igniters, We are not ready to release today. Alexey Goncharuk is still working on ignite-1171. Alex please provide updates by the end of the day. https://issues.apache.org/jira/browse/IGNITE-1516 - performance offheap query benchmark is not fully recovered. Semyon will be fixing it. Sergi, can y

Re: Nodes starts in tests

t; Date: Sun, Sep 20, 2015 at 1:46 PM > > Subject: Re: Nodes starts in tests > > To: dev@ignite.apache.org > > > > > > On Sun, Sep 20, 2015 at 1:34 PM, Branko Čibej wrote: > > > > > On 20.09.2015 10:11, Yakov Zhdanov wrote: > > > > Very cool idea! How

Re: Nodes starts in tests

Sun, Sep 20, 2015 at 1:34 PM, Branko Čibej wrote: > > > > > On 20.09.2015 10:11, Yakov Zhdanov wrote: > > > > Very cool idea! However this will not be working in 100% cases since > > > > sometimes we need custom grid configurations, SPIs, etc, but for

Re: Nodes starts in tests

4 GMT+03:00 Branko Čibej : > On 20.09.2015 10:11, Yakov Zhdanov wrote: > > Very cool idea! However this will not be working in 100% cases since > > sometimes we need custom grid configurations, SPIs, etc, but for > > significant number of tests this will work. > > This i

Re: Nodes starts in tests

Very cool idea! However this will not be working in 100% cases since sometimes we need custom grid configurations, SPIs, etc, but for significant number of tests this will work. --Yakov 2015-09-20 11:00 GMT+03:00 Sergi Vladykin : > Guys, > > A little observation. We have really many tests which

Re: ignite 1.4 status

5) [06:11:40]W: [org.apache.ignite:ignite-core] at org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5268) [06:11:40]W: [org.apache.ignite:ignite-core] at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gri

Re: ignite 1.4 status

Semyon, too. We need to postpone release till very beginning of next week. --Yakov 2015-09-18 12:01 GMT+03:00 Yakov Zhdanov : > Alex, I think that your approach with delaying custom message will work. > As far as coordinator crash protection, we guarantee delivery of certain > messa

<    2   3   4   5   6   7   8   >