Re: Failover in thin client mode

Hi Igor, I just checked the jiras and found this IPE has not been implemented for *java thin client* yet ? https://issues.apache.org/jira/issues/?jql=project%20%3D%20Ignite%20AND%20labels%20IN%20(iep-23)%20ORDER%20BY%20status%20%20%20%20%20%20%20 -- Sent from:

What's the difference between ClientCache#removeAll() and ClientCache#clear()

Here is the code snippet from org.apache.ignite.client.ClientCache what's the difference between these two methods? * /** * Clears the contents of the cache. */ public void clear() throws ClientException; /** *

Re: Failover in thin client mode

Not sure my understanding is correct or not. There is the case when a new node join a cluster, if it's just as your said then some key can not get directly from *the new added node* I suppose it would work as below. 1: 5 node cluster(a,b,c,d,e) 2: even I just set two nodes/endpoints in the

Re: Failover in thin client mode

Thank your information very much! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Failover in thin client mode

>From the document https://apacheignite.readme.io/docs/java-thin-client-initialization-and-configuration knows that ignite **thin** client mode failover is achieved by specified multiple hosts(endpoints). But I know there is a new feature called IEP-23: Best Effort Affinity for thin clients

Re: Most efficient way to update a specific field of a Value in cache

Can you use sql update clause to achieve this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: When I use Ignite create table ddl，can I set the db schema instead of the schema name "PUBLIC"？

Thank you very much! That's really what I want! Hope it will be released in 2.8. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: When I use Ignite create table ddl，can I set the db schema instead of the schema name "PUBLIC"？

For the case describe in the thread http://apache-ignite-users.70518.x6.nabble.com/Re-Can-t-add-new-key-value-pair-to-existing-cache-via-sql-command-td25126.html#none is there a jira trick it ? or when this

What's the difference between client node, jdbc driver and thin client

from the document client node: https://apacheignite.readme.io/docs/clients-vs-servers jdbc driver: https://apacheignite-sql.readme.io/docs/jdbc-client-driver thin client: https://apacheignite.readme.io/docs/java-thin-client when a node runs with *client mode*, it will join the cluster

Re: Can't add new key/value pair to existing cache via sql command

or can I log a feature ticket? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Can't add new key/value pair to existing cache via sql command

is there any timeline to release such limit? I have use ignite in production in my sub-system. it works so far so good, the only one exception is that every time I add new table I have to define a new cache. I think it's ok when the system is small. In fact I would like to use ignite in my another

Is it safe to decrease the data region size for a live cluster

There are 3 nodes in our cluster with persistent enabled. each node has 256G memory And there are already some data in the cluster. here is my data region configuration. dataRegion: RP.initialSize: 50L * 1024 * 1024 * 1024 RP.maxSize: 80L * 1024 * 1024 * 1024

what's the backend table behavior when issue IgniteCache.put(k,v) on an existing key-value pair

when persistence enabled, when call IgniteCache.put(k,v) with a `NEW` key-value pair, it's obviously that there is a new `INSERT` sql generated and the values will be inserted into the backend table. but for the case when I want to update the properties of the value entity (eg, the weight

Re: New added property with @QuerySqlField does not persist

Thank you very much! how to handle this case in production? it's too common to add new attribute to a new cache/pojo attribute.!!! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: New added property with @QuerySqlField does not persist

Thank you reply very much! May be I don't address the issue clearly. here is my steps: 1: keep the server running 2: alter the schema via sql 3: I can query the new add column 4: add the corresponding attribute in pojo and with tag it with @QuerySqlField. 5: call IgniteCache.put with new version

Re: New added property with @QuerySqlField does not persist

i noticed there is a comment from @slava.koptilin > I think the problem is to support dynamic update of fields in QueryEntity. I am afraid that there is no plan to support that. At least, I didn't find a ticket in JIRA. is there any plan to add this feature? it's obviously with the system

New added property with @QuerySqlField does not persist

My case is very similar with this one http://apache-ignite-users.70518.x6.nabble.com/SQL-cannot-find-data-of-new-class-definition-td22081.html I add the new column(property) via sql as addressed in the

