Apache Ignite Developers - Legacy Mail Archive

Ignite 1.5 plans

Classic

List

Threaded

28 messages Options

yzhdanov

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) - Vladimir Ozerov
3. Portable API release - Denis Magda and Vladimir
4. Failover for continuous query notifications - Nick Tikhonov
5. Cache Rebalancing optimizations - Anton Vinogradov
6. Fix compatibility with IBM JDK
7. Cache stability and performance fixes (as many as possible)

Nice to have:
8. Finish vert.x integration - Andrey Gura works on this.
9. Finish node.js integration - I think Semyon should pass it over to
someone else, given he is busy with cache. Anyone? Andrey Gura?

Comments are welcome!

[1] https://issues.apache.org/jira/browse/IGNITE-950
[2] https://issues.apache.org/jira/browse/IGNITE-1282
[3] https://issues.apache.org/jira/browse/IGNITE-1258
[4] https://issues.apache.org/jira/browse/IGNITE-426
[5] https://issues.apache.org/jira/browse/IGNITE-1093
[5] https://issues.apache.org/jira/browse/IGNITE-324
[6] https://issues.apache.org/jira/browse/IGNITE-1526
[7] https://issues.apache.org/jira/browse/IGNITE-1345
[8] https://issues.apache.org/jira/browse/IGNITE-1079
[9] https://issues.apache.org/jira/browse/IGNITE-961

--Yakov

dsetrakyan

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 28, 2015 at 6:43 PM, Yakov Zhdanov <[hidden email]> wrote:

> 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) - Vladimir Ozerov
> 3. Portable API release - Denis Magda and Vladimir
> 4. Failover for continuous query notifications - Nick Tikhonov
> 5. Cache Rebalancing optimizations - Anton Vinogradov
> 6. Fix compatibility with IBM JDK
> 7. Cache stability and performance fixes (as many as possible)
>
> Nice to have:
> 8. Finish vert.x integration - Andrey Gura works on this.
> 9. Finish node.js integration - I think Semyon should pass it over to
> someone else, given he is busy with cache. Anyone? Andrey Gura?
>
> Comments are welcome!
>
> [1] https://issues.apache.org/jira/browse/IGNITE-950
> [2] https://issues.apache.org/jira/browse/IGNITE-1282
> [3] https://issues.apache.org/jira/browse/IGNITE-1258
> [4] https://issues.apache.org/jira/browse/IGNITE-426
> [5] https://issues.apache.org/jira/browse/IGNITE-1093
> [5] https://issues.apache.org/jira/browse/IGNITE-324
> [6] https://issues.apache.org/jira/browse/IGNITE-1526
> [7] https://issues.apache.org/jira/browse/IGNITE-1345
> [8] https://issues.apache.org/jira/browse/IGNITE-1079
> [9] https://issues.apache.org/jira/browse/IGNITE-961
>
> --Yakov
>

Gianfranco Murador-2

Re: Ignite 1.5 plans

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 <[hidden email]>:

> 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 28, 2015 at 6:43 PM, Yakov Zhdanov <[hidden email]>
> wrote:
>
> > 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) - Vladimir Ozerov
> > 3. Portable API release - Denis Magda and Vladimir
> > 4. Failover for continuous query notifications - Nick Tikhonov
> > 5. Cache Rebalancing optimizations - Anton Vinogradov
> > 6. Fix compatibility with IBM JDK
> > 7. Cache stability and performance fixes (as many as possible)
> >
> > Nice to have:
> > 8. Finish vert.x integration - Andrey Gura works on this.
> > 9. Finish node.js integration - I think Semyon should pass it over to
> > someone else, given he is busy with cache. Anyone? Andrey Gura?
> >
> > Comments are welcome!
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-950
> > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> > [4] https://issues.apache.org/jira/browse/IGNITE-426
> > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> > [5] https://issues.apache.org/jira/browse/IGNITE-324
> > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> > [9] https://issues.apache.org/jira/browse/IGNITE-961
> >
> > --Yakov
> >
>

--
Gianfranco Murador
Igniter and Software Engineer.

dsetrakyan

Re: Ignite 1.5 plans

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 <[hidden email]>
wrote:

