Re: Ignite 1.5 plans

While a minor modification which won't affect anything, I'd like to put on the table the consolidation of hadoodp and spark bits into ignite-accelerator assembly. The fix is ready and I was just waiting for 1.4 to come out. Cos On September 28, 2015 11:11:44 AM PDT, Vladimir Ozerov

Re: Write Access To Wiki

On Mon, Sep 28, 2015 at 6:53 PM, Yakov Zhdanov wrote: > I think any contribution should require ICLA. Moreover, it is not a big > deal :) > Is this the case for other projects? Can some in the community who have experience with other Apache projects voice their opinion

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

Congrats! Well timed to @ApacheCon too! Please make sure to do the announcement cc'ed to annou...@apache.org Thanks Cos On September 28, 2015 4:09:25 PM CEST, Anton Vinogradov wrote: >Ignite 1.4.0 successfuly released to

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

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) -

Re: Write Access To Wiki

At Camel we make all Wiki contributors sign an ICLA. But then again, our docs are an export of the Wiki, so it's slightly different to Ignite's case. Since having a Wiki account enables you to make know-how contributions to the ASF (potentially intellectual property) I would get all Wiki users to

Re: Ignite 1.5 plans

I would like to add one more: 10. OSGI integration - Raul Kripalani Raul, hopefully you will have time to finish it. Also, if anyone in the community wants to propose a feature they are working on which can be finished within next couple of weeks, it should get into 1.5 as well. D. On Mon, Sep

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? 2) HP-UX users are also concerned, see last comments in https://issues.apache.org/jira/browse/IGNITE-1493 I think we must adress

Re: Switched main version to 1.4 on readme.io

This news needs a tweet !! :) 2015-09-28 15:24 GMT+02:00 Yakov Zhdanov : > subj > > --Yakov > -- Gianfranco Murador Igniter and Software Engineer.

Re: Ignite 1.5 plans

Yes for OSGi. And I think a Camel-based streamer would also be valuable, as it would allow us to consume messages from any technology supported by Camel. Raúl. On 28 Sep 2015 17:50, "Dmitriy Setrakyan" wrote: > I would like to add one more: > 10. OSGI integration - Raul

Fwd: Coding Guidelines: zookeeper IP finder and mqtt streamer

Cos, your language seems too harsh for the situation. No one here is committing negligence. The explanation is simple: people aren't perfect. Now, let's take a step back and see the big picture. Around 95% of the commits in this project are by GridGain personnel (check git shortlog -s -n) who

Write Access To Wiki

For IGNITE-815 I want to add design document in wiki (wiki.apache.org). So, I need write access to Ignite space. Anyone please give me write access. My user name is lalitj

Re: Write Access To Wiki

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 code.", so I guess the answer is yes. [1]

Re: Coding Guidelines: zookeeper IP finder and mqtt streamer

Raul, I still think it is valid to have a peer review and if someone is trying and spending time to keep code style consistent, it is a good thing. And It should not matter who gets to fixing the style issues until we have check styles or a much improved process for reviewing. Code review

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

Ignite 1.4.0 successfuly released to https://dist.apache.org/repos/dist/release/ignite/1.4.0/ Site will be updated soon. On Mon, Sep 28, 2015 at 4:13 PM, Yakov Zhdanov wrote: > Hello! > > Apache Ignite 1.4.0 release (RC1) has been accepted. > > 9 "+1" votes received. > >

[jira] [Created] (IGNITE-1557) 1.4 release, licenses.txt broken

Anton Vinogradov created IGNITE-1557: Summary: 1.4 release, licenses.txt broken Key: IGNITE-1557 URL: https://issues.apache.org/jira/browse/IGNITE-1557 Project: Ignite Issue Type: Bug

Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)

I'll fix found bugs. https://issues.apache.org/jira/browse/IGNITE-1557 https://issues.apache.org/jira/browse/IGNITE-1558 On Mon, Sep 28, 2015 at 4:30 AM, Dmitriy Setrakyan wrote: > Thanks Raul, > > Any chance you can file a ticket describing this issue? > > D. > > On Sat,

[jira] [Created] (IGNITE-1558) 1.4 release, igniterouter scripts problems

Anton Vinogradov created IGNITE-1558: Summary: 1.4 release, igniterouter scripts problems Key: IGNITE-1558 URL: https://issues.apache.org/jira/browse/IGNITE-1558 Project: Ignite Issue

Re: new committer and PMC member: Denis Magda

Welcome Denis! Good to have you on board! On Sun, Sep 27, 2015 at 06:17PM, Dmitriy Setrakyan wrote: > The Project Management Committee (PMC) for Apache Ignite has asked Denis > Magda to become a committer and PMC member and we are pleased to announce > that Denis has accepted. > > Being a

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

Re: version names

On Sun, Sep 27, 2015 at 11:11PM, Yakov Zhdanov wrote: > I am ok with jira version renaming. > > However, tag name "ignite-1.4.0-rc1" was created automatically, and > changing this will lead to lots of changes inside. We leave this as is. > Correct? > > Tags like "1.3.3-p3" should be just

Re: After setting streamer and ignite,getting NULL

