> > >> > > > My Vote was for 3.0
> > > > > >> > > >
> > > > > >> > > > On Thu, Dec 19, 2019 at 10:44 AM Valentin Kulichenko <
> > > > > >> > > > valentin.kuliche...@gmail.com> wrote:
> > > > > >> >
API compatibility should be
> > > > preserved
> > > > >> > > > within
> > > > >> > > > > a major version. I would oppose doing such a change in
> 2.x.
> > > > >> > > > >
> > > > >> > &g
; > > > >
> > > >> > > > > If this is planned for 3.0, then it's a definite +1 from me.
> > > >> > > > >
> > > >> > > > > -Val
> > > >> > > > >
> > > >> >
19 at 11:34 PM Alexey Kuznetsov <
> > >> > akuznet...@apache.org
> > >> > > > >
> > >> > > > > wrote:
> > >> > > > >
> > >> > > > > > Hi!
> > >> > &
> >> > > > > > Hi!
> >> > > > > >
> >> > > > > > What if some users already using this module?
> >> > > > > > What they should do? Rewrite code?
> >> > > > > > I do not think it is a good idea.
> &
s module?
>> > > > > > What they should do? Rewrite code?
>> > > > > > I do not think it is a good idea.
>> > > > > >
>> > > > > > My "-1" here.
>> > > > > >
>> > > >
re.
> > > > > >
> > > > > > On Thu, Dec 19, 2019 at 8:53 AM Anton Vinogradov
> > > > wrote:
> > > > > >
> > > > > > > ignite-schedule does not look to be properly located or useful.
> > > > > > > My +1 here.
> > > > > >
; > >
> > > > > > ignite-schedule does not look to be properly located or useful.
> > > > > > My +1 here.
> > > > > >
> > > > > > On Thu, Dec 19, 2019 at 8:35 AM Ivan Pavlukhin <
> vololo...@gmail.com>
> > > > &g
1 here.
> > > > > >
> > > > > > On Thu, Dec 19, 2019 at 8:35 AM Ivan Pavlukhin <
> vololo...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Ilya,
> > > > > > >
> >
> > wrote:
> > > > >
> > > > > > Ilya,
> > > > > >
> > > > > > I think it is a good initiative! Do we really need to keep
> > > > > > run/callLocall methods at all?
> > > > > >
> > > > &g
, Dec 19, 2019 at 8:35 AM Ivan Pavlukhin
> > > > wrote:
> > > >
> > > > > Ilya,
> > > > >
> > > > > I think it is a good initiative! Do we really need to keep
> > > > > run/callLocall methods at all?
> > > > &
t;
> > > On Thu, Dec 19, 2019 at 8:35 AM Ivan Pavlukhin
> > > wrote:
> > >
> > > > Ilya,
> > > >
> > > > I think it is a good initiative! Do we really need to keep
> > > > run/callLocall methods at all?
> &g
t all?
> > >
> > > ср, 18 дек. 2019 г. в 17:59, Ilya Kasnacheev :
> > > >
> > > > Hello!
> > > >
> > > > Since 2.8 is branched, I want to initiate the discussion about
> removal
> > of
> > > > ignite-schedule
Hello!
> > >
> > > Since 2.8 is branched, I want to initiate the discussion about removal
> of
> > > ignite-schedule module.
> > >
> > > My plan as follows:
> > >
> > > Remove ignite-schedule module entirely.
> > > Move ru
9, Ilya Kasnacheev :
> >
> > Hello!
> >
> > Since 2.8 is branched, I want to initiate the discussion about removal of
> > ignite-schedule module.
> >
> > My plan as follows:
> >
> > Remove ignite-schedule module entirely.
> > Move runLocal and callLoc
Ilya,
I think it is a good initiative! Do we really need to keep
run/callLocall methods at all?
ср, 18 дек. 2019 г. в 17:59, Ilya Kasnacheev :
>
> Hello!
>
> Since 2.8 is branched, I want to initiate the discussion about removal of
> ignite-schedule module.
>
> My plan a
Hello!
Since 2.8 is branched, I want to initiate the discussion about removal of
ignite-schedule module.
My plan as follows:
Remove ignite-schedule module entirely.
Move runLocal and callLocal methods from IgniteScheduler to IgniteCompute.
Delete IgniteScheduler interface with its remaining
Hello!
In any case I don't see why we would keep ignite-schedule module. We could
merge this change if you moved this functionality into ignite-spring (while
also fixing single thread problem).
The sole reason of existence of ignite-schedule module was the extra
dependency, if we don'
:
> Hello!
>
> I've spent considerable amount of time working on your patch yesterday, but
> eventually I have come to conclusion that we should Deprecate
> IgniteScheduler and ignite-schedule module, and Remove it in 3.0.
>
> The reason for this: IgnoteScheduler interface
Hello!
I've spent considerable amount of time working on your patch yesterday, but
eventually I have come to conclusion that we should Deprecate
IgniteScheduler and ignite-schedule module, and Remove it in 3.0.
The reason for this: IgnoteScheduler interface has 5 methods, of those
call
Hi, Ilya!
It looks like Spring *ThreadPoolTaskScheduler* is bounded to JDK's
*ScheduledThreadPoolExecutor*, so to launch scheduled tasks on public pool
we need provide *ScheduledThreadPoolExecutor* for Public pool. Currently I
see we create Public pool executor as *IgniteThreadPoolExecutor* and it
Hello!
I have started reviewing your pull request.
I will expect that scheduled tasks are executed on Public pool. Is it
possible that tasks are launched on Public pool? If Spring Scheduler
insists on its own thread pool, we can have single-thread pool which will
execute put of tasks to public poo
Hi, Sergey!
I think we should keep compatibility as much as possible for Ignite 2.x.
And we can do breaking changes in Ignite 3.x
What do you think?
On Mon, Dec 24, 2018 at 11:58 PM Sergey wrote:
> HI, Igniters!
>
> I've updated and rebased implementation to master branch and made some
> fixe
HI, Igniters!
I've updated and rebased implementation to master branch and made some
fixes.
Also I have a question regarding current implementation.
As I found Cron4J source code this implementation checks schedule every
minute (seconds not supported) but spawns a thread for every task which
sche
> > > Regards,
> > >
> > > --
> > > Ilya Kasnacheev
> > >
> > > 2018-06-06 19:05 GMT+03:00 Dmitry Pavlov :
> > >
> > > > Hi Igniters,
> > > >
> > > > I've tried to use
> > > >
> > > >
,
> > >
> > > I've tried to use
> > >
> > > ignite.scheduler().scheduleLocal(this::checkFailures, "? * * * * *");
> > >
> > > Result is
> > > class org.apache.ignite.IgniteException: Current Ignite configuration
>
00 Dmitry Pavlov :
>
> > Hi Igniters,
> >
> > I've tried to use
> >
> > ignite.scheduler().scheduleLocal(this::checkFailures, "? * * * * *");
> >
> > Result is
> > class org.apache.ignite.IgniteException: Current Ignit
Result is
> class org.apache.ignite.IgniteException: Current Ignite configuration does
> not support schedule functionality (consider adding ignite-schedule module
> to classpath).
> at
> org.apache.ignite.internal.processors.schedule.
> IgniteNoopScheduleProcessor.processorExcep
Hi Igniters,
I've tried to use
ignite.scheduler().scheduleLocal(this::checkFailures, "? * * * * *");
Result is
class org.apache.ignite.IgniteException: Current Ignite configuration does
not support schedule functionality (consider adding ignite-schedule module
to
Hi Anton,
Thank you for joining and review.
I hope all proposals will be applied.
Sincerely,
Dmitriy Pavlov
пт, 4 мая 2018 г. в 16:04, Anton Vinogradov :
> Folks,
>
> How can it be at PATCH AVAILABLE since *none* of my latest comments (made
> Feb 8) are resolved at Upsource?
> Changed state to
Folks,
How can it be at PATCH AVAILABLE since *none* of my latest comments (made
Feb 8) are resolved at Upsource?
Changed state to IP.
пн, 23 апр. 2018 г. в 20:00, Dmitry Pavlov :
> Hi Andrey,
>
> Could you please pick up review?
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 23 апр. 2018 г. в 17:39, D
Hi Andrey,
Could you please pick up review?
Sincerely,
Dmitriy Pavlov
пн, 23 апр. 2018 г. в 17:39, Dmitriy Setrakyan :
> Dmitriy, who is a good candidate within the community to review this
> ticket?
>
> On Mon, Apr 23, 2018 at 6:10 AM, Dmitry Pavlov
> wrote:
>
> > Hi Igniters,
> >
> > it seem
Dmitriy, who is a good candidate within the community to review this ticket?
On Mon, Apr 23, 2018 at 6:10 AM, Dmitry Pavlov
wrote:
> Hi Igniters,
>
> it seems ticket https://issues.apache.org/jira/browse/IGNITE-5565 is still
> in PA state. What are our next steps?
>
> Who did review of this patc
Hi Igniters,
it seems ticket https://issues.apache.org/jira/browse/IGNITE-5565 is still
in PA state. What are our next steps?
Who did review of this patch?
Sincerely,
Dmitriy Pavlov
ср, 28 июн. 2017 г. в 1:40, Denis Magda :
> Yakov,
>
> No, the mentioned discussion didn’t turn into a JIRA tick
Yakov,
No, the mentioned discussion didn’t turn into a JIRA ticket.
Alex K., please follow to some thoughts from there and wrap them up in a form
of the ticket.
—
Denis
> On Jun 26, 2017, at 2:58 AM, Yakov Zhdanov wrote:
>
> Guys, I remember we discussed this some time ago.
>
> http://apach
Guys, I remember we discussed this some time ago.
http://apache-ignite-developers.2346864.n4.nabble.com/Tasks-Scheduling-and-Chaining-td14293.html
Denis, do you have any ticket or SoW?
--Yakov
CRON;
> > >> 5.spring's code quality is very good, maintainability is good, and the
> > >> quality of quartz code is not very good.
> > >> On 06/21/2017 13:26,Alexey Kuznetsov wrote:
> > >> Hi!
> > >>
> > >> 1) Cron4J
s not very good.
> >> On 06/21/2017 13:26,Alexey Kuznetsov wrote:
> >> Hi!
> >>
> >> 1) Cron4J is very old:
> >> Latest Cron4j 2.2.5 released: *28-Dec-2011 *
> >> Latest Quarz 2.3.0 released: *20-Apr-2017*
> >>
> >> 2)
;>
>> 1) Cron4J is very old:
>> Latest Cron4j 2.2.5 released: *28-Dec-2011 *
>> Latest Quarz 2.3.0 released: *20-Apr-2017*
>>
>> 2) Not very friendly license:
>> CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
>> Quartz is freely usable, licensed
leased: *20-Apr-2017*
>
> 2) Not very friendly license:
> CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
> Quartz is freely usable, licensed under the *Apache 2.0* license.
>
> So, if we replace Cron4J with Quartz we can move *ignite-schedule* module
> fro
nse.
So, if we replace Cron4J with Quartz we can move *ignite-schedule* module
from lgpl profile to main distribution.
Any objections?
If no, I will create JIRA issue and implement this change.
--
Alexey Kuznetsov
t; > D.
>> > >
>> > > On Wed, Jun 21, 2017 at 7:26 AM, Alexey Kuznetsov <
>> akuznet...@apache.org
>> > >
>> > > wrote:
>> > >
>> > > > Hi!
>> > > >
>> > > > 1) Cron4J is very old
n 21, 2017 at 7:26 AM, Alexey Kuznetsov <
> akuznet...@apache.org
> > >
> > > wrote:
> > >
> > > > Hi!
> > > >
> > > > 1) Cron4J is very old:
> > > > Latest Cron4j 2.2.5 released: *28-Dec-2011 *
> > > >
Alexey Kuznetsov created IGNITE-5565:
Summary: Replace Cron4J with Quartz for ignite-schedule module.
Key: IGNITE-5565
URL: https://issues.apache.org/jira/browse/IGNITE-5565
Project: Ignite
> > 1) Cron4J is very old:
> > > Latest Cron4j 2.2.5 released: *28-Dec-2011 *
> > > Latest Quarz 2.3.0 released: *20-Apr-2017*
> > >
> > > 2) Not very friendly license:
> > > CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
> > >
est Cron4j 2.2.5 released: *28-Dec-2011 *
> > Latest Quarz 2.3.0 released: *20-Apr-2017*
> >
> > 2) Not very friendly license:
> > CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
> > Quartz is freely usable, licensed under the *Apache 2.0* license.
>
very friendly license:
> CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
> Quartz is freely usable, licensed under the *Apache 2.0* license.
>
> So, if we replace Cron4J with Quartz we can move *ignite-schedule* module
> from lgpl profile to main distribution.
>
>
Cron4J with Quartz we can move *ignite-schedule* module
from lgpl profile to main distribution.
Any objections?
If no, I will create JIRA issue and implement this change.
--
Alexey Kuznetsov
Ivan Veselovsky created IGNITE-1723:
---
Summary: [Test] 2 tests of "Scalar Examples" suite permanently
fail due to missing "ignite-schedule" module
Key: IGNITE-1723
URL: https://issues.ap
49 matches
Mail list logo