Not sure, I would probably bring that up in the PR so the micronaut devs
are aware of this. Not sure how the CI will work and what can be arranged
in this case.
On Thu, Aug 27, 2020 at 3:50 PM Denis Magda wrote:
> Michael,
>
> The docs look good enough for the release. Once the integration is
>
Petr, thanks,
There is also a collection of modules located in our extensions repository:
https://github.com/apache/ignite-extensions
@Saikat Maitra is migrating all our existing
integrations to that repository and, once this is done, the extensions will
be released to Maven separately. Is it
Guys,
Since we started creating IEPs related specifically for 3.0, I thought it
would be easier if we separate them from others.
I went ahead and created a subfolder under "Active Proposals" [1] and moved
the newly created IEP-52 there.
[1]
Looks beautiful and easy to use, thanks, Artem! Could you please add the
following copyright to the footer of the pages?
*© 2020 The Apache Software Foundation.*
*Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are
either registered trademarks or trademarks of The Apache
Michael,
The docs look good enough for the release. Once the integration is
released, I'll update and extend my Micronaut tutorial elucidating on how
to use the integration in practice for various use cases.
Btw, are the ignite-core and ignite-cache Maven artifacts will be released
for a
Hi Petr,
The proposal makes sense to me - thanks for starting the discussion.
Current installation and upgrade procedures involve a lot of manual steps
and quite error-prone, we need to automate and simplify them as much as
possible.
I believe we eventually should end up with a unified
Hello Nikolay,
Created one, available by link [1]
Initially there was an intention to develop it under IEP-47 [2] and there
is even a separate section for Maintenance Mode there.
But it looks like this feature is useful in more cases and deserves its own
IEP.
[1]
Stanilovsky Evgeny created IGNITE-13389:
---
Summary: Add possibility to obtain full stack trace on thin client
side.
Key: IGNITE-13389
URL: https://issues.apache.org/jira/browse/IGNITE-13389
Hi everyone,
We published the draft of Ignite 2.9 documentation on the Apache Ignite
web-site. The docs are available via the following link:
https://ignite.apache.org/docs/2.9.0/installation/installing-using-docker
Alex,
Is there an estimate for the release date?
-Artem
On 26.08.2020
I've created a JIRA issue:
https://issues.apache.org/jira/browse/IGNITE-13388
-Artem
On 27.08.2020 12:05, Petr Ivanov wrote:
Hi, Artem,
Can you file and issue with description what exactly do not work and
why, please?
On 27 Aug 2020, at 11:55, Artem Budnikov
Artem Budnikov created IGNITE-13388:
---
Summary: apache-ignite deb package depends on the non-existent
package and can't be installed on Debian 10
Key: IGNITE-13388
URL:
Hi, Igniters!
For Apache Ignite 3.0 I would like to propose vision of enhanced delivery and
upgrade processes [1].
The key idea is to make main binary as slim as possible (delivering every
optional component by demand only) while providing way to run each new version
seamlessly without much
Hi, Artem,
Can you file and issue with description what exactly do not work and why,
please?
> On 27 Aug 2020, at 11:55, Artem Budnikov wrote:
>
> Looks like this issue wasn't fixed in 2.8.1. The Ignite deb package v. 2.8.1
> can't be installed on debian 10:
>
>
>> $ sudo apt-get install
Looks like this issue wasn't fixed in 2.8.1. The Ignite deb package v.
2.8.1 can't be installed on debian 10:
$ sudo apt-get install apache-ignite
...
The following packages have unmet dependencies:
apache-ignite : Depends: openjdk-8-jdk but it is not installable or
Hello, Sergey!
Thanks for the proposal.
Let’s have IEP for this feature.
> 27 авг. 2020 г., в 10:25, Sergey Chugunov
> написал(а):
>
> Hello Igniters,
>
> I want to start a discussion about new supporting feature that could be
> very useful in many scenarios where persistent storage is
Hello Igniters,
I want to start a discussion about new supporting feature that could be
very useful in many scenarios where persistent storage is involved:
Maintenance Mode.
*Summary*
Maintenance Mode (MM for short) is a special state of Ignite node when node
doesn't serve user requests nor
16 matches
Mail list logo
