Re: Ignite Cassandra write error

As far as you are doing BULK_WRITE, you summary size of the batch (consisting of several Ignite cache objects) could be rather big. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Cassandra write error

Check your Cassandra cluster. According to the exception, Cassandra driver didn't receive even 1 success write response: *Caused by: com.datastax.driver.core.exceptions.WriteFailureException: Cassandra failure during write query at consistency LOCAL_ONE (1 responses were required but only 0 repl

Re: map types in Cassandra

Ignite-Cassandra module doesn't support Cassandra complex types like map. Only BLOB and simple types which could be directly mapped to appropriate java types are supported. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

That's exactly what I am talking about. You have col10 after col4, because of this you are inserting nulls into col5 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Hm... Did you provide right source code for the classes and CQL statements? Here is the sample of INSERT statement you previously provided: *INSERT INTO test_response (col1,col2,col3,col4,col10,col5,col6,col7,col8,col9) VALUES ('text1','$03','FLAG',1491843013376,60,null,null,'C39A9EFB7E',1,'NA')

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Hi Kenan, Either your *examples.cassandra_persistence_store.model.TestResponse* implementation is incorrect or you just accidentally inserting incorrect values into your Cassandra table. Here are the details: 1) *col5* field in *TestResponse* class has *long* type - which means that it's not nul

Re: Cassandra Cache Store: How are loadCache() queries distributed

Hi Roger, As of now Cassandra Cache Store *loadCache()* implementation is pretty straightforward - it sends all provided CQL queries from all Ignite nodes. There is no query analysis to distribute data loading routine among cluster nodes. There is an enhancement ticket created for this: https://i

Re: Question on efficient loading from Cassandra

Hi Nikolai, As for now Ignite-Cassandra module always executes same CQL query on each node while doing loadCache(...). But you assumptions are right and there is a ticket for this: https://issues.apache.org/jira/browse/IGNITE-3962 Igor On Thu, Jul 27, 2017 at 10:28 AM, Nikolai Tikhonov wrot

Re: apache ignite cassandra persistentStore for enum fields

Hi, You can store enum field as a blob using Cassandra module for Ignite, but you should manually specify this in your persistence descriptor. Igor On Jul 14, 2017 12:25 AM, "babak" wrote: > hi, > > I have a model with enum field. I insert the model to the ignite cache and > the enum field is

Re: Using Ignite as the SQL Engine for Cassandra

Hi Roger, You can use Ignite-Cassandra integration module. In case you need to load specific portion of you Cassandra dataset into Ignite you can use *loadCache(...)* method of Ignite cache API, providing it appropriate CQL query. Igor On Tue, Jul 11, 2017 at 8:29 PM, Roger Fischer (CW) wrote:

Re: Ignite Cassandra Exception

By the way - you have just warning messages or errors? If warnings than it's not critical and means that there were made several attempts to persist your data into Cassandra. In case you have errors you should add more nodes to Cassandra cluster and redistribute data among them. Anyway warning/

Re: Ignite Cassandra Exception

Could you please also provide the logs? Cassandra module was tested with *Cassandra Driver 3.0.0* and *Cassandra Database 3.3*. As far as you are using another version of driver and database, the exception you receiving could be slightly different from the exception we are trying to handle. That

Re: Ignite Cassandra Exception

Cassandra module actually handles such type of exception here: https://github.com/apache/ignite/blob/master/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L164

Re: Ignite Cassandra Exception

Could you please provide full stack trace? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cassandra-Exception-tp13529p13540.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite to Cassandra change from 1.9 to 2.0

There is also patch IGNITE-5368 available which allows you to use annotations for class fields instead of getters/setters. It will be available in the next version of Ignite. -- View this message in context: http://apache-ignite-users.70518

Re: Ignite to Cassandra change from 1.9 to 2.0

The second problem is that your *HistoryResultKey* doesn't have setters. It will not work without setters - your POJO classes should follow Java Beans convention. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-to-Cassandra-change-from-1-9-to-2-0-tp13099p1

Re: Ignite to Cassandra change from 1.9 to 2.0

First of all - annotations *@QuerySqlField* and *@QueryTextField* are no longer supported for the methods. Because of this simplified persistence descriptor doesn't work as expected. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-to-Cassandra-change-from-

Re: Ignite to Cassandra change from 1.9 to 2.0