> 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 <[hidden email]>:
>
> > 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 28, 2015 at 6:43 PM, Yakov Zhdanov <[hidden email]>
> > wrote:
> >
> > > 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) - Vladimir Ozerov
> > > 3. Portable API release - Denis Magda and Vladimir
> > > 4. Failover for continuous query notifications - Nick Tikhonov
> > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> > > 6. Fix compatibility with IBM JDK
> > > 7. Cache stability and performance fixes (as many as possible)
> > >
> > > Nice to have:
> > > 8. Finish vert.x integration - Andrey Gura works on this.
> > > 9. Finish node.js integration - I think Semyon should pass it over to
> > > someone else, given he is busy with cache. Anyone? Andrey Gura?
> > >
> > > Comments are welcome!
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> > >
> > > --Yakov
> > >
> >
>
>
>
> --
> Gianfranco Murador
> Igniter and Software Engineer.
>

Vladimir Ozerov

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
Unsafe refactoring in this release as well.

On Mon, Sep 28, 2015 at 7:57 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> 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 <[hidden email]>
> wrote:
>
> > 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 <[hidden email]>:
> >
> > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov <[hidden email]>
> > > wrote:
> > >
> > > > 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) - Vladimir Ozerov
> > > > 3. Portable API release - Denis Magda and Vladimir
> > > > 4. Failover for continuous query notifications - Nick Tikhonov
> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> > > > 6. Fix compatibility with IBM JDK
> > > > 7. Cache stability and performance fixes (as many as possible)
> > > >
> > > > Nice to have:
> > > > 8. Finish vert.x integration - Andrey Gura works on this.
> > > > 9. Finish node.js integration - I think Semyon should pass it over to
> > > > someone else, given he is busy with cache. Anyone? Andrey Gura?
> > > >
> > > > Comments are welcome!
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> > > >
> > > > --Yakov
> > > >
> > >
> >
> >
> >
> > --
> > Gianfranco Murador
> > Igniter and Software Engineer.
> >
>

Raul Kripalani-2

Re: Ignite 1.5 plans

In reply to this post by dsetrakyan

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" <[hidden email]> wrote:

dsetrakyan

Re: Ignite 1.5 plans

On Mon, Sep 28, 2015 at 10:20 PM, Raul Kripalani <[hidden email]> 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.
allowing Camel to consume Ignite messages?

>
> Raúl.
> On 28 Sep 2015 17:50, "Dmitriy Setrakyan" <[hidden email]> wrote:
>
> > 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 28, 2015 at 6:43 PM, Yakov Zhdanov <[hidden email]>
> > wrote:
> >
> > > 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) - Vladimir Ozerov
> > > 3. Portable API release - Denis Magda and Vladimir
> > > 4. Failover for continuous query notifications - Nick Tikhonov
> > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> > > 6. Fix compatibility with IBM JDK
> > > 7. Cache stability and performance fixes (as many as possible)
> > >
> > > Nice to have:
> > > 8. Finish vert.x integration - Andrey Gura works on this.
> > > 9. Finish node.js integration - I think Semyon should pass it over to
> > > someone else, given he is busy with cache. Anyone? Andrey Gura?
> > >
> > > Comments are welcome!
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> > >
> > > --Yakov
> > >
> >
>

Raul Kripalani-2

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. Dilemma.

Ideas welcome.
On 28 Sep 2015 23:22, "Dmitriy Setrakyan" <[hidden email]> wrote:

> On Mon, Sep 28, 2015 at 10:20 PM, Raul Kripalani <[hidden email]> 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.
> allowing Camel to consume Ignite messages?
>
>
> >
> > Raúl.
> > On 28 Sep 2015 17:50, "Dmitriy Setrakyan" <[hidden email]> wrote:
> >
> > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov <[hidden email]>
> > > wrote:
> > >
> > > > 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) - Vladimir Ozerov
> > > > 3. Portable API release - Denis Magda and Vladimir
> > > > 4. Failover for continuous query notifications - Nick Tikhonov
> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> > > > 6. Fix compatibility with IBM JDK
> > > > 7. Cache stability and performance fixes (as many as possible)
> > > >
> > > > Nice to have:
> > > > 8. Finish vert.x integration - Andrey Gura works on this.
> > > > 9. Finish node.js integration - I think Semyon should pass it over to
> > > > someone else, given he is busy with cache. Anyone? Andrey Gura?
> > > >
> > > > Comments are welcome!
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> > > >
> > > > --Yakov
> > > >
> > >
> >
>

