Sergey,
The issue vanishes as soon as I add the following to the configuration:
<property name="memoryConfiguration">
<bean class="org.apache.ignite.configuration.MemoryConfiguration">
</bean>
</property>
My point is that we just need to create a MemoryConfiguration implicitly if
it’s not defined (no any warnings or extra messages). It’s a responsibility of
our platform to generate a default configuration if it’s not set explicitly.
—
Denis
> On May 26, 2017, at 8:46 AM, Sergey Chugunov <sergey.chugu...@gmail.com>
> wrote:
>
> Hi Denis,
>
> What is the expected behavior in that case? Bug doesn't suggest any.
>
> From my point of view it would be better to throw an exception on startup
> with meaningful message than to silently create a default
> MemoryConfiguration under the cover.
>
> Thanks,
> Sergey.
>
> On Fri, May 26, 2017 at 4:00 AM, Denis Magda <dma...@apache.org> wrote:
>
>> Igniters,
>>
>> I’ve just added the first Persistent Store example to the branch that
>> fosters the donation:
>> https://github.com/apache/ignite/tree/ignite-5267/
>> examples/src/main/java/org/apache/ignite/examples/persistentstore
>>
>> However, the example fails with an NPE if a MemoryConfiguration is not
>> defined explicitly:
>> https://issues.apache.org/jira/browse/IGNITE-5295
>>
>> Please those who are involved in the store development fix the issue by
>> the end of tomorrow. I want to complete with the technical documentation
>> referring to a workable example.
>>
>> —
>> Denis
