Re: Halfway to Ignite 1.6

Igniters, We postponed code freeze till monday UTC 19-00. On Thu, May 12, 2016 at 1:48 PM, Anton Vinogradov wrote: > Typo fix: > Pushes to ignite-1.6 are allowed till Friday (*May *13) 19:00 UTC. > > > > On Thu, May 12, 2016 at 1:41 PM, Anton Vinogradov wrote: > >>

Re: Code merge in 1.6 branch at 16-th

Seems we postpone code freeze till monday UTC 19-00. So, feel free to merge changes on Monday On Fri, May 13, 2016 at 6:19 PM, Alexey Kuznetsov wrote: > I also have whole feature (web-console) not merged yet to ignite-1.6. Also > need some review before merge. > > > > On Fri, May 13, 2016 at 10:

Re: Halfway to Ignite 1.6

Typo fix: Pushes to ignite-1.6 are allowed till Friday (*May *13) 19:00 UTC. On Thu, May 12, 2016 at 1:41 PM, Anton Vinogradov wrote: > Igniters, > > Ignite 1.6 almost ready to be finally tested. > > Branch ignite-1.6 now contains all changes scheduled for 1.6. > > In

Re: Halfway to Ignite 1.6

. On Fri, May 6, 2016 at 4:18 PM, Anton Vinogradov wrote: > Igniters, > > We're going to release Ignite 1.6 in the nearest future. > Branch ignite-1.6 was created and already contains changes scheduled for > 1.6. > > And from now on, I propose to start testing and fixing i

Halfway to Ignite 1.6

Igniters, We're going to release Ignite 1.6 in the nearest future. Branch ignite-1.6 was created and already contains changes scheduled for 1.6. And from now on, I propose to start testing and fixing ignite-1.6 source code to provide stable release. As you know we have a huge amount of tests and

Re: 1.5.0.final is breaking packaging: osgi dependency is non-existent

Igniters, Issue is critical for Bigtop project. In case someone familiar with OSGI please have a look. On Wed, May 4, 2016 at 11:15 AM, Anton Vinogradov wrote: > Roman, Raul, > > As far as I remember you're familiar with OSGI. Could you please have a > look at this? > >

Re: 1.5.0.final is breaking packaging: osgi dependency is non-existent

Roman, Raul, As far as I remember you're familiar with OSGI. Could you please have a look at this? On Wed, May 4, 2016 at 6:09 AM, Konstantin Boudnik wrote: > Hey guys > > For your information: adding osgi into the product is breaking the > dependency matrix of the bigtop packages. For more inf

Re: IGNITE-1071 IgniteCache.metrics() method returns local metrics

gt; Could we have local and global MBeans? > > Or local and global metrics inside same MBean? > > > > On Thu, Mar 24, 2016 at 6:26 PM, Anton Vinogradov < > > avinogra...@gridgain.com> > > wrote: > > > > > Hello, > > > > > > I

IGNITE-1071 IgniteCache.metrics() method returns local metrics

Hello, I'd like to discuss IGNITE-1071 IgniteCache.metrics() method returns local metrics I agree to make IgniteCache.metrics() global but want to keep MBeans local. According to specification: An MBean can represent a device, an application, o

All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

Hello, I found that every BinaryObject created by BinaryObjectBuilder has hashcode == 0 by default. This can cause situation that all objects created by code similar to: *BinaryObject key = builder.setField("id", i).build();* *streamer.addData(key, key);* will be stored at one partition and this

Re: github replication of Ignite

Replication fixed. On Thu, Mar 24, 2016 at 11:04 AM, Anton Vinogradov wrote: > Roman, > > thanks for pointing this, I've created infra issue > > https://issues.apache.org/jira/browse/INFRA-11534 > > On Thu, Mar 24, 2016 at 8:53 AM, Roman Shtykh > wrote: > >

Re: github replication of Ignite

