Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

1) My testing shows that CassandraCacheStoreFactory is read from xml config once if the cache name does not exist in Ignite Persistence. It appears that CassandraCacheStoreFactory bean is persisted along with cache name in Ignite Persistence Store, CassandraCacheStoreFactory will not be re-instanti

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! Looks overall correct. Regards, -- Ilya Kasnacheev чт, 14 янв. 2021 г. в 11:43, xmw45688 : > 1) My testing shows that CassandraCacheStoreFactory is read from xml config > once if the cache name does not exist in Ignite Persistence. It appears > that > CassandraCacheStoreFactory bean is

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! 1) Can you please elaborate? If you set this value in a cache store factory, it will keep this boolean value and deserialize it when node is started. I'm not entirely sure if Ignite will store cache store factory or cache store instance in the persistent cache configuration. My expectation

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thanks for your recommendations! 1) The dynamicConfigurationReload is not able to reset once cacheStoreFactory is cached. It means that cacheStoreFactory does not read this value unless cacheStoreFactory is first instantiated. Do I miss something? Which factory should I put dynamicConfigurationR

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! This seems like a valid change, however, there are issues with it: if you don't have persistence settings files on some nodes, it will cause failure on these nodes. It may also re-read these files too eagerly in its current form. I can totally see how this may be an option to have in the C

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thanks for your clarifications, and appreciated your suggestions and guidance. My college and I went to ignite-cassandra module, commented two lines, */testing purpose/*, in org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.getPersistenceSettings(), see the changes below. Rem

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

, you may improve Cassandra cache store to track environment changes. Regards, -- Ilya Kasnacheev вт, 5 янв. 2021 г. в 04:38, xmw45688 : > Hi Ilya, > > Thanks for your guidance and happy new year! Sorry for late catchup. > > You are right, Ignite Native Persistence does track

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hi Ilya, Thanks for your guidance and happy new year! Sorry for late catchup. You are right, Ignite Native Persistence does track the changes in class definition for "Ignite Native Persistence". But the configuration to load data from Cache to Cassandra store is stored in xml con

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! Why do you think that change should be on Ignite Persistence side? You said yourself that Ignite Persistence tracks the changes in class definition, it's the Cassandra store that does not. Regards, -- Ilya Kasnacheev ср, 23 дек. 2020 г. в 00:17, xmw45688 : > Thanks for your suggestion,

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thanks for your suggestion, Ilya. Can you give me a reference to override default Cassandra Store implementation? I thought that the changes would be on Ignite Persistence side because caching data from standalone Cassandra store (with Ignite Persistence) did read configuration including class de

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! I think that maybe you could try coding such a cache store which will update this information. It's just that the default Cassandra store doesn't seem to. Regards, -- Ilya Kasnacheev сб, 19 дек. 2020 г. в 05:17, xmw45688 : > Thanks for your confirmation, Ilya. > > I do have a follow-up

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thanks for your confirmation, Ilya. I do have a follow-up question for you. When Ignite Persistence is used together with Cassandra. The caches for Cassandra table mappings are provided via xml file. The java class for the mappings is for BOTH Ignite Persistence and Cassandra cache store. Wh

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

assandra to > Ignite Cache stores using Cache.loadfull(). This works well for the > use > cases where 3rd party persistence store is used first, then Ignite Native > Persistence store is used with 3rd party persistence together later. > > However, the configuration of 3rd par

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thank you for your answer. I'm able to load the data from Cassandra to Ignite Cache stores using Cache.loadfull(). This works well for the use cases where 3rd party persistence store is used first, then Ignite Native Persistence store is used with 3rd party persistence together

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

It's seem to > me > that the keyspace are cached in the Ignite native persistence layer. > > How do I change the keyspaces of Cassandra? > > The use case is that we use Ignite as cache initially with the data stored > in Cassandra. With the data increase, caching all d

not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

space instead of the new keyspace that are in ignite config file. It's seem to me that the keyspace are cached in the Ignite native persistence layer. How do I change the keyspaces of Cassandra? The use case is that we use Ignite as cache initially with the data stored in Cassandra. Wit

Re: Ignite Native Persistence With write behind additional store

There is a typo in my previous message, I meant "Storages will be synchronized in case of one of the node failure." There is no reference for this type of configuration since there is no guarantee for the consistency. If you still want to use it, you can just combine configuration for persistence

Re: Ignite Native Persistence With write behind additional store

Hi, Thanks for the reply. is there a reference to configure custom store along with native persistence enabled. Thanks & Regards, Devakumar J -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Native Persistence With write behind additional store

Hi, There is no guarantee of data consistency between Ignite persistence and 3rd party DB in this case. Storages will be synchronized in case of one of the node failure. You can try to run some explicit checking for data consistency, but I believe it won't be easy with the load. Evgenii вт, 14 и

Ignite Native Persistence With write behind additional store

Hi, I am exploring ways to do data backup along with native persistence. Is it possible to achieve this using cache store implementation. So that data will be persisted in disk as well as replica copy. Thanks, Devakumar J -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: When trying to activate cluster to use ignite native persistence getting topology update failed error .

Hello! By default, information is logged to console (standard out). Please start your node with -DIGNITE_QUIET=false (or bin/ignite.sh -v) and copy-paste its output as you try to activate cluster. Regards, -- Ilya Kasnacheev чт, 27 февр. 2020 г. в 08:39, Preet : > I am new to Ignite. I do

Re: When trying to activate cluster to use ignite native persistence getting topology update failed error .

I am new to Ignite. I don't know how to check log. When I searched then I got to know that it is under /work/logs but I think that are static file. I don't know why activating cluster node is failing. I want to use persistence enabled feature for my IGFS application. -- Sent from: http://apache

Re: When trying to activate cluster to use ignite native persistence getting topology update failed error .

Hello! Do you see anything in server nodes' logs? Regards, -- Ilya Kasnacheev ср, 26 февр. 2020 г. в 14:31, Preet : > < > http://apache-ignite-users.70518.x6.nabble.com/file/t2787/Screenshot_2020-02-26_at_4.png > > > This is the error I received. Please help me to resolve this error. I wa

When trying to activate cluster to use ignite native persistence getting topology update failed error .

This is the error I received. Please help me to resolve this error. I want to use native persistence feature. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite native persistence

Hello! When running your reproducer, I don't see any "method will have no effect" messages, instead I can see in debugger that loadCache() is triggered and then com.gpc.rpm.IgniteCacheLoader.datagrid.store.spring.CacheSpringARInvoiceStore2#loadCache is called. Can you please describe the problem

Re: Ignite native persistence

Tried with appending cache name as schema with no success. Attach is a link to my project: https://drive.google.com/open?id=1F53um8TeUK45U3SOW0_Vlj04S8DWyjKI Please take a look. I suspect it is something in my code. Thanks, Naushad -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite native persistence

You might need to set the cache name as a schema for the queries. For instance, the query needs to be transformed to "Select ... {YOUR_CACHE_NAME}.ARInvoice FROM ..". Also, do you really need to have both 3rd party and native persistence enabled for the cluster. If the 3rd party is only used as an

Re: Ignite native persistence

ignite_sql_error.ignite_sql_error ARInvoiceRepository.java Attached is the file containing statcktrace and the r

Re: Ignite native persistence

Please send exception/error message you are getting and the query you are trying to execute. On Tue, Nov 26, 2019, 8:04 PM niamin wrote: > I found what I was doing wrong. I can now load/pre-fetch from 3rd party > store > to cache. It looks like the data is present in in-memory cache but also >

Re: Ignite native persistence

I found what I was doing wrong. I can now load/pre-fetch from 3rd party store to cache. It looks like the data is present in in-memory cache but also stored in the persistent store. However, when I run a native query configured on my SpringData Repository I get an error that the SQL table mentioned

Re: Ignite native persistence

Thanaks Denis. However, how do or should I preload the data to disk first? Or as Ignite fetches data from the 3rd part datastore it is expected to distribute between RAM and disk? Is there an example project that implements this strategy? On my POC, I have SpringBoot project that includes the Ignit

Re: Ignite native persistence

Hi there, Looks like you are trying to preload data from the persistence to memory with Cache.loadCache method. Presently, this operation is not supported for the native persistence and it’s optional - just start issuing your queries after the cluster restart and Ignite will get all the data neede

Ignite native persistence

What is the right way to enable native persistence? As per Ignite documentation, I added the following property to enable native persistence:

Re: Using Ignite Native Persistence as a "temporary durable" cache

: (modified section in above example) [image: image.png] On Thu, Sep 5, 2019 at 12:17 PM Alexander Korenshteyn < alexanderko...@gmail.com> wrote: > Hello, >Ignite native persistence has a good track record, is fast and > reliable, you can use it in your application. > >

Re: Using Ignite Native Persistence as a "temporary durable" cache

Hello, Ignite native persistence has a good track record, is fast and reliable, you can use it in your application. Take a look at the following example of how to use a streamer to quickly insert data: https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite

Using Ignite Native Persistence as a "temporary durable" cache

Hi all, We have MS SQL database server which contains all data. Our application will fetch some datas from database server and put them to the cache. And then, during 5-10 seconds we will do some updates to that objects and push that changes to ignite in-memory cache. And then, after 5-10 seconds

Re: SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

Are you available for a verbal conversation? I would invite a solution architect on a call to figure out if Ignite works or not for your use case. - Denis On Wed, May 15, 2019 at 10:17 PM Denis Magda wrote: > Hi, > > But after seeing your explanation below I understand that option 2 above is >

Re: SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

Hi, But after seeing your explanation below I understand that option 2 above is > not really the way Ignite is supposed to be used - even if it is on top of > hadoop. Did I get that right? In this configuration, Ignite will not be on top of Hadoop, it will be close to it - deployed as separate s

Re: SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

Hi Denis, Thank you very much for a good response. Definitely helps. Hope I can ask one follow-up question which I feel I did not make so clear from the beginning: The business has a very strong (non-negotiable) requirement on that the data warehouse should be modeled with high normalisation. Th

Re: SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

Hello, In short, Ignite persistence primary advantages are: - Enables multi-tiered storage across RAM and disk - 100% of data persisted to disk ("warm" and "cold" data sets) while "hot" data always stays in RAM. You lay out the data the way you need. Applications just run queries and

SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

Hi, I am in a project where we are building a new database with strong normalisation requirements - very much like a relational data warehouse. We source the data from HDFS. And the maintenance team requires the data movement to be implemented through SQL APIs. Main Question: Would it be a viabl

Re: pre-load data (Apache ignite native persistence store or Cassandra) into two partitioned cache tables

Hello! If you are using two rows as @AffinityKeyMapped, you can join other tables which use same two rows, BUT you can't join tables which use only first row as @AffinityKeyMapped or only second row. That's why you can join invoice_line to fact_purhcase_line - I guess they both have invoiceId and

Re: pre-load data (Apache ignite native persistence store or Cassandra) into two partitioned cache tables

Can some one comments on the following questions in my previous post? 4. fact_purhcase_line, invoice and invoice line via factLineId and InvoiceID do not work, please see annotation below public class InvoiceLineKey { /** Primary key. */ private long id; /** Foreign key to fact

Re: pre-load data (Apache ignite native persistence store or Cassandra) into two partitioned cache tables

Thanks for reply. I got the most working thanks to the example (https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/starschema/CacheStarSchemaExample.java) provided by Ignite. Here is my sql for POC (Cassandra DDL scripts) create table ignitet

Re: pre-load data (Apache ignite native persistence store or Cassandra) into two partitioned cache tables

rgCache.put(org.id, org); >} > >If I used Ignite native persistence store, how does Ignite cluster know > that both company and person are collocated? > > 2. How do I know that @AffinityKeyMapped annotated key comes from the > cache I need to map. I don't see the logi

pre-load data (Apache ignite native persistence store or Cassandra) into two partitioned cache tables

r org { personCache.put(affinityKey(p.id, org.id), org); } orgCache.put(org.id, org); } If I used Ignite native persistence store, how does Ignite cluster know that both company and person are collocated? 2. How do I know that @AffinityKeyMapped annotated key comes from the cache I need to ma

Re: How to add a new node to an existing cluster which Ignite native persistence is enabled?

-40c0-84fe-d0bb5226c720 Number of other nodes: 1 You can then add node e019f021-5988-40c0-84fe-d0bb5226c720 to your topology via "control.sh --baseline add". On Thu, Dec 20, 2018 at 5:47 AM soonjoin wrote: > Hi Team, I am testing Ignite on version 2.7.0. I used Ignite native > per

How to add a new node to an existing cluster which Ignite native persistence is enabled?

Hi Team, I am testing Ignite on version 2.7.0. I used Ignite native persistence and cache mode is PARTITIONED. I found there’s no data was stored in the node which joined the cluster after the cluster is already active，even though I deactivate the cluster and activate it again. I have to delete

Re: Ignite native persistence and replicated caches - should it even be possible?

Ilya, thank you very much for your response! Kamil Mišúth On 2018-12-17 15:13, Ilya Kasnacheev wrote: Hello! I'm not completely sure but persistent REPLICATED cache is the same as PARTITIONED with MAXINT backups. It means that every node will have a copy of data, but it has to be in BLT to be

Re: Ignite native persistence and replicated caches - should it even be possible?

Hello! I'm not completely sure but persistent REPLICATED cache is the same as PARTITIONED with MAXINT backups. It means that every node will have a copy of data, but it has to be in BLT to be used. Regards, -- Ilya Kasnacheev пн, 17 дек. 2018 г. в 14:46, kimec.ethome.sk : > Hi all, > > Could

Ignite native persistence and replicated caches - should it even be possible?

Hi all, Could somebody confirm my conclusion below? It seems it is possible to declare a REPLICATED cache configuration for caches that are mapped to a data region backed by the native persistence layer. Ignite does not complain about this configuration and boots happily. Yet, after cluster r

Re: Can Ignite native persistence used with 3rd party persistence?

wrote: > Created the ticket: https://issues.apache.org/jira/browse/IGNITE-7235 > > 2017-12-15 16:16 GMT+03:00 Alexey Goncharuk : > >> Ray, >> >> With the current API it is impossible to get a reliable integration of >> Ignite native persistence with 3rd party persistenc

Re: Can Ignite native persistence used with 3rd party persistence?

Created the ticket: https://issues.apache.org/jira/browse/IGNITE-7235 2017-12-15 16:16 GMT+03:00 Alexey Goncharuk : > Ray, > > With the current API it is impossible to get a reliable integration of > Ignite native persistence with 3rd party persistence. The reason is that > fi

Re: Can Ignite native persistence used with 3rd party persistence?

Ray, With the current API it is impossible to get a reliable integration of Ignite native persistence with 3rd party persistence. The reason is that first, CacheStore interface does not have methods for 2-phase commit, second, it would require significant changes to the persistence layer itself

Re: Can Ignite native persistence used with 3rd party persistence?

Hi Ray, > One more question here, how can a update or new inserts back-propagate to > Ignite when another application(not ignite) writes to persistence(hbase)? It is not supported. On Fri, Dec 1, 2017 at 12:08 PM, Ray wrote: > http://apache-ignite-users.70518.x6.nabble.com/Two- > persisten

Re: Can Ignite native persistence used with 3rd party persistence?

http://apache-ignite-users.70518.x6.nabble.com/Two-persistent-data-stores-for-a-single-Ignite-cluster-RDBMS-and-Ignite-native-td18463.html Found a similar case here, I think I'll try Slava's suggestions first. One more question here, how can a update or new inserts back-propagate to Ignite when a

Can Ignite native persistence used with 3rd party persistence?

Ignite native persistence provides on-disk sql query and quick cluster startup without data loading, so we definitely want to use it. But we have a legacy hbase served as persistence layer and there are some business rely on it. So can Ignite native persistence used with 3rd party persistence

RE: Strange problems with Ignite native Persistence when Data exceeds Memory

-configuration#memory-policies Thanks! -Dmitry. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Strange-problems-with-Ignite-native-Persistence-when-Data-exceeds-Memory-tp16187p16336.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

RE: Strange problems with Ignite native Persistence when Data exceeds Memory

this thread. Thanks... Roger -Original Message- From: dkarachentsev [mailto:dkarachent...@gridgain.com] Sent: Tuesday, August 15, 2017 12:04 AM To: user@ignite.apache.org Subject: Re: Strange problems with Ignite native Persistence when Data exceeds Memory Hi Roger, It looks like not all

Re: Strange problems with Ignite native Persistence when Data exceeds Memory

this message in context: http://apache-ignite-users.70518.x6.nabble.com/Strange-problems-with-Ignite-native-Persistence-when-Data-exceeds-Memory-tp16187p16194.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Strange problems with Ignite native Persistence when Data exceeds Memory

Hello, I am running into strange problems with Ignite Native Persistence when the data exceeds the size of the cache (memory). I have 3 nodes with 8 GB each, one cache, using 1 backup. I am using SQL queries, and the cache has 3 indexes. I am loading 9.6M objects, using IgniteDataStreamer in