Re: Can't add new key/value pair to existing cache via sql command

Thank you reply very much! If I keep all the caches for my system are created via sql, then all the backend h2 tables are in public schema. in this case even all the caches are in the same schema but there are different cache (one cache per table but all in the same schema) then we can use

Re: Can't add new key/value pair to existing cache via sql command

based on my knowledge about ignite, there is a corresponding database `schema` for each `cache` in ignite (cache name) in real case there are always more than one tables in a database `schema`. that's why I keep more than one tables in a single ignite `cache` if use one table per cache,

Re: Can't add new key/value pair to existing cache via sql command

Thank you very much! can you tell me why there is a such limit that new created table via sql can not be in the non-public schema? I am using ignite with persistent, each `module` in my system is using a cache, which there are some tables generated via `cfg.setIndexedTypes` right now for

Re: How to add a new cache type to a existing cache?

from the command line there is a error messasge Error: CREATE TABLE can only be executed on PUBLIC schema. (state=5,code=0) just want to know is there anyway to add the new type/table to my existing schema? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to add a new cache type to a existing cache?

from the command line there is a error messasge Error: CREATE TABLE can only be executed on PUBLIC schema. (state=5,code=0) just want to know is there anyway to add the new type/table to my existing schema? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How to add a new cache type to a existing cache?

my cache is created via (cache name is 'abc') == igniteSpringBean.getOrCreateCache(cfg) == and the indexedType is [Long.class, Person.class, Long.class, Student.class] keep the server node running, and issue command from `sqlline.sh`

Can't add new key/value pair to existing cache via sql command

my cache is created via (cache name is 'abc')*igniteSpringBean.getOrCreateCache(cfg);*and the indexedType is [Long.class, Person.class]keep the server node running, and issue command via 'sqlline.sh'CREATE TABLE IF NOT EXISTS Person ( id int, city_id int, name varchar, age int, company

JDBC thin: support connection pooling in 2.7?

know that the coming release (2.7) support JDBC: * Implemented DataSource interface for thin driver and there is a jira about the connection pool https://issues.apache.org/jira/browse/IGNITE-6145 it comments as below W have to support connection pool to JDBC compliance. At the very least

ignite 2.7 connection pool support?

Known from mail list ignite 2.7 will support jdbc datasource. and there is a jira about jdbc connection support https://issues.apache.org/jira/browse/IGNITE-6145 it's blocked by https://issues.apache.org/jira/browse/IGNITE-6140 right now https://issues.apache.org/jira/browse/IGNITE-6140

Re: how ignite distribute sql query to all nodes when use REPLICATED mode

I found the document here https://apacheignite-sql.readme.io/docs/select *SELECT queries can be executed against both replicated and partitioned data. When executed against fully replicated data, Ignite will send a query it to a single cluster node and run it over the local data there. On the

how ignite distribute sql query to all nodes when use REPLICATED mode

Suppose right now the cluster has 3 nodes, and all cases are in REPLICATED mode, that means every node has full set of the data. then in this case how ignite distribute the sql query to all nodes to speed up the query? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: close method must be called on IgniteCache?

thank your reply very much! I suppose this method `close` is intended for resource release. by the way, keep the `cache` there would occupy system resource/decrease system performance? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

close method must be called on IgniteCache?

here is the document from source code I just wondering is the `close` method must be called ? for my case, In my kafka consumer, I did some computation and then put the data into ignite. as the message comes in continuous, I just wondering if keep `close` and `open` frequently will decrease the

RE: Can I use limit and offset these two h2 features for pagination

Thank you reply very much! in standalone h2 mode, if want to make `limit` and `offset` work correctly the sql must be take a `order` clause. as I can't find document address how h2 works in ignite cluster.(I just know it works something like map-reduce. so I guess if `limit` ,`offset` and

Can I use limit and offset these two h2 features for pagination

I know in h2 standalone mode, we can use *limit* and *offset* features(functions) for pagination. Not sure in ignite I can still use these two function for same purpose? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteCache.size() for different cache show the same number

public *IgniteCache* comment() { return igniteSpringBean.getOrCreateCache(IgDef.DOCS); } public *IgniteCache *reply() { return igniteSpringBean.getOrCreateCache(IgDef.DOCS); } you can find the caches are totally different(key type and value type) -- Sent

IgniteCache.size() for different cache show the same number

here is my code public IgniteCache comment() { return igniteSpringBean.getOrCreateCache(IgDef.DOCS); } public IgniteCache reply() { return igniteSpringBean.getOrCreateCache(IgDef.DOCS); } I put 10 records to *IgniteCache * but when I call IgniteCache.size()

Re: ***UNCHECKED*** new CacheConfiguration always returns same instance

As I pass different cache name as the parameter, so I suppose the hash code should be different. in my use case i create Spring bean via @Bean with @Scope(value = SCOPE_PROTOTYPE) when I try to verify if a new instance is created or not I found the hash code is the same. that's why I ask

***UNCHECKED*** new CacheConfiguration always returns same instance

here is a simple test code CacheConfiguration cacheCfg = new CacheConfiguration<>(IG_P); cacheCfg.setBackups(1); cacheCfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.PRIMARY_SYNC); logger.info("instance {}", cacheCfg.hashCode()); cacheCfg = new

