Hi Emmanouil,
The changes looks good to me. I wanted to check if you are also able to
validate that the once data is added to Ignite cluster you are also able to
access it using another Ignite client or using rest endpoints.
We use Teamcity for CI process, the details are as follows
Trigger
Hi Everyone,
We will be hosting a webinar this week to talk about and demo What's New in
Web Console 2019.10.
Here is a registration link if you would like to join the discussion
https://ignite.apache.org/events.html#whats-new-in-gridgain-web-console
A replay will also be published after the
Vladislav Pyatkov created IGNITE-12290:
--
Summary: Re-balance fully restart for case when WAL disabled
Key: IGNITE-12290
URL: https://issues.apache.org/jira/browse/IGNITE-12290
Project: Ignite
Maxim Muzafarov created IGNITE-12289:
Summary: TestBinaryContext should be removed from production code
Key: IGNITE-12289
URL: https://issues.apache.org/jira/browse/IGNITE-12289
Project: Ignite
Dmitriy,
> PS, I've shared links to new images sources in the Slack channel.
Cannot find links. Which Slack channel was meant?
чт, 10 окт. 2019 г. в 00:42, Dmitriy Pavlov :
>
> Hi Ivan, thanks for bringing this here, it is definitely needed to be fixed.
>
> There is the same issue for one
Hi Maxim,
I'm glad to see that you care about documentation. Way to go! Here is a
couple of points that can help:
1) I think it's safe to assume that Prachi will not work on the Ignite
documentation any longer. You can take up the issues assigned to her and
prioritize them whichever way is
Denis,
The idea of having a sandbox for running a user-defined code is useful, but
I don't fully understand the implementation approach.
There is no detailed description of the ticket about what public API
methods or configuration parameters should be covered.
There is no description of what have
Yes, let's use the Russian for short discussion, the meeting notes will be
presented in English
пн, 14 окт. 2019 г. в 14:08, Nikolay Izhikov :
> Hello, Alexey.
>
> I'm ready to take part in the meeting.
> It will be in Russian, isn't it?
>
> В Пн, 14/10/2019 в 14:00 +0300, Alexey Zinoviev пишет:
Hello, Alexey.
I'm ready to take part in the meeting.
It will be in Russian, isn't it?
В Пн, 14/10/2019 в 14:00 +0300, Alexey Zinoviev пишет:
> Hi, Igniters, and especially Nikolay Izhikov
>
> I suggest to arrange the meeting via ASF-slack in #ignite-spark-integration
> channel at 17 October,
Hi, Igniters, and especially Nikolay Izhikov
I suggest to arrange the meeting via ASF-slack in #ignite-spark-integration
channel at 17 October, in 16 MSK Time.
The language of the meeting: Russian
*The topics to discuss:*
- Review of next tickets
1. [Spark][Bug] IgniteSpark integration
Alexey Zinoviev created IGNITE-12288:
Summary: [ML] Replace assert logic with exceptions
Key: IGNITE-12288
URL: https://issues.apache.org/jira/browse/IGNITE-12288
Project: Ignite
Issue
Ok, thank you, I've missed the start of the discussion
пн, 14 окт. 2019 г. в 11:13, Ivan Pavlukhin :
> Alexey, Petr,
>
> Please read first message in this thread. Now checkstyle is a part of
> [Build
> Apache Ignite].
>
> If you still have any questions after that please write back.
> Sincerely,
Fully agree with the benchmark's importance.
Currently, we're not able to perform proper benchmarking.
Slava, Is it possible to ask you to check the solution using GridGain's
benchmarking environment?
On Mon, Oct 14, 2019 at 12:07 PM Вячеслав Коптилин
wrote:
> Hello Anton,
>
> > We should avoid
Hello Anton,
> We should avoid heavy merges if possible.
Why it should be avoided? To be honest, I don't see any reason for that.
Every pull request can be and should be reviewed when it is done and ready
to be merged into the epic branch (IEP branch).
So, the final review of the entire IEP is
Hi Saikat,
Sorry for delay. I will do my best to check it in the beginning of this week.
сб, 12 окт. 2019 г. в 08:15, Saikat Maitra :
>
> Hello Ivan,
>
> I have updated the PR as per our discussion.
>
> Please review and share your feedback.
>
> Regards,
> Saikat
>
> On Sun, Sep 1, 2019 at 3:20
Alexey, Petr,
Please read first message in this thread. Now checkstyle is a part of [Build
Apache Ignite].
If you still have any questions after that please write back.
Sincerely, I do not want us to repeat the discussion as it was
detailed enough and in my opinion Maxim did the change
Maksim, why have you removed Checkstyle from Run All?
> On 13 Oct 2019, at 18:52, Maxim Muzafarov wrote:
>
> Igniters,
>
> The `checkstyle` profile has been enabled for the Apache Ignite build
> procedure.
> Unused imports in the spark module have been fixed [1].
> The `[Check Code Style]`
Folks,
We should avoid heavy merges if possible.
I'm ok with IEP to keep tasks properly, but strictly against all-in-one
"+27000,-18200" merges.
This task implements Sandbox (API + core) which covered by tests and by
some integrations with existing components, which is enough to merge.
The most
18 matches
Mail list logo
