Kirill Tkalenko created IGNITE-12466:
Summary: Monitor query pool starvation
Key: IGNITE-12466
URL: https://issues.apache.org/jira/browse/IGNITE-12466
Project: Ignite
Issue Type: Improvem
Hi Ivan, Igniters,
My proposal is to apply PR and take a look to wider statistics in the
master branch. WDYT?
Sincerely,
Dmitriy Pavlov
ср, 18 дек. 2019 г. в 09:36, Ivan Pavlukhin :
> Igniters,
>
> I run tests several times for my PR [1] and results [2] looks somehow
> better than in master [3]
Folks,
I have no objections. But I would like to count on your support in
cases of any release-blocking issues. Can I?
Anton,
Let's do the following:
1. Merge the issue to the master branch.
2. Wait for two-three weeks of running tests.
3. Check that there are not flaky failures and fix them al
So, if nobody objects, I will merge PR [1] on Friday.
[1] https://github.com/apache/ignite/pull/7142
ср, 18 дек. 2019 г. в 13:13, Dmitriy Pavlov :
>
> Hi Ivan, Igniters,
>
> My proposal is to apply PR and take a look to wider statistics in the
> master branch. WDYT?
>
> Sincerely,
> Dmitriy Pavlo
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 sche
Ivan, thank you for your response!
18.12.2019, 10:24, "Ivan Pavlukhin" :
> Hi Ilya,
>
> Welcome to Apache Ignite Community!
>
> As I see you already have a contributor role in JIRA (you can work on
> tickets). You can find some contribution guidelines in
> https://github.com/apache/ignite/blob/mas
Alexey, Nikolay,
Could you please step in and shed some light on what has changed with
Spark? Probably, that's an issue that needs to be addressed before the
release.
-
Denis
On Wed, Dec 18, 2019 at 9:26 AM Stefan Miklosovic <
stefan.mikloso...@instaclustr.com> wrote:
> Hi,
>
> I want to try s
Sure,
You may count on my assistance in case of any problems.
We're both in the same boat.
But I see no reason to delay the "pme-free switch" merge to 2.8.
We always have to merge all release features asap to have as much time as
possible to fix all bugs.
I will replace the "feature activation ve
Anton,
Thank you.
Have no objections, let's do it!
On Wed, 18 Dec 2019 at 23:23, Anton Vinogradov wrote:
>
> Sure,
> You may count on my assistance in case of any problems.
> We're both in the same boat.
>
> But I see no reason to delay the "pme-free switch" merge to 2.8.
> We always have to me
Robert Emanuele created IGNITE-12467:
Summary: Thing Client Support for Transactions
Key: IGNITE-12467
URL: https://issues.apache.org/jira/browse/IGNITE-12467
Project: Ignite
Issue Type:
Hi,
The page with the embedded recording and slides link is
https://www.gridgain.com/resources/webinars/data-streaming-using-apache-flink-and-apache-ignite/view
.
You can go directly to the YouTube video at
https://www.youtube.com/watch?v=wM-YVYVU8Lk.
You can go directly to the slides at
ht
LEE PYUNG BEOM created IGNITE-12468:
---
Summary: ClassCastException on thinClient in Apache Ignite
Key: IGNITE-12468
URL: https://issues.apache.org/jira/browse/IGNITE-12468
Project: Ignite
Is
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 as follows:
>
> Remove igni
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 wrote:
> 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 :
> >
> > Hel
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Hi!
What if some users already using this module?
What they should do? Rewrite code?
I do not think it is a good idea.
My "-1" here.
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.
>
> On Thu, Dec 19, 2019
Is this suggested for 3.0 or 2.8?
I tend to agree with Alexey - API compatibility should be preserved within
a major version. I would oppose doing such a change in 2.x.
If this is planned for 3.0, then it's a definite +1 from me.
-Val
On Wed, Dec 18, 2019 at 11:34 PM Alexey Kuznetsov
wrote:
>
My Vote was for 3.0
On Thu, Dec 19, 2019 at 10:44 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Is this suggested for 3.0 or 2.8?
>
> I tend to agree with Alexey - API compatibility should be preserved within
> a major version. I would oppose doing such a change in 2.x.
>
> If
18 matches
Mail list logo
