[jira] [Created] (IGNITE-2088) EntryProcessor invoke might not run in CLOCK write order

Avihai Berkovitz created IGNITE-2088: Summary: EntryProcessor invoke might not run in CLOCK write order Key: IGNITE-2088 URL: https://issues.apache.org/jira/browse/IGNITE-2088 Project: Ignite

Ignoring a node as a Service Grid deployment candidate

Igniters, Presently every node that is a part of a cluster listens for Service Grid assignment changes in order to find out whether a service has to be deployed on it or not. However, there is a possible case when a node is not considered to be a target for service A at all during its

Re: EA versioning

Cos and Brane, This issue arised not from our feeling of beautiful, but from practical reasons, namely we need to conform existing Maven and OSGi version models at the same time. We did not invent Maven or OSGi, but if we want to play with them well, we have to keep in mind their own quirks and

[CLOSE] [VOTE] Apache Ignite 1.5.0-b1

Guys, Community agreed to release Apache Ignite 1.5.0-b1. Results: 9 "+1" votes (7 binding) out of 9 votes The following votes were received: 1. Yakov Zhdanov +1 (binding) 2. Anton Vinogradov +1 (binding) 3. Nick Tikhonov +1 (binding) 4. Raul Kripalani +1 (binding) 5. Vladislav Jelisavcic +1

Re: Ignoring a node as a Service Grid deployment candidate

Denis, What will happen if node B becomes a deployment target due to topology changes? Thanks, Roman On Sunday, December 6, 2015 5:17 PM, Denis Magda wrote: Igniters, Presently every node that is a part of a cluster listens for Service Grid assignment changes in order

Re: EA versioning

On Sun, Dec 06, 2015 at 11:30AM, Sergi Vladykin wrote: > Cos and Brane, > > This issue arised not from our feeling of beautiful, but from practical > reasons, > namely we need to conform existing Maven and OSGi version models at the > same time. > > We did not invent Maven or OSGi, but if we

What is jdbc:ignite:cfg ??

Guys, I am looking into [1] and see a reference to ignite.jdbc.url = "jdbc:ignite:cfg://" So, I am curious if there's a way to fetch node's config via JDBC somehow? Or this is just a simple error in the doc, which needs to be fixed? Would appreciate the insight from the team. Thanks! Cos

[jira] [Created] (IGNITE-2089) Implement static block callout

Dmitriyff created IGNITE-2089: - Summary: Implement static block callout Key: IGNITE-2089 URL: https://issues.apache.org/jira/browse/IGNITE-2089 Project: Ignite Issue Type: Sub-task Affects

Weird releases [Was: EA versioning]

Forking of the release schema conversation. I have noticed that official dist http://archive.apache.org/dist//ignite/ has 2.2.2-test version. Anyone knows why it is there? Cos signature.asc Description: Digital signature

Re: EA versioning

Oh, and not to say - JIRA would have to have a corresponding versions. Say right now I see only 1.5 in JIRA and it has 161 unresolved bugs. However, the -b1 release is already voted for and is almost official. Cos On Sun, Dec 06, 2015 at 03:11PM, Konstantin Boudnik wrote: > On Sun, Dec 06, 2015