dsetrakyan

Re: Ignite 1.5 plans

On Tue, Sep 29, 2015 at 12:33 AM, Raul Kripalani <[hidden email]> 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 don't like splitting the integration half here
> and half there. Dilemma.

I also think it should be in Camel, however streamer can be in Ignite for
consistency with other streamers. I see your point, but I think it is
proper structure: camel->ignite integration in camel, and ignite->camel
integration in ignite, no?

>
> Ideas welcome.
> On 28 Sep 2015 23:22, "Dmitriy Setrakyan" <[hidden email]> wrote:
>
> > On Mon, Sep 28, 2015 at 10:20 PM, Raul Kripalani <[hidden email]>
> 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.
> > allowing Camel to consume Ignite messages?
> >
> >
> > >
> > > Raúl.
> > > On 28 Sep 2015 17:50, "Dmitriy Setrakyan" <[hidden email]>
> wrote:
> > >
> > > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov <[hidden email]>
> > > > wrote:
> > > >
> > > > > 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) - Vladimir Ozerov
> > > > > 3. Portable API release - Denis Magda and Vladimir
> > > > > 4. Failover for continuous query notifications - Nick Tikhonov
> > > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> > > > > 6. Fix compatibility with IBM JDK
> > > > > 7. Cache stability and performance fixes (as many as possible)
> > > > >
> > > > > Nice to have:
> > > > > 8. Finish vert.x integration - Andrey Gura works on this.
> > > > > 9. Finish node.js integration - I think Semyon should pass it over
> to
> > > > > someone else, given he is busy with cache. Anyone? Andrey Gura?
> > > > >
> > > > > Comments are welcome!
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> > > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> > > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> > > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> > > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> > > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> > > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> > > > >
> > > > > --Yakov
> > > > >
> > > >
> > >
> >
>

Konstantin Boudnik-2

Re: Ignite 1.5 plans

In reply to this post by Vladimir Ozerov

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 <[hidden email]> wrote:

>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 refactoring in this release as well.
>
>On Mon, Sep 28, 2015 at 7:57 PM, Dmitriy Setrakyan
><[hidden email]>
>wrote:
>
>> 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
><[hidden email]>
>> wrote:
>>
>> > 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
><[hidden email]>:
>> >
>> > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov
><[hidden email]>
>> > > wrote:
>> > >
>> > > > 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) - Vladimir Ozerov
>> > > > 3. Portable API release - Denis Magda and Vladimir
>> > > > 4. Failover for continuous query notifications - Nick Tikhonov
>> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
>> > > > 6. Fix compatibility with IBM JDK
>> > > > 7. Cache stability and performance fixes (as many as possible)
>> > > >
>> > > > Nice to have:
>> > > > 8. Finish vert.x integration - Andrey Gura works on this.
>> > > > 9. Finish node.js integration - I think Semyon should pass it
>over to
>> > > > someone else, given he is busy with cache. Anyone? Andrey Gura?
>> > > >
>> > > > Comments are welcome!
>> > > >
>> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
>> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
>> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
>> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
>> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
>> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
>> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
>> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
>> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
>> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
>> > > >
>> > > > --Yakov
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Gianfranco Murador
>> > Igniter and Software Engineer.
>> >
>>

dsetrakyan

Re: Ignite 1.5 plans

On Tue, Sep 29, 2015 at 7:40 AM, Konstantin Boudnik <[hidden email]> 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 like the idea. However ignite-accelerator does not seem like a right
name. Any other candidates?

>
> Cos
>
> On September 28, 2015 11:11:44 AM PDT, Vladimir Ozerov <
> [hidden email]> wrote:
> >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 refactoring in this release as well.
> >
> >On Mon, Sep 28, 2015 at 7:57 PM, Dmitriy Setrakyan
> ><[hidden email]>
> >wrote:
> >
> >> 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
> ><[hidden email]>
> >> wrote:
> >>
> >> > 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
> ><[hidden email]>:
> >> >
> >> > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov
> ><[hidden email]>
> >> > > wrote:
> >> > >
> >> > > > 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) - Vladimir Ozerov
> >> > > > 3. Portable API release - Denis Magda and Vladimir
> >> > > > 4. Failover for continuous query notifications - Nick Tikhonov
> >> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> >> > > > 6. Fix compatibility with IBM JDK
> >> > > > 7. Cache stability and performance fixes (as many as possible)
> >> > > >
> >> > > > Nice to have:
> >> > > > 8. Finish vert.x integration - Andrey Gura works on this.
> >> > > > 9. Finish node.js integration - I think Semyon should pass it
> >over to
> >> > > > someone else, given he is busy with cache. Anyone? Andrey Gura?
> >> > > >
> >> > > > Comments are welcome!
> >> > > >
> >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> >> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> >> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> >> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> >> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> >> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> >> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> >> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> >> > > >
> >> > > > --Yakov
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Gianfranco Murador
> >> > Igniter and Software Engineer.
> >> >
> >>
>