Chandresh, I think that the suggestion of Roman is preferable, we can use the following code : Let me know if you have problems /** Start a simulated topology */ public void startTopology(StormStreamer stormStreamer) { MkClusterParam mkClusterParam = new MkClusterParam();

Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)

Raul, thanks! Closed my issue as duplicate. On Mon, Sep 28, 2015 at 11:44 AM, Raul Kripalani wrote: > Hey Anton, > > I had already fixed the igniterouter scripts: > https://issues.apache.org/jira/browse/IGNITE-1554 > > On both 1.4 and master. > > Regards, > Raúl. > On 28 Sep

Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)

Hey Anton, I had already fixed the igniterouter scripts: https://issues.apache.org/jira/browse/IGNITE-1554 On both 1.4 and master. Regards, Raúl. On 28 Sep 2015 08:48, "Anton Vinogradov" wrote: > I'll fix found bugs. >

Re: Coding Guidelines: zookeeper IP finder and mqtt streamer

Yakov, I think it is best to provide the code review comments in the Jira ticket, and not here. Also, Jira ticket has information on who authored the code as well (don't think we should be calling names out on the dev list). Can you please reopen the ticket and provide the link to this

Re: Ignite 1.5 plans

Yep but I'm struggling imagining that component living in the Apache Ignite repo. It should be hosted in Camel as a Camel component with consumers and producers, and making extensive use of Camel APIs. However, at the same time I don't like splitting the integration half here and half there.

Re: Write Access To Wiki

Lalit, Sounds like you will have to sign the ICLA. Generally, it's not a bad thing, as it will be one less thing you have to do when becoming a committer. Here are the instructions: http://www.apache.org/dev/new-committers-guide.html#cla Just fill it out and send it to secret...@apache.org.

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

Cos, I think Raul's point was that coding guidelines are not very clear. I think Raul thought that he was following the coding guidelines. I don't think "negligence" is a fair word to describe this. In my view, we have a couple of omissions in the process on Wiki that need to be spelled out

Re: Ignite 1.5 plans

On Mon, Sep 28, 2015 at 10:20 PM, Raul Kripalani wrote: > Yes for OSGi. > > And I think a Camel-based streamer would also be valuable, as it would > allow us to consume messages from any technology supported by Camel. > I like the idea. Does the reverse integration make sense

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

Hmm... Negligence, n. : the trait of neglecting responsibilities and lacking concern syn : omission, oversight Doesn't sound catastrophic in my vocabulary, really. Does this > case of negligence and needs to be addressed accordingly. translate to "should face a firing squad without a trial of

Re: Ignite 1.5 plans

On Tue, Sep 29, 2015 at 12:33 AM, Raul Kripalani wrote: > Yep but I'm struggling imagining that component living in the Apache Ignite > repo. It should be hosted in Camel as a Camel component with consumers and > producers, and making extensive use of Camel APIs. > > However,

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

There has been no negligence, Cos! People are human and make mistakes. End of the story. Bringing such negative verbiage to the community helps in nothing. Everybody is doing their best, I'd like to think so. In fact, you have shifted the conversation away from the actual topic at hand. So

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

One more point about empty lines. I have reviewed our empty line policy and I don't think I can do a better job describing it. The explanation is pretty accurate. However, the main problem with our empty line policy is that, although the resulting code looks very neat, the policy is just too

[jira] [Created] (IGNITE-1560) ClassNotFoundException on AWS

Alexandre Boudnik created IGNITE-1560: - Summary: ClassNotFoundException on AWS Key: IGNITE-1560 URL: https://issues.apache.org/jira/browse/IGNITE-1560 Project: Ignite Issue Type: Bug

Re: Coding Guidelines: zookeeper IP finder and mqtt streamer

Are these official guidelines that are worked-out and communicated by community? Basically, were they made clear when the project went on the CTR model? I presume it is/was looking at the wikipage. Hence non-sticking to them is a case of negligence and needs to be addressed accordingly. I would

Switched main version to 1.4 on readme.io

subj --Yakov

Re: Coding Guidelines: zookeeper IP finder and mqtt streamer

Hey guys, I have little time now, but before this discussion escalates... #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: Commit: 88acd318b84ce3bff8c061bb34718e0e5f7127fb

[GitHub] ignite pull request: IGNITE-429: Implement IgniteStormStreamer to ...

Github user murador closed the pull request at: https://github.com/apache/ignite/pull/107 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[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

[GitHub] ignite pull request: Ignite 429: Implement IgniteStormStreamer to ...

GitHub user murador opened a pull request: https://github.com/apache/ignite/pull/109 Ignite 429: Implement IgniteStormStreamer to stream data from Apache Storm The test was successful with the latest changes, we use a simulated topology. The operation of the stream is different

[GitHub] ignite pull request: Ignite 429: Implement IgniteStormStreamer to ...

Github user murador closed the pull request at: https://github.com/apache/ignite/pull/109 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Coding Guidelines: zookeeper IP finder and mqtt streamer

Agree about checkstyle. I myself do mistakes even after more than 3 years on this code base. Checkstyle is a nice tool, works for many IDEs. For example H2 database requires incoming patches to conform provided checkstyle config, I use it right from Eclipse. Sergi 2015-09-28 16:25 GMT+03:00 Raul