Could you please provide full exception stack trace? What do you mean by upgraded to version 2.0? Is it Cassandra or Ignite version or something else? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-to-Cassandra-change-from-1-9-to-2-0-tp13099p13108.html Se

Re: what is the right way to run tests against Cassandra module?

Hi Alexei, Tests for Cassandra module should be executed just using standard maven approach: mvn clean test Igor On Apr 19, 2017 6:40 AM, "Alexei Kaigorodov" wrote: > the document DEVNOTES.txt says to run maven with argument > -Dtest=%TEST_PATTERN% > but cassandra test are placed in package or

Re: Timestamp is not stored correctly with Cassandra

Hello, It works for long, but doesn't work for Timestamp cause there are no direct mapping ( http://docs.datastax.com/en/developer/java-driver/3.1/manual/#cql-to-java-type-mapping ) from java.sql.Timestamp t

Re: Mapping java.util.Map in CassandraPersistentStore

Hello, As for now it's only supported mapping for simple java types which could be directly mapped http://docs.datastax.com/en/developer/java-driver/3.1/manual/#cql-to-java-type-mapping to corresponding CQ

Re: Ignite with Cassandra questions / errors

Hi Kenan, You missed the main point - getters or setters of your custom classes should be annotated with *@QuerySqlField* instead of class private members. Here is a slightly modified version of your custom classes which should work: == import org.apache.ignite.ca

Re: Ignite with Cassandra questions / errors

Ok, I took a look at the *HistoryResult* implementation once again and found the reason. Your java class should follow JavaBeans Conventions . The most important here is that you class should implement getters/setters methods for READ/WR

Re: Ignite with Cassandra questions / errors

Hi, This is not actually 100% true - Cassandra integration supports @QuerySqlField annotations to create tables and doing mapping between object fields and table columns. Kenan, have you tried Cassandra DDL generator https://apacheignite-mix.readme.io/docs/ddl-generator for your persistence descr

Re: Cassandra cache info

