http://apache-ignite-developers.2346864.n4.nabble.com/IgniteBinary-POJOs-and-indexing-tp6447p6759.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
there is no "persistent configuration
>> storage" to store the dynamic cache configs, and Ignite doesn't even try to
>> recreate them after a full cluster restart -- it's the use who does that,
>> either in the code or thru the configuration files.
>>
>
figs, and Ignite doesn't even try to
> recreate them after a full cluster restart -- it's the use who does that,
> either in the code or thru the configuration files.
>
> Thanks
> Andrey
>
> > From: sergi.vlady...@gmail.com
> > Date: Sat, 9 Jan 2016 13:10:13 +
uration files.
Thanks
Andrey
> From: sergi.vlady...@gmail.com
> Date: Sat, 9 Jan 2016 13:10:13 +0300
> Subject: Re: IgniteBinary, POJOs and indexing
> To: dev@ignite.apache.org
>
> I don't think we can easily implement this feature. Because it means that
> we need some k
I don't think we can easily implement this feature. Because it means that
we need some kind of "persistent configuration storage", which will be
consistent in all the scenarios of failures/restarts. So we have to design
this thing first keeping in mind that in the future we will store there not
onl
Hi Andrey,
The answer right now is simple. Yes, you can create classes and add fields
at runtime. No, you cannot change indexes that you have created in cache
configuration.
However, you are raising a very valid point. We should be able to create
and update indexes dynamically. There is a ticket
Hello, Ignite Community,
IgniteBinary javadocs mention the ability to dynamically change the structure
of the "classes" without restarting the cluster. The javadocs even say that the
new fields become automatically available to the SQL queries with no extra
effort. It's all fine and dandy, but
