It is the last point in the wishlist that probably nobody cares about.
I see no discussion at all, no @Deprecation annotations and a lot of
abandoned and broken code only.
пт, 3 дек. 2021 г. в 11:01, Maxim Muzafarov :
> Ivan,
>
> It seems shmem is already in the remove list [1].
>
> [1]
> https:/
Ivan,
It seems shmem is already in the remove list [1].
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
On Fri, 3 Dec 2021 at 10:42, Ivan Daschinsky wrote:
>
> So if nobody wants it to resurrect, maybe it is worth removing it?
>
>
> пт, 3 дек. 2021 г. в 09:25,
So if nobody wants it to resurrect, maybe it is worth removing it?
пт, 3 дек. 2021 г. в 09:25, Ivan Pavlukhin :
> Latest that I heard that it literally was never in use.
>
> 2021-11-29 19:44 GMT+03:00, Ivan Daschinsky :
> > There is JNI library in ipc/shmem directory. It even compiles with
> min
Latest that I heard that it literally was never in use.
2021-11-29 19:44 GMT+03:00, Ivan Daschinsky :
> There is JNI library in ipc/shmem directory. It even compiles with minimal
> modification on modern gcc (9.3.0)
> But there is no script to build jar with native library.
>
> May be it is possib
There is JNI library in ipc/shmem directory. It even compiles with minimal
modification on modern gcc (9.3.0)
But there is no script to build jar with native library.
May be it is possible to create separate module, refactor it a bit, change
build process (CMake)?
Is there a technical reason why i
Guys, what is the status of ignite-shmem and TcpCommunication through it?
1. Native part has not been built at all since 2015
2. It is currently broken in master -- I've fixed some NPE and metrics
conversion locally and it works for me. It is broken for almost a year.
3. GridShmemCommunicationClie
LGTM. Merged to master.
Thank you for your contribution!
On Fri, Nov 26, 2021 at 12:20 PM Maxim Muzafarov wrote:
> Folks,
>
> This is a friendly reminder :-)
> PR [1] is ready for review. Will anyone take a look?
>
> [1] https://github.com/apache/ignite/pull/9577/files
>
> On Sat, 20 Nov 2021 a
Folks,
This is a friendly reminder :-)
PR [1] is ready for review. Will anyone take a look?
[1] https://github.com/apache/ignite/pull/9577/files
On Sat, 20 Nov 2021 at 03:17, Maxim Muzafarov wrote:
>
> Folks,
>
>
> I've prepared the changes related to the legacy Service Grid removal
> for the 2
Folks,
I've prepared the changes related to the legacy Service Grid removal
for the 2.13 release. Here is the issue [1] and the PR [2] of these
changes.
Some important notes:
- Removed GridServiceProcessor legacy implementation (internal)
- The IGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED syst
Hello.
In the scope of IEP-80 Breaking changes in Ignite-2.x PR for the following API
are prepared:
1. MVCC
- https://issues.apache.org/jira/browse/IGNITE-15757
- https://github.com/apache/ignite/pull/9516
2. LOCAL caches
- https://issues.apache.org/jira/browse/IGNITE-15756
THanks, Maksim.
Tickets included in IEP scope and marked for d&r in 2.12-2.13
> 15 окт. 2021 г., в 16:03, Maxim Muzafarov написал(а):
>
> Let's deprecate RebalanceDelay and RebalanceMode=NONE also.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12662
> [2] https://issues.apache.org/jira/
Let's deprecate RebalanceDelay and RebalanceMode=NONE also.
[1] https://issues.apache.org/jira/browse/IGNITE-12662
[2] https://issues.apache.org/jira/browse/IGNITE-14613
On Fri, 15 Oct 2021 at 15:46, Anton Vinogradov wrote:
>
> +1
>
> On Fri, Oct 15, 2021 at 3:41 PM Nikita Amelchev
> wrote:
>
>
+1
On Fri, Oct 15, 2021 at 3:41 PM Nikita Amelchev
wrote:
> +1 for deprecation in the 2.12 release
>
> пт, 15 окт. 2021 г. в 15:35, Nikolay Izhikov :
> >
> > Hello, Igniters.
> >
> > I’ve prepared IEP-80 [1] to track breaking changes that should be done
> in Ignite 2.x.
> >
> > We agreed on the
+1 for deprecation in the 2.12 release
пт, 15 окт. 2021 г. в 15:35, Nikolay Izhikov :
>
> Hello, Igniters.
>
> I’ve prepared IEP-80 [1] to track breaking changes that should be done in
> Ignite 2.x.
>
> We agreed on the following algorithm to deal with breaking changes:
>
> - Ignite 2.[x] - d
Hello, Igniters.
I’ve prepared IEP-80 [1] to track breaking changes that should be done in
Ignite 2.x.
We agreed on the following algorithm to deal with breaking changes:
- Ignite 2.[x] - deprecate the API + notification of the users.
- Ignite 2.[x+1] - API removal.
I propose to start
15 matches
Mail list logo