Roman, thanks for pointing this, I've created infra issue https://issues.apache.org/jira/browse/INFRA-11534 On Thu, Mar 24, 2016 at 8:53 AM, Roman Shtykh wrote: > Hi Anton, > > I have pushed two changes to the master this morning and see no > replication to github. Is it normal? > > It seems y

Re: Contributions that are waiting for review

be the first improvement we can do > in this direction. > > -- > Denis > > > On 3/4/2016 4:14 PM, Anton Vinogradov wrote: > >> Pavel, >> I think that script should be stored inside TeamCity task. >> >> >> >> On Fri, Mar 4, 2016 at 3:56 PM, Pavel Tup

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

:35, Dmitriy Setrakyan > > wrote: > > > > > > +1 on FAQ > > > > > > Can we just create a page, and start populating it? > > > > > > D. > > > > > > On Fri, Mar 11, 2016 at 3:25 AM, Anton Vinogradov < > > avinogra.

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Yakov, I've answered. Seems we have to have special FAQ section at Ignite wiki to publish same things. On Sun, Mar 6, 2016 at 12:21 PM, Yakov Zhdanov wrote: > Vlad and all (esp Val and Anton V.), > > I reviewed the PR. My comments are in the ticket. > > Anton V. there is a question regarding op

Re: Contributions that are waiting for review

ve something > suitable already? > > > > On Fri, Mar 4, 2016 at 3:34 PM, Anton Vinogradov > > wrote: > > > Folks, > > > > we can create TeamCity task with special trigger (eg. once a day). > > This task can contains any script. > > > > On Fri

Re: Contributions that are waiting for review

Folks, we can create TeamCity task with special trigger (eg. once a day). This task can contains any script. On Fri, Mar 4, 2016 at 3:18 PM, Pavel Tupitsyn wrote: > Raul, I'm not good with shell scripts. As a .net person I was thinking > about a scheduled C# script on one of our TeamCity win ma

Re: Switching back to review-then-commit process

