ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: Deprecate IgniteConfiguration.marshaller and make it no-op!
Date Thu, 08 Jun 2017 21:30:29 GMT
Denis,

I think we should not provide distinction between "data grid", "compute
grid" and other use case. We should have consistent product which just
works.

Anyway,I am OK to just deprecate these property for 2.0 and remove 3.0 if
community thinks that custom marshallers are still needed.

On Fri, Jun 9, 2017 at 12:19 AM, Denis Magda <dmagda@apache.org> wrote:

>
> > On Jun 8, 2017, at 1:37 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>
> wrote:
> >
> > On Thu, Jun 8, 2017 at 1:16 PM, Denis Magda <dmagda@apache.org> wrote:
> >
> >>
> >>>> It means that the binary marshaller is irreplaceable for Ignite as
> for a
> >>>> SQL database. Which is fine and makes total sense to me.
> >>>>
> >>>> However, for Ignite as for a Data Grid use case it should be
> supported.
> >>>> So, personally, I would document all this properly.
> >>>>
> >>>> Other thoughts?
> >>>>
> >>>
> >>> Denis, will Data Grid use case work if you plugin your own marshaller?
> I
> >>> have a sense that most of the API will fail, no?
> >>
> >> Why shouldn’t it work? Key-value, compute tasks and streamers shouldn’t
> >> highly depend on the binary marshaller.
> >>
> >
> > Will SQL queries work? Will JDBC data store integration work?
>
> They won’t. But that’s not a pure data grid use case, right?
>
> —
> Denis

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message