Hi Riccardo, It depends on how you are asking for the record which is not in Ignite cache. If you are doing this using *get* method of Ignite cache API it will load this record from DB (if it's not already in Ignite cache), put it into in-memory cache and return it to you. But if you are using Ig

Re: Ignite Cassandra AWS test framework

t; the status of the process was not updated into the S3 folder as suggested > in the documentation. > > Could it be for some reason that I get a test-package from the src code > which does not include the needed files (maybe some build errors)? > > Have a nice day > > Riccard

Re: Ignite Cassandra AWS test framework

Ok guys, just updated the documentation. Igor On Thu, Dec 1, 2016 at 4:44 PM, Igor Rudyak wrote: > Hi Riccardo, > > Thanks for noticing this. That's a documentation issue. There were number > of refactorings for Ignite-Cassandra and documentation now is not 100% up > to d

Re: Ignite Cassandra AWS test framework

Hi Riccardo, Thanks for noticing this. That's a documentation issue. There were number of refactorings for Ignite-Cassandra and documentation now is not 100% up to date. Igor On Thu, Dec 1, 2016 at 3:13 PM, Riccardo Iacomini < riccardo.iacom...@rdslab.com> wrote: > Hi Val, > > No, that's not th

Re: Cassandra basic setup

> Best Regards > > Riccardo Iacomini > > > *RDSLab* > > On Tue, Nov 29, 2016 at 11:18 PM, Igor Rudyak wrote: > >> Ok, thanks for the info. >> >> Igor >> >> On Tue, Nov 29, 2016 at 12:56 PM, Denis Magda wrote: >> >>> Igor,

Re: Cassandra basic setup

t; > — > Denis > > On Nov 29, 2016, at 11:49 AM, Denis Magda wrote: > > Igor, > > Please hold on for a while. I’ve just started moving all the integrations > related documentation to a new domain. I’ll let you know when it’s safe to > update the doc. > > — >

Re: Cassandra basic setup

rsion of the documentation in contrast with the > one I was running. > > Anyway, thank you for your time. > > Best regards > > Riccardo Iacomini > > > *RDSLab* > > On Mon, Nov 28, 2016 at 5:34 PM, Igor Rudyak wrote: > >> If you are using ignite.sh it sh

Re: Cassandra basic setup

If you are using ignite.sh it should be fine. Igor On Nov 28, 2016 8:29 AM, "Riccardo Iacomini" wrote: > I will try. Yes I am using the ignite.sh command. Any drawbacks? > > Il 28 nov 2016 5:26 PM, "Igor Rudyak" ha scritto: > > Try to check your classpath.

Re: Cassandra basic setup

he image as specified here > <https://apacheignite.readme.io/v1.5/docs/docker-deployment> in the > documentation. Do you have any other suggestion? > > Thanks for your patience. > > Best regards > > Riccardo Iacomini > > > *RDSLab* > > On Sun, Nov 27, 2016 at 8:46 PM, Ig

Re: Cassandra basic setup

the jar ignite-cassandra-1.7.0.jar in > IGNITE_HOME/modules/cassandra/target. I tried adding the path to > USER_LIBS and CLASSPATH, no different behavior. Maybe the environment > variables got ignored? > > > Riccardo Iacomini > > > *RDSLab* > > On Wed, Nov 23, 2016 at 7:41 PM,

Re: Cassandra basic setup

Hi Riccardo, *CassandraAdminCredentials *class is only available in Ignite unit tests sources. If you want to use it you should build Ignite from source code. Such way, it will create *ignite-cassandra-tests-${project.version}.zip* where jar may find jar file containing all the test classes. Also

Re: Cannot query on a cache using Cassandra as a persistent store

Hi Guang, If Cassandra table structure changed you should also change Ignite cache mapping settings specified by Cassandra persistence descriptor. For this, you need to destroy and recreate your cache or you can just create another cache with the most actual mapping settings. Yes you are free to

Re: Cannot query on a cache using Cassandra as a persistent store

Hi Guang, You can specify your custom IgniteBiPredicate implementation if you need some custom pre-processing for each key-value pair loaded from persistent store. Yes you can pass more that one query using something like that: cache3.loadCache(null, "select * from my_table_1", "select * from m

Re: Cannot query on a cache using Cassandra as a persistent store

Hi Guang, Try this: *cache3.loadCache(null, new String[] {"select * from test1.pojo_test3 limit 10"});* -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cannot-query-on-a-cache-using-Cassandra-as-a-persistent-store-tp7870p7918.html Sent from the Apache Ignite

Re: Ignite with Cassandra

The reason is in *"id"* field. According to the persistence descriptor, cache key will be stored in "id" field, but at the same time User POJO class also has such field. There are several options to fix this: 1) Specify another column mapping for Ignite cache key. For example: ** 2) Specify non d

Re: Ignite with Cassandra

Could you please provide full definition of key and value classes and xml persistence descriptor you are using for Ignite cache? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-with-Cassandra-tp7242p7331.html Sent from the Apache Ignite Users mailing list

Re: Cassandra - Ignite Exception

GridWorker.java:110) > [ignite-core-1.6.0.jar:1.6.0] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > [?:1.7.0_40] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > [?:1.7.0_40] >

Re: Cassandra - Ignite Exception

reate table" is executed simultaneously from multiple clients (Ignite nodes in our case) it could cause such an error in the log. Regards, Igor Rudyak On Fri, Aug 12, 2016 at 12:20 PM, vkulichenko wrote: > Hi Kamal, > > I would ask on the Cassandra forum about this. Can you do this? The

Re: Any plan for a book on Apache Ignite

Looks cool!!! Igor On Fri, Aug 12, 2016 at 12:48 PM, Denis Magda wrote: > Cross-posting to the dev list. > > Wow, this is great. Are you the one of the authors? > > — > Denis > > > On Aug 12, 2016, at 12:08 PM, srecon wrote: > > > > One book is going to publish soon, you can check the table of

Re: Cassandra Cache Store Example

y normal to have billions partitions in Cassandra. Igor Rudyak On Fri, Jul 15, 2016 at 12:03 AM, Kamal C wrote: > Val, > > I too have some concerns to use cassandra partitioned table. For initial > version, I'm using PRIMITIVE / BLOB > persistent strategy to store the key-v

Re: Cassandra Cache Store Example

Ignite partitions are two absolutely different animals, it doesn't make sense to compare them. Just check that you are using @AffinityKeyMapped annotation for your key classes. In a such way all the values having same affinity will be persisted on the same Cassandra node. Igor Rudyak On Thu, J