Re: IgniteBinary, POJOs and indexing

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

[jira] [Created] (IGNITE-2343) IGFS: MapReduce task sent by Hunk/Splunk fails with NPE

Denis Magda created IGNITE-2343: --- Summary: IGFS: MapReduce task sent by Hunk/Splunk fails with NPE Key: IGNITE-2343 URL: https://issues.apache.org/jira/browse/IGNITE-2343 Project: Ignite Issue

[jira] [Created] (IGNITE-2344) WebSessionFilter doesn't support session ID renewal

Denis Magda created IGNITE-2344: --- Summary: WebSessionFilter doesn't support session ID renewal Key: IGNITE-2344 URL: https://issues.apache.org/jira/browse/IGNITE-2344 Project: Ignite Issue

IgniteBinary, POJOs and indexing

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

Re: Javadoc link need to be updated

Thanks Roman! I updated the link. On Thu, Jan 7, 2016 at 7:40 PM, Roman Shtykh wrote: > Igniters, > > I noticed Javadoc link on https://apacheignite.readme.io/ points to the > older 'b1' version, instead of 'final' >