+1 (but I hope it's still up to a committer to decide whether a change should need a review or not.) On Thu, Mar 3, 2016 at 8:09 PM, Dmitriy Setrakyan wrote: > I hate to be religious about anything, but do think that for most of the > functionality, RTC makes sense. > > On Thu, Mar 3, 2016 at 7:

Re: IGNITE-2693 - could someone take a look and help me with a quick review

Hello, commented at issue On Thu, Mar 3, 2016 at 5:28 PM, Dood@ODDO wrote: > Hello, > > This is my second Ignite ticket and if I understand correctly, it is a > simple fix - I submitted a patch recently, it is only a few lines. Can > someone take a look and see if I am on the right track or did

Re: Contributions that are waiting for review

Denis, We have a special status at Ignite JIRA - PATCH AVAILABLE which means that issue ready to be reviewed. Currently 59 issues has such status according to https://issues.apache.org/jira/issues/?filter=-2&jql=project%20%3D%20Ignite%20and%20status%20%3D%20%22Patch%20Available%22 I think we have

Re: newbie tickets

Done, Updated to https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20status%20%3D%20OPEN On Wed, Feb 24, 2016 at 12:15 PM, Yakov Zhdanov wrote: > I think link should be > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%2

Re: Grid behavior at key deserialization failure during rebalancing

t; becomes more critical. > > D. > > On Tue, Feb 16, 2016 at 12:37 AM, Anton Vinogradov < > avinogra...@gridgain.com > > wrote: > > > Dmitry, > > > > I found such behavior at GridCacheRebalancingUnmarshallingFailedSelfTest. > > Seems

[jira] [Created] (IGNITE-2660) Correct Grid behavior at key deserialization failure during rebalancing

Anton Vinogradov created IGNITE-2660: Summary: Correct Grid behavior at key deserialization failure during rebalancing Key: IGNITE-2660 URL: https://issues.apache.org/jira/browse/IGNITE-2660

Re: Grid behavior at key deserialization failure during rebalancing

, Dmitriy Setrakyan wrote: > Anton, > > I am not sure why we would deserialize on the server side with Binary > Marshaller. The data should remain in binary form. Do you know if we have a > test for it? > > Thanks, > D. > > On Mon, Feb 15, 2016 at 1:20 AM,

Re: Grid behavior at key deserialization failure during rebalancing

, Dmitriy Setrakyan wrote: > Anton, > > I am not sure I fully grok the use case. Can you please explain why a key > can be broken? > > D. > > On Fri, Feb 12, 2016 at 7:11 AM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > > Igniters, >

Grid behavior at key deserialization failure during rebalancing

Igniters, At this moment key deserialization failure during rebalancing cause strange situation: Rebalancing from node sent supply message with broken key will be cancelled at current topology. All upcoming supply messages from this node will be be ignored, no new demand messages to this node wil

[jira] [Created] (IGNITE-2565) TCK suite fail periodically

Anton Vinogradov created IGNITE-2565: Summary: TCK suite fail periodically Key: IGNITE-2565 URL: https://issues.apache.org/jira/browse/IGNITE-2565 Project: Ignite Issue Type: Bug

Re: [jira] [Commented] (IGNITE-1523) Need to always serialize user objects with configured marshaller

Val, Please see commit 28a5247d37ba65bdcb6119f97023f32d511b5f1e at master. On Thu, Feb 4, 2016 at 3:53 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Anton, > > Where can I see the changes? > > -Val > > On Wed, Feb 3, 2016 at 12:01 AM, An

Powered by Ignite logo

Igniters, I'd like to add "Powered by Ignite" logo files to https://www.apache.org/foundation/press/kit/poweredBy but I have no such permissions. Only ASF Members can do it. "Powered by Ignite" logo files located at /x1/home/sboikov/pb (at people.apache.org) Could someone from ASF Members copy

Re: [jira] [Commented] (IGNITE-1523) Need to always serialize user objects with configured marshaller

n you please assign it to yourself? > > -Val > > -- Forwarded message -- > From: Anton Vinogradov (JIRA) > Date: Tue, Feb 2, 2016 at 4:43 AM > Subject: [jira] [Commented] (IGNITE-1523) Need to always serialize user > objects with configured marshaller > To: v

new committer and PMC member: Roman Shtykh

The Project Management Committee (PMC) for Apache Ignite has asked Roman Shtykh to become a committer and PMC member and we are pleased to announce that Roman has accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. T

[jira] [Created] (IGNITE-2514) IgfsStartCacheTest.testCacheStart (IGFS test suite) fails periodically

Anton Vinogradov created IGNITE-2514: Summary: IgfsStartCacheTest.testCacheStart (IGFS test suite) fails periodically Key: IGNITE-2514 URL: https://issues.apache.org/jira/browse/IGNITE-2514

Re: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

pelin integration and have noticed > that > > > > the > > > > version reported by the node in the log isn't the same as the version > > > just > > > > released. It says > > > > 1.5.0-final > > > > instead of > &g

Re: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

.final version. What is the > procedure for adding it? > > D. > > On Mon, Jan 4, 2016 at 2:12 AM, Anton Vinogradov wrote: > > > Hello! > > > > Apache Ignite 1.5.0.final release (RC3) has been accepted. > > > > 13 "+1" votes received. > >

[RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

Hello! Apache Ignite 1.5.0.final release (RC3) has been accepted. 13 "+1" votes received. Here are the votes received: - Anton Vinogradov (binding) - Nikolay Tikhonov (binding) - Konstantin Boudnik (binding) - Semyon Boikov (binding) - Gianfranco Murador (binding)

Ignite Voting Process

Igniters, We've published Ignite Voting Process, please have a look before sending +1 to vote ;) https://cwiki.apache.org/confluence/display/IGNITE/Voting+Process

Re: [VOTE] Apache Ignite 1.5.0.final RC3

Semyon's +1 is binding On Wed, Dec 30, 2015 at 5:11 PM, Gianfranco Murador wrote: > +1 (binding) > > 2015-12-30 15:09 GMT+01:00 Semyon Boikov : > > > +1 > > > > On Tue, Dec 29, 2015 at 1:54 PM, Anton Vinogradov wrote: > > > > > Dear Sirs!

Re: Providing an example as part of contribution

Tue, Dec 29, 2015 at 4:46 PM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > > This should be at least discussable for each new feature/functionalitiy. > > It would be nice to see OSGi example at this release. It's still riddle > for > > me what

Re: Providing an example as part of contribution

This should be at least discussable for each new feature/functionalitiy. It would be nice to see OSGi example at this release. It's still riddle for me what our OSGi modules do. On Tue, Dec 29, 2015 at 4:41 PM, Yakov Zhdanov wrote: > I suggest no rules here. Let's take the decision on whether to

Re: Providing an example as part of contribution

+100500 On Tue, Dec 29, 2015 at 4:21 PM, Sergey Kozlov wrote: > Hi > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > I propose to introduce the requirement to add an example for new > features/functionalities. It will make easier further using/testing by the > communit

Re: [VOTE] Apache Ignite 1.5.0.final RC3

+1 (binding) On Tue, Dec 29, 2015 at 4:17 PM, 姜 为 wrote: > +1 nice job! > > > 在 2015年12月29日，下午6:54，Anton Vinogradov 写道： > > > > Dear Sirs! > > > > We have uploaded release candidate to > > https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-r

[VOTE] Apache Ignite 1.5.0.final RC3

Dear Sirs! We have uploaded release candidate to https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc3/ This is very important release containing initial versions of Ignite.NET and Ignite C++ and many other important features. Tag name is 1.5.0.final-rc3 1.5.0 changes: * Ignite.NET: Ini

[CLOSE] [VOTE] Apache Ignite 1.5.0.final

Vote has to be closed due to found issues. A new build will be resubmitted soon.

[jira] [Created] (IGNITE-2305) DEVNOTES.txt should contain infornation about platform build.

Anton Vinogradov created IGNITE-2305: Summary: DEVNOTES.txt should contain infornation about platform build. Key: IGNITE-2305 URL: https://issues.apache.org/jira/browse/IGNITE-2305 Project

Re: [VOTE] Apache Ignite 1.5.0.final

e goal >> > org.apache.maven.plugins:maven-antrun-plugin:1.7:run (dotnetdoc) on >> project >> > ignite-clients: An Ant BuildException has occured: Execute failed: >> > java.io.IOException: Cannot run program "doxygen" (in directory >> > &

Re: [VOTE] Apache Ignite 1.5.0.final

+1 (binding) On Fri, Dec 25, 2015 at 4:19 PM, Nikolay Tikhonov wrote: > +1 (binding) > > On Fri, Dec 25, 2015 at 4:00 PM, Anton Vinogradov wrote: > > > Dear Sirs! > > > > We have uploaded release candidate to > > https://dist.apache.org/repos/dist/dev/ign

[VOTE] Apache Ignite 1.5.0.final

Dear Sirs! We have uploaded release candidate to https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc1/ This is very important release containing initial versions of Ignite.NET and Ignite C++ and many other important features. Tag name is 1.5.0.final-rc1 1.5.0 changes: * Ignite.NET: Ini

Re: 1.5.final

The fix for https://issues.apache.org/jira/browse/IGNITE-2175 has been merged to ignite-1.5​ On Wed, Dec 23, 2015 at 4:30 PM, Alexey Kuznetsov wrote: > I think "IGNITE-2252 Add support for cache sql schema in REST topology > command" will be fixed tomorrow in first half of a day. > > On Wed, Dec

Re: 1.5.final

I closed one, Left: IGNITE-2175 Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7) On Wed, Dec 23, 2015 at 9:22 AM, Vladimir Ozerov wrote: > I closed my ticket. There was a problem in test preventing compilation with > Java 8. > > On We

Re: 1.5 GA

Versions updated. On Tue, Dec 22, 2015 at 12:36 PM, Anton Vinogradov wrote: > Seems everything is ok, > > https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-b1 > https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-final > > I'll update versions. >

Re: 1.5 GA

Seems everything is ok, https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-b1 https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-final I'll update versions. On Tue, Dec 22, 2015 at 12:28 PM, Anton Vinogradov wrote: > Dmitriy, > > that's not a big change, b

Re: 1.5 GA

t mean that we need to rush > and > > produce yet another one that will be causing troubles downstream. > > > > There's nothing to research really. Just dump the string suffixes in the > > versions and be happy. They are solving nothing, but create confusion and >

Re: 1.5.final

My tickets: IGNITE-2226 Replace dash in 1.5.0-final with dot 1.5.0.final IGNITE-2175 Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7) Both should be ready today. IGNITE-2116 ignite-osgi-karaf has only readme and license files Waiting

Re: 1.5 GA

re it will not break compatibility with some other case. Raul & Sergi, Could you please check that usage of "." instead of "-" is a good case? On Fri, Dec 18, 2015 at 10:19 AM, Anton Vinogradov wrote: > Yakov, > > ignite-1.5.0-b1-rc1

Re: 1.5 GA

Yakov, ignite-1.5.0-b1-rc1 was correct. 1.5.0-b1 - now correct too, was fixed. Both

Re: 1.5 GA

Raul, Tag 1.5.0-b1 fixed, please check. On Mon, Dec 14, 2015 at 3:59 PM, Raul Kripalani wrote: > On Mon, Dec 14, 2015 at 10:36 AM, Yakov Zhdanov > wrote: > > > osgi has been pushed to 1.5 after b1 has been built. You can build ignite > > binaries from ignite-1.5 branch to test the functionalit

Re: Debug Output in Prod

Yakov, We can simply grep sources for U.debug(), but I'm not sure it helpes. Am I rigth that we have to reconfigure log4j setting each time we want to use U.debug()? On Mon, Dec 14, 2015 at 3:01 PM, Yakov Zhdanov wrote: > Guys, > > I noticed the following code in repo several days > ago(org/apa

[jira] [Created] (IGNITE-2106) BinaryMarshaller: near cache mustn't keep a copy on put() operation

Anton Vinogradov created IGNITE-2106: Summary: BinaryMarshaller: near cache mustn't keep a copy on put() operation Key: IGNITE-2106 URL: https://issues.apache.org/jira/browse/IGNITE-2106 Pr

Re: Update version for branch ignite-1.5

Done On Mon, Dec 7, 2015 at 9:00 PM, Konstantin Boudnik wrote: > If the version is still under development it should be changed to > 1.5.0-b2-SNAPSHOT > > Cos > > On Mon, Dec 07, 2015 at 06:03PM, Sergey Kozlov wrote: > > Hi > > > > Now we released Apache Ignite 1.5.0-b1 and version in branch

Re: Update version for branch ignite-1.5

+1 On Mon, Dec 7, 2015 at 6:03 PM, Sergey Kozlov wrote: > Hi > > Now we released Apache Ignite 1.5.0-b1 and version in branch ignite-1.5 > should changed to 1.5.0-b2 > > Thoughts? > > -- > Sergey Kozlov >

Re: [CLOSE] [VOTE] Apache Ignite 1.5.0-b1

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

Re: Weird releases [Was: EA versioning]

It's a test release. I have no clue why it's located at archive dist. It should be removed. Does anybody know how to remove it? On Mon, Dec 7, 2015 at 7:18 AM, Konstantin Boudnik wrote: > Forking of the release schema conversation. I have noticed that official > dist > http://archive.apache

Re: GridCacheIoManager.processFailedMessage() method

https://issues.apache.org/jira/browse/IGNITE-2079 On Thu, Dec 3, 2015 at 11:26 AM, Yakov Zhdanov wrote: > This method was introduced exactly to prevent cluster from hanging in case > of unexpected problems during message processing. The thing is that the one > who has added new message has not a

[jira] [Created] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case

Anton Vinogradov created IGNITE-2079: Summary: GridCacheIoManager eats exception trail if it falls into the directed case Key: IGNITE-2079 URL: https://issues.apache.org/jira/browse/IGNITE-2079

Re: Build Failure on master branch

h. > but this issue only happens in Windows > > On Thursday, December 3, 2015, Anton Vinogradov > wrote: > > Ken, > > > > I can't understand, did my tip helped? > > > > On Thu, Dec 3, 2015 at 3:11 PM, Ken Cheng wrote: > > > >> HI Anto

Re: Build Failure on master branch

Ken, I can't understand, did my tip helped? On Thu, Dec 3, 2015 at 3:11 PM, Ken Cheng wrote: > HI Anton, > > it's wired, as I did not nothing just try to build the the jar. > > Thanks, > kcheng > > On Thu, Dec 3, 2015 at 8:08 PM, Anton Vinogradov > > wr

Re: Build Failure on master branch

Ken, Seems some other application used files at D:\sandbox\ignite\modules\gce\target\apidocs. Possible it's an Explorer. On Thu, Dec 3, 2015 at 3:04 PM, Ken Cheng wrote: > Hi All, > > Here is my environment details: > > OS : Windows 64 > jdk 1.7 > > here is error message > > > -

Ignite Teamcity update

Igniters, Ingite tests at Teamcity migrated from 'Ignite' project to "Ignite Tests" project. Old project (Ignite) paused now and will be removed next week. Please use "Ignite Tests" project only.

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 many other important feat

Re: EA versioning

Sergi, Is *b1* equals to *beta1* in OSGi case? On Tue, Dec 1, 2015 at 6:38 PM, Dmitriy Setrakyan wrote: > I like “1.5.0-b1”, etc. Let’s use this for now, as it seems to work. > > On Tue, Dec 1, 2015 at 7:27 AM, Sergi Vladykin > wrote: > > > The most promising way which should work for both Mav

Re: EA versioning

stion because I never see EA and RC in one name. Only one > of > > them. > > But seems it is OK to have such name. > > > > On Tue, Dec 1, 2015 at 7:11 PM, Anton Vinogradov < > avinogra...@gridgain.com > > > > > wrote: > > > > > RC means Rel

Re: AWS Tests on TeamCity

Raul, As far as I understand you already have free AWS account. I've got following exception at AWS tests at TeamCity: org.apache.ignite.IgniteCheckedException: The AWS Access Key Id you provided does not exist in our records. Could you please setup your credentials to AWS test at TeamCity. Lin

Re: EA versioning

RC means Release Candidate. After successful vote RC cut from name, and this binary becomes release. On Tue, Dec 1, 2015 at 1:04 PM, Alexey Kuznetsov wrote: > Ok, now I see. > > But just one more question it is possible to add "-vote1" instead "-rc1"? > Or I just do not understand what is abbrev

Re: Publishing readme.io site

uld be > impossible to discern between different platforms within one subdomain. > > Thanks, > > On Tue, Dec 1, 2015 at 12:11 PM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > > Pavel, > > > > I think we should not publish ignite.NET wiki

Re: Publishing readme.io site

Pavel, I think we should not publish ignite.NET wiki at separate domain. Better case is to add .Net (c++, etc ... ) section to https://apacheignite.readme.io/ On Tue, Dec 1, 2015 at 11:35 AM, Pavel Tupitsyn wrote: > It was available, and I have just taken it. > Dmitry, I've added you as an adm

Ignite 1.5 Wiki changed status to Beta.

Igniters, Wiki page https://apacheignite.readme.io/v1.5 now public beta.

Re: OSGi integration ready for review

Raul, I've added 1.6 space as a copy of 1.5. But I gain no results at OSGi search. Could you please specify what pages should be removed from 1.5 or revome them by yourself? On Mon, Nov 30, 2015 at 6:18 PM, Yakov Zhdanov wrote: > Raul, as far as commits - they are mostly fixes for functionality

Re: Optional modules without README and apache license

Raul, Thanks. On Fri, Nov 27, 2015 at 2:54 PM, Raul Kripalani wrote: > On Fri, Nov 27, 2015 at 9:38 AM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > > Raul, we are goin to make release today (4 hours later this email) is it > > possible to push jms11

Re: Optional modules without README and apache license

I'll take care of ignite-kafka readme & all apache-2.0.txt Raul, we are goin to make release today (4 hours later this email) is it possible to push jms11, zk, mqtt changes before this moment? On Thu, Nov 26, 2015 at 11:37 AM, Raul Kripalani wrote: > Yep. I'll take care of jms11, zk, mqtt. > >

Re: Optional modules without README and apache license

Igniters, it's really Important! It's impossible to release 1.5.0 without README.txt files inside modules. Please create them at modules made by you or/and at modules you reviewed. On Wed, Nov 25, 2015 at 5:50 PM, Vasilisa Sidorova wrote: > Dear Igniters, > we have following optional modules w

Re: Ignite-1.5 Release

Twitter intergration *https://issues.apache.org/jira/browse/IGNITE-530 * is done too On Thu, Nov 19, 2015 at 5:32 PM, Semyon Boikov wrote: > Just merged single get optimizations (improvements in the last benchmarks > run: ~10% for atomic-put-get

Re: Javadoc warnings at Ignite 1.5

Engineer > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitter: @raulvk > > On Thu, Nov 19, 2015 at 9:37 AM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > > Raul, > > > > Of course

Re: Javadoc warnings at Ignite 1.5

not abuse the mailing list for details like this. > > Regards, > Raúl. > On 19 Nov 2015 08:49, "Anton Vinogradov" wrote: > >> Hello, >> >> I've checked output of prerelease build of Ignite 1.5 and found javadoc >> warnings like >> CamelStr

Javadoc warnings at Ignite 1.5

Hello, I've checked output of prerelease build of Ignite 1.5 and found javadoc warnings like CamelStreamer.java:51: warning - Tag @link: malformed: "StreamMultipleTupleExtractor)" Raul, seems that was your changes. Could you please fix it?

[jira] [Created] (IGNITE-1924) Uncompleme marshaller cashe rebalancing cause Grid hangs

Anton Vinogradov created IGNITE-1924: Summary: Uncompleme marshaller cashe rebalancing cause Grid hangs Key: IGNITE-1924 URL: https://issues.apache.org/jira/browse/IGNITE-1924 Project: Ignite

[jira] [Created] (IGNITE-1913) Assertion fail cause Grid hangs

Anton Vinogradov created IGNITE-1913: Summary: Assertion fail cause Grid hangs Key: IGNITE-1913 URL: https://issues.apache.org/jira/browse/IGNITE-1913 Project: Ignite Issue Type: Bug

Re: How to build ignite-1.5.0 from source code

Hi Ken, Everything is correct. Version should be changed to 1.5.0 manually. Please check DEVNOTES.txt for release instructions. Quote from DEVNOTES.txt: "Ensure you have RELEASE (not SNAPSHOT) version at Ignite poms. Maven release plugin release:prepare goal can be used to make release tag." O

Work on IGNITE-708 can be continued.

Gianfranco, Need to remove background partition exchange is a very important ticked and it's not blocked by any other tickets at this moment. I will be nice to include this improvement to next release. Let me know in case you heed help or pull req

Re: Rebalancing speedup (IGNITE-1093)

No GC hell happens now at the end of rebalancing. On Tue, Aug 11, 2015 at 11:42 AM, Alexey Kuznetsov wrote: > Anton, I created issues IGNITE-1230 and IGNITE-1231 and linked them to > https://issues.apache.org/jira/browse/IGNITE-1093. > > On Tue, Aug 11, 2015 at 3:31 PM

Re: Ignite-1.5 Release

Branch ignite-1.5 created. On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov wrote: > I assume that correct link at 10th feature is > https://issues.apache.org/jira/browse/IGNITE-638 > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov wrote: > >> Guys, >> >> I

Re: Ignite-1.5 Release

I assume that correct link at 10th feature is https://issues.apache.org/jira/browse/IGNITE-638 On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov wrote: > Guys, > > I think we can start preparation to Ignite-1.5 release which will include > many interesting features: > > 1. Portable object API > http

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

+1 (binding) On Wed, Oct 14, 2015 at 4:47 PM, Gianfranco Murador wrote: > +1 (binding) > > 2015-10-14 15:46 GMT+02:00 Yakov Zhdanov : > > > +1 (binding) > > > > --Yakov > > > > 2015-10-14 1:30 GMT+03:00 Konstantin Boudnik : > > > > > Hi! > > > > > > As discussed in the "[DISCUSS] PMC Chair rotat

Re: Name of .Net product

+1 Ignite.NET On Wed, Oct 7, 2015 at 4:27 PM, chandresh pancholi < chandreshpancholi...@gmail.com> wrote: > What abount "Ignite DotN". > > On Wed, Oct 7, 2015 at 6:54 PM, Sergi Vladykin > wrote: > > > I like "Ignite.NET". > > > > Sergi > > > > 2015-10-07 15:04 GMT+03:00 Vladimir Ozerov : > > > >

Re: 'Implement IgniteSemaphore data structure' Review

equest is not mentioned in the ticket? Also, the > ticket should be moved to the Patch Available state, right? > > D. > > On Fri, Oct 2, 2015 at 10:19 AM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > > Val, > > > > Vladisav prepared pull re

Re: 'How to Contribute' wiki page updated.

e > whole > TC suite passes. > > Raul, it would be nice if you could also take a look and provide comments. > > Thanks, > D. > > On Mon, Oct 5, 2015 at 7:36 AM, Anton Vinogradov wrote: > > > Igniters, > > > > https://cwiki.apache.org/confluence/dis

'How to Contribute' wiki page updated.

Igniters, https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute page updated. Changes: 1) Jira process and Git process becomes part of How to Contribute . 2) Added 'Ticket Branch' case (only for committers). 3) F

[jira] [Created] (IGNITE-1612) Do not upload ignite-apache-license-gen to maven

Anton Vinogradov created IGNITE-1612: Summary: Do not upload ignite-apache-license-gen to maven Key: IGNITE-1612 URL: https://issues.apache.org/jira/browse/IGNITE-1612 Project: Ignite

[jira] [Created] (IGNITE-1611) [Test Failed] GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit

Anton Vinogradov created IGNITE-1611: Summary: [Test Failed] GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit Key: IGNITE-1611 URL: https://issues.apache.org/jira/browse/IGNITE

Re: Fwd: Coding Guidelines: zookeeper IP finder and mqtt streamer

Raul, I've fixed most of TODOs you created. Seems that indentation policy with multi-line parameter descriptions already defined: "multiline comments in Javadoc tags should be indented by 4 or 5 characters ...". Please check my changes: https://cwiki.apache.org/confluence/pages/diffpagesbyversion

'Implement IgniteSemaphore data structure' Review

Val, Vladisav prepared pull request related to Implement IgniteSemaphore data structure . Pull request seems to be ready for review. Could you please review it? PR url: https://github.com/apache/ignite/pull/120

<    4   5   6   7   8   9   10   >