yzhdanov

Re: Ignite 1.5 plans

In reply to this post by Vladimir Ozerov

> 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 last comments in
> https://issues.apache.org/jira/browse/IGNITE-1493 I think we must adress
> Unsafe refactoring in this release as well.

Well, this is a bit more complex, but let's see if it fits

Gianfranco Murador-2

Re: Ignite 1.5 plans

In reply to this post by dsetrakyan

Dmitry,
The short answer is because JBPM is integrated well with Infinispan,the
longest and technically correct answer is as follows.

JBPM is now used in many productions of the clients they serve a high
number of users.The main problem with the engine of business processes
resides in the non- synchronicity of the workflow, ie the workflow goes
forward based on the working times of the employees, so it is possible that
a workflow ends within a few days. Maintain an instance of a workflow in
the database and retrieve it each time it is expensive in terms of time, we
might have many workflow latches.The idea is to allow to save in cache the
entire instance of a workflow in order to make the most rapid recovery
possible.

There are also rapid workflows where the use of a cache is very
interesting, for example, a job stream must be recovered and carried
forward in a few second (for example,at a bank office). The idea is to
create a grid of instances of workflows to allow recovery quickly.

The idea has already been implemented for Infinispan, but is not very
advanced.

https://github.com/droolsjbpm/droolsjbpm-integration/tree/master/kie-infinispan/jbpm-infinispan-persistence/src/main/java/org/jbpm/persistence

Regards,
Gianfranco.

2015-09-28 18:57 GMT+02:00 Dmitriy Setrakyan <[hidden email]>:

--
Gianfranco Murador
Igniter and Software Engineer.

Konstantin Boudnik-2

Re: Ignite 1.5 plans

In reply to this post by dsetrakyan

how about
ignite-booster

or something?
Cos

On Tue, Sep 29, 2015 at 08:33AM, Dmitriy Setrakyan wrote:

> On Tue, Sep 29, 2015 at 7:40 AM, Konstantin Boudnik <[hidden email]> 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 like the idea. However ignite-accelerator does not seem like a right
> name. Any other candidates?
>
>
> >
> > Cos
> >
> > On September 28, 2015 11:11:44 AM PDT, Vladimir Ozerov <
> > [hidden email]> wrote:
> > >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 refactoring in this release as well.
> > >
> > >On Mon, Sep 28, 2015 at 7:57 PM, Dmitriy Setrakyan
> > ><[hidden email]>
> > >wrote:
> > >
> > >> 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
> > ><[hidden email]>
> > >> wrote:
> > >>
> > >> > 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
> > ><[hidden email]>:
> > >> >
> > >> > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov
> > ><[hidden email]>
> > >> > > wrote:
> > >> > >
> > >> > > > 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) - Vladimir Ozerov
> > >> > > > 3. Portable API release - Denis Magda and Vladimir
> > >> > > > 4. Failover for continuous query notifications - Nick Tikhonov
> > >> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> > >> > > > 6. Fix compatibility with IBM JDK
> > >> > > > 7. Cache stability and performance fixes (as many as possible)
> > >> > > >
> > >> > > > Nice to have:
> > >> > > > 8. Finish vert.x integration - Andrey Gura works on this.
> > >> > > > 9. Finish node.js integration - I think Semyon should pass it
> > >over to
> > >> > > > someone else, given he is busy with cache. Anyone? Andrey Gura?
> > >> > > >
> > >> > > > Comments are welcome!
> > >> > > >
> > >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> > >> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> > >> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> > >> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> > >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> > >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> > >> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> > >> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> > >> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> > >> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> > >> > > >
> > >> > > > --Yakov
> > >> > > >
> > >> > >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Gianfranco Murador
> > >> > Igniter and Software Engineer.
> > >> >
> > >>
> >

