[DISCUSSION] Redis and memcached protocol support.

[Ivan Daschinsky <iv...@apache.org>]

Igniters, I'd like to discuss the future of this functionality in Apache
Ignite

Today this functionality seems to be unusable
1. It is limited (especially redis)
2. It doesn't support HA (redis sentinel or redis cluster)
3. Nobody maintains it and even nobody fixes bugs. (i.e. [1] is not merged
for years).

If we want to support redis protocol, we should rewrite it and add HA
features.
Otherwise, I suppose that we should consider complete removal of this code
from codebase.

WDYT?


[1] -- https://issues.apache.org/jira/browse/IGNITE-7153

Re: [DISCUSSION] Redis and memcached protocol support.

[Ivan Daschinsky <iv...@gmail.com>]

As for me, I believe that this should be removed. We have already proven
binary protocol that is under heavy use.

ср, 9 февр. 2022 г. в 15:11, Maxim Muzafarov <mm...@apache.org>:

> Hello,
>
> From my point of view, it's better to reduce the scope of features to
> be supported and focus on those ones that a really important for
> production e.g. Calcite for Ignite 2.x. However, talking in terms of
> open-source development it's better to find a volunteer who will fix
> all the issues you describe.
>
> On Tue, 8 Feb 2022 at 14:27, Ivan Daschinsky <iv...@apache.org> wrote:
> >
> > Igniters, I'd like to discuss the future of this functionality in Apache
> > Ignite
> >
> > Today this functionality seems to be unusable
> > 1. It is limited (especially redis)
> > 2. It doesn't support HA (redis sentinel or redis cluster)
> > 3. Nobody maintains it and even nobody fixes bugs. (i.e. [1] is not
> merged
> > for years).
> >
> > If we want to support redis protocol, we should rewrite it and add HA
> > features.
> > Otherwise, I suppose that we should consider complete removal of this
> code
> > from codebase.
> >
> > WDYT?
> >
> >
> > [1] -- https://issues.apache.org/jira/browse/IGNITE-7153
>


-- 
Sincerely yours, Ivan Daschinskiy

Re: [DISCUSSION] Redis and memcached protocol support.

[Maxim Muzafarov <mm...@apache.org>]

Hello,

From my point of view, it's better to reduce the scope of features to
be supported and focus on those ones that a really important for
production e.g. Calcite for Ignite 2.x. However, talking in terms of
open-source development it's better to find a volunteer who will fix
all the issues you describe.

On Tue, 8 Feb 2022 at 14:27, Ivan Daschinsky <iv...@apache.org> wrote:
>
> Igniters, I'd like to discuss the future of this functionality in Apache
> Ignite
>
> Today this functionality seems to be unusable
> 1. It is limited (especially redis)
> 2. It doesn't support HA (redis sentinel or redis cluster)
> 3. Nobody maintains it and even nobody fixes bugs. (i.e. [1] is not merged
> for years).
>
> If we want to support redis protocol, we should rewrite it and add HA
> features.
> Otherwise, I suppose that we should consider complete removal of this code
> from codebase.
>
> WDYT?
>
>
> [1] -- https://issues.apache.org/jira/browse/IGNITE-7153