Re: Should Ignition.start() method to be called in a spark-igniteRDD app?

What makes me very confused is that when I use ignite to run a spark word count app, it did not ask me to call 'Ignition.start()', while I use igniteRDD to cache table and just run a spark streaming app, the console throw the exception. What's the difference? -- View this message in context: ht

Re: Should Ignition.start() method to be called in a spark-igniteRDD app?

I added 'Ignition.start()' in my first line of the 'main' method, but still got the same error, add also notified that it seems the approach I use to start ignite in spark cluster is wrong, the ignite instance is more than I expected, there is 3 worker nodes in my cluster . I use '${IGNITE_HOME}/bi

Re: Cache write-through for backup entries

Hi, Store is not updated on backup nodes because Ignite assumes that the store is some kind of shared storage. Can you provide more details on your use case? How are going to use the data written to the store afterwards? -Val -- View this message in context: http://apache-ignite-users.70518.x

Re: How to configure user data type for sql queries?

Hi, This is currently not supported with binary format, which is default. There is a ticket to fix this: https://issues.apache.org/jira/browse/IGNITE-2208 As a workaround you can switch to OptimizedMarshaller. Add this to your configuration: Let me know if it helps. -Val

Re: Should Ignition.start() method to be called in a spark-igniteRDD app?

Hi, The code there is not completely correct and there is a ticket for that [1]. Essentially, if there is some kind of misconfiguration, the corresponding exception will be lost and the one you got will be thrown. Most likely that's what happening in your test. I would recommend to execute a Spar

Re: Getting ignite import errors

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 akriti91 wrote > I'm getting errors on all Ignite imports like: > >

Re: Getting Retrying preload partition exchange due to timeout waring a lot

Hi Sandeep, The first thing I would check is the memory consumption. Make sure that nodes do not run out of memory and do not suffer from long GC pauses. If this is not the case, please attach full log files from both nodes. -Val -- View this message in context: http://apache-ignite-users.705

How to configure user data type for sql queries?

One of my cache fields is a custom type MyCustomDateType implements Serializable, Comparable. How can I map this type to be able to query via sql? I have tried the following, but was not able to get the sql result. H2 Console shows the column data type for this field as (OTHER): /

Re: Ignite Schema Import Utility - BinaryMetadata mismatch error when using gerenated classes

Alexey, We have nightly builds running on Jenkins: https://builds.apache.org/view/H-L/view/Ignite/job/Ignite-nightly/lastSuccessfulBuild/ Is this what you need? D. On Fri, Apr 1, 2016 at 8:16 AM, Alexey Kuznetsov wrote: > Jan, > > I think it is know bug. > > See https://issues.apache.org/jir

Getting Retrying preload partition exchange due to timeout waring a lot

Hi, I am starting a two node grid with a cluster singleton service, which has a partitioned cache. Once in a while, both the nodes start fine, however most of the times, I am seeing this warning repeatedly on one of the server nodes: 2016-04-01 08:28:58 WARN [sys-#18%DistEvtSch%] GridDhtPartitio

Re: Ignite Schema Import Utility - BinaryMetadata mismatch error when using gerenated classes

Jan, I think it is know bug. See https://issues.apache.org/jira/browse/IGNITE-2849 This issue is already closed. Could you check this using master branch? You will need to build sources from master and check. Any way it will be available in next release. It seems that Ignite missing nightly bu

Re: Ignite Schema Import Utility - Case mismatch between table index and query index defined in generated code

Jan, It seems a bug in code generator, I will take a look and fix next week. Thanks for pointing this out. I will update this thread when I fix this issue. On Fri, Apr 1, 2016 at 7:32 PM, jan.swaelens wrote: > Hello, > > Continuing my initial mention of this problem in another thread > < > h

Cache write-through for backup entries

Hi, I would like to implement cache write through for both primary and backup entries. The use-case is to maintain a backup of the cache on disk on each DDM node. I have implemented CacheWriter but it is only called for primary entries, not backup entries. Is there a way that I can implement thi

Re: Should Ignition.start() method to be called in a spark-igniteRDD app?

I've no idea about how the Ignition.start() method was called in the ignite kernel. Is there some document to refer to? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Should-Ignition-start-method-to-be-called-in-a-spark-igniteRDD-app-tp3854p3860.html Sent from

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Thank you! I registered two additional threads for the problems, referring back to this one in terms of generated collaterals, hope that is ok. br jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-when-loading-data-betwee

Ignite Schema Import Utility - Case mismatch between table index and query index defined in generated code

Hello, Continuing my initial mention of this problem in another thread where more information such as DDL and generated code can be found: Looki

Ignite Schema Import Utility - BinaryMetadata mismatch error when using gerenated classes

Hello, I get an error which stops the cache from loading in 'BinaryUtils.mergeMetadata' when it tries to merge two values for the 'nameMlid' field. At a certain point it generates a mismatch error because newFieldTypeName is set to long and OldFieldTypeName is set to Object. The trace leading to

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Jan, I think it will be better to start separate threads. As of IGNITE-2936 I will review Vasiliy code and merge into master in a couple of days. On Fri, Apr 1, 2016 at 6:26 PM, jan.swaelens wrote: > Thanks! > > For the two other cases (case mismatch on index and binary mismatch), > should > I s

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Thanks! For the two other cases (case mismatch on index and binary mismatch), should I start a separate thread or will we continue this in the current one? best regards jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-wh

Should Ignition.start() method to be called in a spark-igniteRDD app?

I got an error when I submit a jar. The cluster does not seems to be wrong, since I've tested it using the official guide: https://apacheignite-fs.readme.io/docs/ignitecontext-igniterdd#section-running-sql-queries-against-ignite-cache

Re: visor keep trigger alert when condition no longer satisfied?

Problem reproduced. Created issue: https://issues.apache.org/jira/browse/IGNITE-2930 -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/visor-keep-trigger-alert-when-condition-no-longer-satisfied-tp3772p3853.html Sent from the Apache Ignite Users mailing list archiv

Re: How to solve the 22 parameters' limit under scala 2.10 in the case class?

Thank you for your advice , I hope it will work, at least the compilation did not throw any exception. But I got another error when I submit the jar. The cluster does not seems to be wrong, since I've tested it using the official guide: https://apacheignite-fs.readme.io/docs/ignitecontext-igniterd

Re: How to solve the 22 parameters' limit under scala 2.10 in the case class?

Why do you need case classes? It is possible to use usual classes? Here my code that works: import org.apache.ignite.cache.query.annotations.{QuerySqlField, QueryTextField} import scala.annotation.meta.field /** * Scala wrappers for java SQL annotations. */ object SqlAnnotations { type Sc

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Hello @jan.swaelens I reproduce you problem. Issue https://issues.apache.org/jira/browse/IGNITE-2936 is created. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-when-loading-data-between-Date-and-Timestamp-tp3790p3850.html S

Re: How to solve the 22 parameters' limit under scala 2.10 in the case class?

Here are some details: I created the case class A which parameter is less than 22 and the case class B which has more than 22 parameters, I want to let ignite to create index on the fields , so the case class is like: ---

Re: A question of ignite on spark streaming

vkulichenko: Thanks for your carefulness, I put the query string into the 'sql' method, hope it well works well, but when I compile this maven project, I meet another problem and post another question in this forum : *

How to solve the 22 parameters' limit under scala 2.10 in the case class?

*Description:* I have two tables to join in spark - ignite hyper environment. one has 20 fields, the other has 40 fields, I *can not create more than 22 params in a case class under scala 2.10*(It has solved in scala 2.11, but for some reason, *I can not use 2.11 in my environment)*. The ign