Konstantin Boudnik-2

Re: Ignite 1.5 plans

Here's the link to the JIRA just in case
https://issues.apache.org/jira/browse/IGNITE-1555

On Tue, Sep 29, 2015 at 03:17AM, Konstantin Boudnik wrote:

> how about
> ignite-booster
>
> or something?
> Cos
>
> On Tue, Sep 29, 2015 at 08:33AM, Dmitriy Setrakyan wrote:
> > On Tue, Sep 29, 2015 at 7:40 AM, Konstantin Boudnik <[hidden email]> 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 like the idea. However ignite-accelerator does not seem like a right
> > name. Any other candidates?
> >
> >
> > >
> > > Cos
> > >
> > > On September 28, 2015 11:11:44 AM PDT, Vladimir Ozerov <
> > > [hidden email]> wrote:
> > > >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 refactoring in this release as well.
> > > >
> > > >On Mon, Sep 28, 2015 at 7:57 PM, Dmitriy Setrakyan
> > > ><[hidden email]>
> > > >wrote:
> > > >
> > > >> 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
> > > ><[hidden email]>
> > > >> wrote:
> > > >>
> > > >> > 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
> > > ><[hidden email]>:
> > > >> >
> > > >> > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov
> > > ><[hidden email]>
> > > >> > > wrote:
> > > >> > >
> > > >> > > > 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) - Vladimir Ozerov
> > > >> > > > 3. Portable API release - Denis Magda and Vladimir
> > > >> > > > 4. Failover for continuous query notifications - Nick Tikhonov
> > > >> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> > > >> > > > 6. Fix compatibility with IBM JDK
> > > >> > > > 7. Cache stability and performance fixes (as many as possible)
> > > >> > > >
> > > >> > > > Nice to have:
> > > >> > > > 8. Finish vert.x integration - Andrey Gura works on this.
> > > >> > > > 9. Finish node.js integration - I think Semyon should pass it
> > > >over to
> > > >> > > > someone else, given he is busy with cache. Anyone? Andrey Gura?
> > > >> > > >
> > > >> > > > Comments are welcome!
> > > >> > > >
> > > >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> > > >> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> > > >> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> > > >> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> > > >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> > > >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> > > >> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> > > >> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> > > >> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> > > >> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> > > >> > > >
> > > >> > > > --Yakov
> > > >> > > >
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Gianfranco Murador
> > > >> > Igniter and Software Engineer.
> > > >> >
> > > >>
> > >

dsetrakyan

Re: Ignite 1.5 plans

On Tue, Sep 29, 2015 at 1:44 PM, Konstantin Boudnik <[hidden email]> wrote:

> Here's the link to the JIRA just in case
> https://issues.apache.org/jira/browse/IGNITE-1555

Would be great if someone in the community could review the patch.

Also, Cos, can you please change the ticket to "Patch Available"?

D.

>
>
>
> On Tue, Sep 29, 2015 at 03:17AM, Konstantin Boudnik wrote:
> > how about
> > ignite-booster
> >
> > or something?
> > Cos
> >
> > On Tue, Sep 29, 2015 at 08:33AM, Dmitriy Setrakyan wrote:
> > > On Tue, Sep 29, 2015 at 7:40 AM, Konstantin Boudnik <[hidden email]>
> 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 like the idea. However ignite-accelerator does not seem like a right
> > > name. Any other candidates?
> > >
> > >
> > > >
> > > > Cos
> > > >
> > > > On September 28, 2015 11:11:44 AM PDT, Vladimir Ozerov <
> > > > [hidden email]> wrote:
> > > > >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 refactoring in this release as well.
> > > > >
> > > > >On Mon, Sep 28, 2015 at 7:57 PM, Dmitriy Setrakyan
> > > > ><[hidden email]>
> > > > >wrote:
> > > > >
> > > > >> 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
> > > > ><[hidden email]>
> > > > >> wrote:
> > > > >>
> > > > >> > 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
> > > > ><[hidden email]>:
> > > > >> >
> > > > >> > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov
> > > > ><[hidden email]>
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > > > 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) - Vladimir Ozerov
> > > > >> > > > 3. Portable API release - Denis Magda and Vladimir
> > > > >> > > > 4. Failover for continuous query notifications - Nick
> Tikhonov
> > > > >> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> > > > >> > > > 6. Fix compatibility with IBM JDK
> > > > >> > > > 7. Cache stability and performance fixes (as many as
> possible)
> > > > >> > > >
> > > > >> > > > Nice to have:
> > > > >> > > > 8. Finish vert.x integration - Andrey Gura works on this.
> > > > >> > > > 9. Finish node.js integration - I think Semyon should pass
> it
> > > > >over to
> > > > >> > > > someone else, given he is busy with cache. Anyone? Andrey
> Gura?
> > > > >> > > >
> > > > >> > > > Comments are welcome!
> > > > >> > > >
> > > > >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> > > > >> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> > > > >> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> > > > >> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> > > > >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> > > > >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> > > > >> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> > > > >> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> > > > >> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> > > > >> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> > > > >> > > >
> > > > >> > > > --Yakov
> > > > >> > > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> > Gianfranco Murador
> > > > >> > Igniter and Software Engineer.
> > > > >> >
> > > > >>
> > > >
>