Re: SQL SELECT with AffinityKeyMapped - no results

I ran into the same issue. if we can not use @AffinityKeyMapped without any workaround. then Can I use AffinityKey as the document address Object personKey1 = new AffinityKey("myPersonId1", "myCompanyId"); Object personKey2 = new AffinityKey("myPersonId2", "myCompanyId"); Person p1 = new

KafkaStreamer and IgniteDataStreamer dynamic cache name

Seems KafkaStreamer and IgniteDataStreamer has one to one mapping. that's to say a KafkaStreamer can only persistent to one cache. right now my case is a bit complicated. KafkaStreamerGenericEntity*> kafkaStreamer = new KafkaStreamer<>(); during persist phrase, I need to save a *GenericEntity*

Re: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to find SQL table for type:

@Test public void happyFlow(){ UserAppInfo userAppInfo = dynamicUserAppInfo(); userAppInfoService.put(userAppInfo); UserAppInfo userAppInfo1 = userAppInfoService.get(userAppInfo.getAppId(), userAppInfo.getUid()); Assert.assertNotNull(userAppInfo1);

class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to find SQL table for type:

I run into above exception when I do a SQLQuery. but it's works well with put/get. I have below dependency 2.3.0 org.apache.ignite ignite-core ${ignite.version} org.apache.ignite ignite-spring

log4j on server node (log no print)

Here is my configuration client node 1: IgniteBean 2: log4j2 dependency on the client node

Re: Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:

Saying cache mode is "PARTITIONED", in this case both primary node and backup nodes would execute the same piece of code, right? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Caused-by-class-org-apache-ignite-binary-BinaryInvalidTypeException-tp4311p4585.html

Re: Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:

Yes, you are right, also need another minor change as well. need to set "peerClassLoadingEnabled" to "true" By the way, what does it mean for below explanation(https://apacheignite.readme.io/v1.5/docs/jcache) > Whenever doing puts and updates in cache, you are usually sending full > state

Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:

I ran into this issue with below code public static void main(String[] args) { ApplicationContext appCtx = new ClassPathXmlApplicationContext(new String[] {"grid-01.xml"}); IgniteSpringBean ignite = (IgniteSpringBean)appCtx.getBean("igniteSpringBean");

Re: Point to point messaging with Ignite

Thank you very much! I am going to use Ignite Queue implement this. but you mentioned that* Ignite Queue + [Distributed Countdown Latch + Atomic Counter] * why need *Distributed Countdown Latch * or* Atomic Counte* here ? As once an entry item from poll from the queue, then other node can

How ignite server node release memory(GC) for IgniteQueue and IgniteSet

Would ignite node release memory for those IgniteQueue and IgniteSet when those queue or set not used any more? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-ignite-server-node-release-memory-GC-for-IgniteQueue-and-IgniteSet-tp2388.html Sent from the