Null as a name for default memory policy?

[dmagda]

Folks,

Are we sure we want to use ‘null’ as a name for the default policy if it’s not configured explicitly? Presently, MemoryConfiguration.getDefaultMemoryPolicyName suggests ‘null’ as a default one.

I’m bringing this to your attention only because in AI 2.0 we’re trying to get rid of ‘null’ as a default for the cache name but, strangely, we keep following this criticized approache in the new API.

—
Denis

[dsetrakyan]

How about we name it "default"?

On Mon, Apr 17, 2017 at 5:53 PM, Denis Magda <[hidden email]> wrote:

> Folks,
>
> Are we sure we want to use ‘null’ as a name for the default policy if it’s
> not configured explicitly? Presently, MemoryConfiguration.getDefaultMemoryPolicyName
> suggests ‘null’ as a default one.
>
> I’m bringing this to your attention only because in AI 2.0 we’re trying to
> get rid of ‘null’ as a default for the cache name but, strangely, we keep
> following this criticized approache in the new API.
>
> —
> Denis
>
>

[dmagda]

Sounds good to me. Other thoughts?

—
Denis

> On Apr 17, 2017, at 5:54 PM, Dmitriy Setrakyan <[hidden email]> wrote:
>
> How about we name it "default"?
>
> On Mon, Apr 17, 2017 at 5:53 PM, Denis Magda <[hidden email]> wrote:
>
>> Folks,
>>
>> Are we sure we want to use ‘null’ as a name for the default policy if it’s
>> not configured explicitly? Presently, MemoryConfiguration.getDefaultMemoryPolicyName
>> suggests ‘null’ as a default one.
>>
>> I’m bringing this to your attention only because in AI 2.0 we’re trying to
>> get rid of ‘null’ as a default for the cache name but, strangely, we keep
>> following this criticized approache in the new API.
>>
>> —
>> Denis
>>
>>

[Alexey Kuznetsov-2]

+1 to "default".


On Tue, Apr 18, 2017 at 8:01 AM, Denis Magda <[hidden email]> wrote:

> Sounds good to me. Other thoughts?
>
> —
> Denis
>
> > On Apr 17, 2017, at 5:54 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
> >
> > How about we name it "default"?
> >
> > On Mon, Apr 17, 2017 at 5:53 PM, Denis Magda <[hidden email]> wrote:
> >
> >> Folks,
> >>
> >> Are we sure we want to use ‘null’ as a name for the default policy if
> it’s
> >> not configured explicitly? Presently, MemoryConfiguration.
> getDefaultMemoryPolicyName
> >> suggests ‘null’ as a default one.
> >>
> >> I’m bringing this to your attention only because in AI 2.0 we’re trying
> to
> >> get rid of ‘null’ as a default for the cache name but, strangely, we
> keep
> >> following this criticized approache in the new API.
> >>
> >> —
> >> Denis
> >>
> >>
>
>

--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[Sergey Chugunov]

Guys,

I created a ticket for this as a subtask of IGNITE-3488
<https://issues.apache.org/jira/browse/IGNITE-3488>; you can find it
IGNITE-5025 <https://issues.apache.org/jira/browse/IGNITE-5025>

Thanks,
Sergey.

On Tue, Apr 18, 2017 at 5:20 AM, Alexey Kuznetsov <[hidden email]>
wrote:

> +1 to "default".
>
>
> On Tue, Apr 18, 2017 at 8:01 AM, Denis Magda <[hidden email]> wrote:
>
> > Sounds good to me. Other thoughts?
> >
> > —
> > Denis
> >
> > > On Apr 17, 2017, at 5:54 PM, Dmitriy Setrakyan <[hidden email]>
> > wrote:
> > >
> > > How about we name it "default"?
> > >
> > > On Mon, Apr 17, 2017 at 5:53 PM, Denis Magda <[hidden email]>
> wrote:
> > >
> > >> Folks,
> > >>
> > >> Are we sure we want to use ‘null’ as a name for the default policy if
> > it’s
> > >> not configured explicitly? Presently, MemoryConfiguration.
> > getDefaultMemoryPolicyName
> > >> suggests ‘null’ as a default one.
> > >>
> > >> I’m bringing this to your attention only because in AI 2.0 we’re
> trying
> > to
> > >> get rid of ‘null’ as a default for the cache name but, strangely, we
> > keep
> > >> following this criticized approache in the new API.
> > >>
> > >> —
> > >> Denis
> > >>
> > >>
> >
> >
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>