Gianfranco Murador-2

Re: Ignite 1.5 plans

In reply to this post by Gianfranco Murador-2

Dmitry,
Could you give me some feedback about this proposal? You think it might be
interesting? Thank you.

2015-09-29 12:00 GMT+02:00 Gianfranco Murador <[hidden email]>:

> Dmitry,
> The short answer is because JBPM is integrated well with Infinispan,the
> longest and technically correct answer is as follows.
>
> JBPM is now used in many productions of the clients they serve a high
> number of users.The main problem with the engine of business processes
> resides in the non- synchronicity of the workflow, ie the workflow goes
> forward based on the working times of the employees, so it is possible that
> a workflow ends within a few days. Maintain an instance of a workflow in
> the database and retrieve it each time it is expensive in terms of time, we
> might have many workflow latches.The idea is to allow to save in cache the
> entire instance of a workflow in order to make the most rapid recovery
> possible.
>
> There are also rapid workflows where the use of a cache is very
> interesting, for example, a job stream must be recovered and carried
> forward in a few second (for example,at a bank office). The idea is to
> create a grid of instances of workflows to allow recovery quickly.
>
> The idea has already been implemented for Infinispan, but is not very
> advanced.
>
>
> https://github.com/droolsjbpm/droolsjbpm-integration/tree/master/kie-infinispan/jbpm-infinispan-persistence/src/main/java/org/jbpm/persistence
>
> Regards,
> Gianfranco.
>
>
>
> 2015-09-28 18:57 GMT+02:00 Dmitriy Setrakyan <[hidden email]>:
>
>> 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 <[hidden email]>
>> wrote:
>>
>> > 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 <[hidden email]>:
>> >
>> > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov <[hidden email]>
>> > > wrote:
>> > >
>> > > > 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) - Vladimir Ozerov
>> > > > 3. Portable API release - Denis Magda and Vladimir
>> > > > 4. Failover for continuous query notifications - Nick Tikhonov
>> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
>> > > > 6. Fix compatibility with IBM JDK
>> > > > 7. Cache stability and performance fixes (as many as possible)
>> > > >
>> > > > Nice to have:
>> > > > 8. Finish vert.x integration - Andrey Gura works on this.
>> > > > 9. Finish node.js integration - I think Semyon should pass it over
>> to
>> > > > someone else, given he is busy with cache. Anyone? Andrey Gura?
>> > > >
>> > > > Comments are welcome!
>> > > >
>> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
>> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
>> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
>> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
>> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
>> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
>> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
>> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
>> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
>> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
>> > > >
>> > > > --Yakov
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Gianfranco Murador
>> > Igniter and Software Engineer.
>> >
>>
>
>
>
> --
> Gianfranco Murador
> Igniter and Software Engineer.
>
>

--
Gianfranco Murador
Igniter and Software Engineer.

yzhdanov

Re: Ignite 1.5 plans

I recall I heard about JBPM from one of our users and he referenced
infinispan integration as example. So, yes, this can be interesting, but
isn't https://github.com/droolsjbpm/droolsjbpm-integration repo a proper
place for it?

--Yakov

