ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: Configuration inconsistency
Date Thu, 14 May 2015 11:11:45 GMT
This is one more argument to move to factories.

--Yakov

2015-05-13 6:02 GMT+03:00 Valentin Kulichenko <valentin.kulichenko@gmail.com
>:

> All our implementations are Serializable. But we don't know anything about
> user's implementations.
>
> --
> Val
>
> On Tue, May 12, 2015 at 11:50 AM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> wrote:
>
> > On Tue, May 12, 2015 at 2:45 PM, Valentin Kulichenko <
> > valentin.kulichenko@gmail.com> wrote:
> >
> > > I already created a ticket ​anyway (can cloase it if we decide not to
> > fix):
> > > https://issues.apache.org/jira/browse/IGNITE-896
> > >
> > > There is one more issue here: we require cache configuration to be
> > > serializable for dynamic cache support. So if eviction policy, for
> > example,
> > > depends on some non-serializable objects, it will be very hard to
> > > configure. It's probably a very rare use case, but we need to keep it
> in
> > > mind.
> > >
> >
> > This is a good point. I think we should make everything that can end up
> in
> > configuration as  Serializable. Would this be possible for eviction
> policy?
> >
> >
> >
> > >
> > > --
> > > Val
> > >
> >
>

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