Hello, Saikat.
As far as I can see you changed artifactId of the extensions not only docs.
Do we have an agreement to name each extension as «{extension-name}-ext» like
«ignite-camel-ext» or similar?
We don’t have much extensions release, so maybe it will be better to have
naming like
Hi,
I have raised a PR for the following issue.
Jira : https://issues.apache.org/jira/browse/IGNITE-12951
PR : https://github.com/apache/ignite-extensions/pull/30
This is an initial PR in Ignite Extensions repo. I will work on another PR
in ignite repo for the remaining changes.
Regards,
Hi,
I have raised a PR for the following jira issue.
Jira : https://issues.apache.org/jira/browse/IGNITE-13648
PR : https://github.com/apache/ignite-extensions/pull/29
We are observing following exceptions in the test failures:
Caused by: org.apache.ignite.IgniteCheckedException: Remote node
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master JCache TCK 1.1
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_JCacheTck11?branch=%3Cdefault%3E
No changes in the build
-
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master-nightly Disk Page Compressions
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_DiskPageCompressions?branch=%3Cdefault%3E
No changes
Igniters,
This is a continuation of "Use Netty for Java thin client" [1],
I'm starting a new thread for better visibility.
The problems with current Java thin client are:
* Socket writes block user threads
* Every connection uses a separate listener thread (with partition
awareness there is a
Yaroslav, there is another bug for 2.9.1 release
https://issues.apache.org/jira/browse/IGNITE-13572
чт, 5 нояб. 2020 г., 19:23 Yaroslav Molochkov :
> Ivan, hi!
> Sure.
>
> UPD: i am the release manager and will be doing this with Maxim's help
> (since i don't have some user permissions)
>
> On