2015-09-29 16:22 GMT+03:00 Gianfranco Murador <[hidden email]>:

> Dmitry,
> Could you give me some feedback about this proposal? You think it might be
> interesting? Thank you.
>
> 2015-09-29 12:00 GMT+02:00 Gianfranco Murador <[hidden email]>:
>
> > Dmitry,
> > The short answer is because JBPM is integrated well with Infinispan,the
> > longest and technically correct answer is as follows.
> >
> > JBPM is now used in many productions of the clients they serve a high
> > number of users.The main problem with the engine of business processes
> > resides in the non- synchronicity of the workflow, ie the workflow goes
> > forward based on the working times of the employees, so it is possible
> that
> > a workflow ends within a few days. Maintain an instance of a workflow in
> > the database and retrieve it each time it is expensive in terms of time,
> we
> > might have many workflow latches.The idea is to allow to save in cache
> the
> > entire instance of a workflow in order to make the most rapid recovery
> > possible.
> >
> > There are also rapid workflows where the use of a cache is very
> > interesting, for example, a job stream must be recovered and carried
> > forward in a few second (for example,at a bank office). The idea is to
> > create a grid of instances of workflows to allow recovery quickly.
> >
> > The idea has already been implemented for Infinispan, but is not very
> > advanced.
> >
> >
> >
> https://github.com/droolsjbpm/droolsjbpm-integration/tree/master/kie-infinispan/jbpm-infinispan-persistence/src/main/java/org/jbpm/persistence
> >
> > Regards,
> > Gianfranco.
> >
> >
> >
> > 2015-09-28 18:57 GMT+02:00 Dmitriy Setrakyan <[hidden email]>:
> >
> >> 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 <[hidden email]
> >
> >> wrote:
> >>
> >> > 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 <[hidden email]>:
> >> >
> >> > > 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 28, 2015 at 6:43 PM, Yakov Zhdanov <[hidden email]
> >
> >> > > wrote:
> >> > >
> >> > > > 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) - Vladimir Ozerov
> >> > > > 3. Portable API release - Denis Magda and Vladimir
> >> > > > 4. Failover for continuous query notifications - Nick Tikhonov
> >> > > > 5. Cache Rebalancing optimizations - Anton Vinogradov
> >> > > > 6. Fix compatibility with IBM JDK
> >> > > > 7. Cache stability and performance fixes (as many as possible)
> >> > > >
> >> > > > Nice to have:
> >> > > > 8. Finish vert.x integration - Andrey Gura works on this.
> >> > > > 9. Finish node.js integration - I think Semyon should pass it over
> >> to
> >> > > > someone else, given he is busy with cache. Anyone? Andrey Gura?
> >> > > >
> >> > > > Comments are welcome!
> >> > > >
> >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-950
> >> > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282
> >> > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258
> >> > > > [4] https://issues.apache.org/jira/browse/IGNITE-426
> >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093
> >> > > > [5] https://issues.apache.org/jira/browse/IGNITE-324
> >> > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526
> >> > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345
> >> > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079
> >> > > > [9] https://issues.apache.org/jira/browse/IGNITE-961
> >> > > >
> >> > > > --Yakov
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Gianfranco Murador
> >> > Igniter and Software Engineer.
> >> >
> >>
> >
> >
> >
> > --
> > Gianfranco Murador
> > Igniter and Software Engineer.
> >
> >
>
>
> --
> Gianfranco Murador
> Igniter and Software Engineer.
>

yzhdanov

Re: Ignite 1.5 plans

Igniters,

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

--Yakov

Gianfranco Murador-2

Re: Ignite 1.5 plans

Yakov,
So I guess that integration should only affect the way JBPM interacts with
Ignite ?
I think that a module dedicated to ignite could provide APIs more advanced
than simple get and put on a grid. Infinispan already provides a second
level cache Ignite does, but that does not mean that
Ignite does not have to provide similar feature.
Interacting JBPM with a dedicated module of ignite we could do processing
on the workflow instance in advanced mode, exploiting the near cache in a
distributed environment.
Maybe the module might not be ready for the release of version 1.5.
Ultimately, who knows better than you that Ignite is more advanced than
Infinspan ?

2015-09-29 16:52 GMT+02:00 Yakov Zhdanov <[hidden email]>:

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

--
Gianfranco Murador
Igniter and Software Engineer.