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
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 Typ
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, Sep 26, 2015 at 3:16 AM
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.
> https://issues.apache.org/jira/browse/IGNITE-1557
> https://issues.apache.o
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 2015 08:48, "Anton
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();
mk
Gian,
Lets use this and modify our tests. I will push the code by tomorrow EOD.
Thanks
Chandresh Pancholi
On Mon, Sep 28, 2015 at 3:58 PM, Gianfranco Murador <
murador.gianfra...@gmail.com> wrote:
> Chandresh,
> I think that the suggestion of Roman is preferable, we can use the
> following c
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
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 committ
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 removed.
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 al
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
subj
--Yakov
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 [88ac
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 ena
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 com
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 ena
GitHub user murador opened a pull request:
https://github.com/apache/ignite/pull/110
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 com
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
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.
>
> Here are the votes recei
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 hav
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 comm
Site updated.
On Mon, Sep 28, 2015 at 5:09 PM, Anton Vinogradov
wrote:
> 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
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
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]
http://apache-ignite-developers.2346864.n4.nabble.com/Documentation-by-contributors-td2623.html#a2659
This news needs a tweet !! :)
2015-09-28 15:24 GMT+02:00 Yakov Zhdanov :
> subj
>
> --Yakov
>
--
Gianfranco Murador
Igniter and Software Engineer.
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
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
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
On Mon, Sep 28, 2015 at 6:42 PM, Gianfranco Murador
wrote:
> This news needs a tweet !! :)
>
Tweets are nice, but blogs are better :) I want to encourage everyone to
blog about Ignite. I am working on a blog myself right now.
>
>
> 2015-09-28 15:24 GMT+02:00 Yakov Zhdanov :
>
> > subj
> >
> >
I would like to propose the integration with JBPM ,
I think I can finish in a couple of weeks since I have a bit of time to
devote to Ignite.
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 - Rau
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 here?
>
> --Yakov
>
> 20
Gianfranco,
I am not too familiar with JBPM. Can you make a case on why we may need
this integration and how it will benefit Ignite users?
Thanks,
D.
On Mon, Sep 28, 2015 at 6:56 PM, Gianfranco Murador
wrote:
> I would like to propose the integration with JBPM ,
> I think I can finish in a co
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
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
>https://dist.apache.org/repos/dist/release/ignite/1.4.0/
>Site will b
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
Unsafe
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 Kripalani
>
> Raul, hope
Artem Shutak created IGNITE-1559:
Summary: Need to improve tests, javadoc and documentation of
UriDeploymentHttpScanner.
Key: IGNITE-1559
URL: https://issues.apache.org/jira/browse/IGNITE-1559
Project
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 as well, i.e.
allow
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. When
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 discussion
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. Dilem
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 his
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, at the same time I d
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 clear
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 thanks
On Tue, Sep 29, 2015 at 12:49 AM, Dmitriy Setrakyan wrote:
> 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 cou
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 compl
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
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
wrote:
>I
Hi Igniters
I found the intersting article:
http://blogs.technet.com/b/wincat/archive/2012/12/05/fast-tcp-loopback-performance-and-low-latency-with-windows-server-2012-tcp-loopback-fast-path.aspx
Could someone take a look how to difficult to implement it for Ignite?
--
Sergey Kozlov
On Tue, Sep 29, 2015 at 7:40 AM, Konstantin Boudnik wrote:
> 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.
>
I
Gian,
is code for ignite-429 in master branch?
On Mon, Sep 28, 2015 at 5:27 PM, chandresh pancholi <
chandreshpancholi...@gmail.com> wrote:
> Gian,
>
> Lets use this and modify our tests. I will push the code by tomorrow EOD.
>
> Thanks
> Chandresh Pancholi
>
> On Mon, Sep 28, 2015 at 3:58 PM, G
Semen Boikov created IGNITE-1561:
Summary: Cross cache tx tests with near cache fail with asserts
Key: IGNITE-1561
URL: https://issues.apache.org/jira/browse/IGNITE-1561
Project: Ignite
Issue
54 matches
Mail list logo
