Re: Number of servers and lambdas ?

Hi, Can you please properly subscribe to the mailing list so that the community receives email notifications? Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 limabean wrote > I have a question about lambdas and Ignite servers.

Re: Unable to cache beyond RAM memory. Help me PLease!!!

Hi Bhargav, Can you please properly subscribe to the mailing list so that community receives email notifications? Follow the instructions here: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 bhargav wrote > I am trying to check the option of ignite,

Re: index and query org.apache.ignite.spark.IgniteRDD[String,org.apache.spark.sql.Row]

Yep, BinaryObjectBuilder should definitely be a solution for this. You can obtain an instance of Ignite from IgniteContext and use the IgniteBinary interface to get an instance of BinaryObjectBuilder to build object structures dynamically. And you can use QueryEntity class to describe the index

Re: @QuerySqlField for collections

Hi DmitryB, Could you please provide the full class name of "List"? Is it java.util.List or some Scala collection? Can you try putting java.util.ArrayList and see if it works? Vladimir. On Fri, Mar 4, 2016 at 6:59 AM, DmitryB wrote: > Hi team, > > I found that fields with

Re: index and query org.apache.ignite.spark.IgniteRDD[String,org.apache.spark.sql.Row]

Dmitry, case classes are needed only for Sprak sqlContext.createDataFrame method because type parameter should be scala.Product. Ignite doesn't imply such limitations to user types. I have no ideas how to use dynamic structures. Alexey Goncharuk, can we use BinaryObject for this case? May be

Re: Version issue with concurrent cache updates (EntryProcessor)

Thanks Alexey, I will consider an option to get familiar more deeply with product and contribute some patch. 2016-03-04 1:03 GMT+02:00 Alexey Goncharuk : > Myron, > > I believe IGNITE-2645 should be fixed in the near future since the issue > is critical, and will