Re: Get high throughput for loading data in ignite

I agree with Andrey, you should debug your application first and find out where the bottleneck is. Why do you think it's on system level? I honestly doubt it. -Val -- View this message in context:

Re: Can continuousAsyncQuery guarantee event to be processed in order?

Hi, Async callbacks do not change notification guarantees. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Can-continuousAsyncQuery-guarantee-event-to-be-processed-in-order-tp10521p10534.html Sent from the Apache Ignite Users mailing list archive at

Re: EntryProcessor for cache

Anil, What exactly did you try and what didn't work? Can you show your code? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/EntryProcessor-for-cache-tp10432p10532.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cache write behind optimization

Hi Tolga, There is a back-pressure mechanism to ensure that node doesn't run out of memory because of too long write behind queue. You can try increasing writeBehindFlushSize property to relax it. -Val -- View this message in context:

Re: Question on replication

Hi Rishi, Updates are updated with the whole value. However, in PRIMARY_SYNC mode (default one) it's done asynchronously in background. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Question-on-replication-tp10528p10530.html Sent from the Apache Ignite

Re: spring boot clustered session with ignite

Great! Please refer to this page for details: http://ignite.apache.org/community/contribute.html#contribute -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/spring-boot-clustered-session-with-ignite-tp10455p10511.html Sent from the Apache Ignite Users

Re: Ignite integration with Spring Batch and Spring Integration frameworks

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. clong0214 wrote > hello, it seems to fit me my case when i

Re: spring boot clustered session with ignite

Hi Rishi, We currently don't use voting. In any case, the fastest way to get a future done is to contribute it. Are you interested? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/spring-boot-clustered-session-with-ignite-tp10455p10508.html Sent from the

Re: NOT IN in ignite

Anil, You should always try to colocate as much as possible when working with a distributed system. If you colocate properly and set collocated=true, you will get correct result with the best possible performance. If you can't colocate, you have to set the flag to false. Result will still

Re: pure memory SQL Grid

BTW, schema utility is deprecated. It's better to use web console: http://ignite.apache.org/addons.html#web-console -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/pure-memory-SQL-Grid-tp10464p10494.html Sent from the Apache Ignite Users mailing list

Re: pure memory SQL Grid

Hi Lighfer, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. Lighfer wrote > I hava billions of JSON data

Re: NOT IN in ignite

Not correct :) You can join data from two caches with one connection. Cache you provide in the URL will be treated as a default schema. Other tables can be accessed by providing schema name in from of the table name ("my-cache".MyType). -Val -- View this message in context:

Re: Partition mapping to Ignite node

AffinityFunctionContext is the input, it provides information about topology for which the mapping has to be created. assignPartitions() method then has to return this mapping. Here is the JavaDoc quote for this method: Returns: Unmodifiable list indexed by partition number. Each element of array

Re: EntryProcessor for cache

Anil, I don't think there is such an example in particular. Just implement ComputeTask, access cache(s) in compute jobs and work with local data. Then reduce in reduce() method to get final result. Other particular details depend on your use case. -Val -- View this message in context:

Re: persist only on delete

Shawn, I don't know, sounds wrong. Do you have a unit test reproducing this? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/persist-only-on-delete-tp10438p10489.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: EntryProcessor for cache

Yes, you can create a map reduce task, execute local query within each job (use Query.setLocal(true)), and update queried entries accordingly. Also note that each SQL table in Ignite has predefined _key field that returns key object, so you can return set of keys from the query. -Val -- View

RE: persist only on delete

Hi Shawn, Your approach sounds a bit dangerous. Store is called within an entry lock, which means that if you do a distributed get there, you will likely get thread starvation. This should not happen on stable topology, but if another node fails or joins, you can get stuck. I think you should

Re: insert and update dml issues

Hi, Yes, feel free to create a ticket if there is a bug. Please create a unit test that reproduces the issue and attach it there. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/insert-and-update-dml-issues-tp10456p10460.html Sent from the Apache Ignite

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Yuci, RESTART_JVM policy restarts the whole JVM (surprisingly :) ), so it works only for standalone nodes started with ignite.sh script. In your case you can use NOOP policy, listen to EVT_NODE_SEGMENTED event and restart the node in a listener. -Val -- View this message in context:

Re: NOT IN in ignite

Well, I would agree that the flag is confusing, but your understanding is not correct. When used incorrectly, this flag does breaks query result because it forces Ignite to change execution plan to more optimal. This optimization doesn't always work though (that's actually the reason why it's

Re: does QuerySqlField support data type Collection?

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. howfree wrote > if true, send me some examples or its link,

Re: How create cache on linux system for apache ignite/ gridgain .

Hi Debasis, There is nothing specific for Linux. Check that you provide correct classpath to 'java' command and that your JAR is picked up. -Val -- View this message in context:

Re: equivalent xml configuration with code.

Or you can just provide indexed types: java.lang.String Ignite XML configuration is based on Spring [1], so you can use anything available there. [1] https://docs.spring.io/spring/docs/current/spring-framework-reference/html/beans.html -Val -- View this message

Re: backup to swap

I don't understand this one. Backup copy is exact replication of primary copy. So if primary copy consumes 5GB and you have 1 backup, it will be 10GB in total. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/backup-to-swap-tp10255p10424.html Sent from the

Re: 2nd level cache with eclipselink

No, no plans. Feel free to create a feature request ticket in Jira. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/2nd-level-cache-with-eclipselink-tp10385p10423.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: count from subquery is wrong

I think optimization is possible only if you don't have any conditions (i.e. query like 'select count(*) from Table'). Ignite doesn't optimize this case though. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/count-from-subquery-is-wrong-tp10344p10407.html

Re: How we can get metrics through JMX?

MBeans are created automatically by default. Just connect to MBean server with any JMX client (e.g. VisualVm) to view them. Default port is 49112 (the actual value is printed out in the startup log). -Val -- View this message in context:

Re: Thread pool for partition aware operations

Anything executed on IgniteCompute API is executed in public pool (size is configured via IgniteConfiguration.publicThreadPoolSize property), while all cache operations including entry processor are executed in system pool (IgniteConfiguration.publicSystemPoolSize property). Sizes for both pools

Re: 2nd level cache with eclipselink

I don't think there is an implementation for Eclipselink. Ignite provides L2 cache for Hibernate and also there is an implementation for MyBatis. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/2nd-level-cache-with-eclipselink-tp10385p10402.html Sent from

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Hi Yuci, We do not allow reconnection of server nodes because it's dangerous for data consistency. Segmented node must rejoin topology as a new one. There is RESTART_JVM policy which restarts node immediately. -Val -- View this message in context:

Re: Read heavy small cache in all clients and servers

Then partitioned cache would be a better choice. Also it sounds like continuous queries can be useful to notify other clients about updates: https://apacheignite.readme.io/docs/continuous-queries -Val -- View this message in context:

Re: Deploying cache on selected server nodes within cluster

You don't need custom affinity function for this. Nodes where a particular cache is deployed is defined by filter provided via CacheConfiguration.nodeFilter property. I would recommend to use user node attributes to assign nodes to different logical groups, and implement a filter that will filter

Re: backup to swap

Yep, sounds correct. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/backup-to-swap-tp10255p10398.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Custom AffinityFunction

Yes, if collocated types are stored in different caches, these caches must have the same affinity function. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Custom-AffinityFunction-tp10167p10396.html Sent from the Apache Ignite Users mailing list archive at

Re: Configure number of partitons

Number of partitions is configured as a part of affinity function: -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Configure-number-of-partitons-tp10392p10395.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Write behind - coalesces updates on a specific key

Yes, that's exactly what I meant. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Write-behind-coalesces-updates-on-a-specific-key-tp10368p10378.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Write behind - coalesces updates on a specific key

Write behind store rewrites consequent updates, I don't think there is a way to override this behavior, except implementing your own implementation of CacheStore that would do write-behind logic. -Val -- View this message in context:

Re: Read heavy small cache in all clients and servers

It sounds like you simply need a cache replicated across all client applications, and actually no need for standalone server nodes. If that's the case, start an embedded node using Ignition.start() in each application, and configure a cache with cache mode set to REPLICATED. -Val -- View this

Re: Ignite as a shared file sysytem

Rishi, Secondary file system acts as a persistent storage for in-memory FS. It sounds like you're looking for simple shared network file server. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-as-a-shared-file-sysytem-tp10361p10367.html Sent from

Re: simple file based persistent store support TTL

Hi Shawn, Built in expiration is cache expiration, which by definition doesn't touch database. This means that you need to manually use remove() operation to delete from both cache and store. I think approach #1 is the best way to approach this. -Val -- View this message in context:

Re: Get distributed query data from Ignite local caches in cluster

Hi, That sounds like a very weird use case. Why don't you use partitioned cache? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Get-distributed-query-data-from-Ignite-local-caches-in-cluster-tp10310p10317.html Sent from the Apache Ignite Users mailing

Re: Fetch by contains on a field as Array or List

Sam, Collections can't be indexed in Ignite. You can easily implement CONTAINS function as you described, but as I mentioned, using it will trigger full scan. Another option you have is to implement IndexingSpi and use SpiQuery to execute queries. But this will imply implementing indexing and

Re: Fetch by contains on a field as Array or List

Hi Sam, To do the search you can create a custom function that will do the job [1]. But note that this search will not be indexed. To create an index you need to store each element of collection as a separate cache entry.

Re: IGFS Questions

pragmaticbigdata wrote > I will spend sometime in understanding what this means but by "Hadoop > compliant implementation" are you hinting that HDFS needs to be running > even if I have S3 as the secondary file system? It's any FS that has a connector that implements

Re: Text query

Got it. I believe there is no mechanism to inject custom analyzer. I'm not a big Lucene expert, do you have an example of how this can be done? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Text-query-tp8661p10296.html Sent from the Apache Ignite Users

Re: eagerTtl

Surprisingly, the name of the thread is 'ttl-cleanup-worker' :) It's started only if there is at least one cache using it. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/eagerTtl-tp10249p10275.html Sent from the Apache Ignite Users mailing list archive at

Re: Newbie: Questions on Ignite over cassandra

I meant that Cassandra itself will be involved only when you load the data into caches, which is a separate step that should happen prior to query execution. When Ignite query is executed, Cassandra is not touched. The answer on your question is yes - any joins are possible, similar to any

Re: Apache Ignite 1.7.0 Session caching issue with update session attributes

Binary marshaller is default internal format, there is no need to set it explicitly in configuration. If you remove the 'marshaller' property from configuration, it will be used. If it doesn't work this way as well, please attach configuration and the exception trace. -Val -- View this

Re: Newbie: Questions on Ignite over cassandra

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. Jenny B. wrote > I am exploring Apache Ignite on top of

Re: How to get On heap memory usage for a map?

What do you mean by usage? Which metrics are you looking for exactly? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-get-On-heap-memory-usage-for-a-map-tp10263p10267.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: backup to swap

Hi Anil, Take a look at this discussion: http://stackoverflow.com/questions/40403598/can-you-evict-ignite-cache-backups-to-disk -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/backup-to-swap-tp10255p10266.html Sent from the Apache Ignite Users mailing

Re: Getting previous value in cache immediately after performing an unlock

Hi, Your test is incorrect. This lines are not synchronized and can be reordered with each other and with the validation that happens in another thread: simpleCacheValidationWithLock.setIndex(i - 1); simpleCacheValidationWithLock.setValueToValidate(valueCounter); After I moved them into the

Re: Cache stopped

Anil, Take a look at lifecycle beans: https://apacheignite.readme.io/docs/ignite-life-cycle -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-stopped-tp9503p10253.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Text query

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. avpdiver wrote > Is there possibility to use my custom

Re: eagerTtl

Hi Sam, According to code, there is actually a thread per node not per cache. Do you observe different behavior? Also I didn't find anything about "thread per cache" in JavaDoc. Can you please show where you read this? -Val -- View this message in context:

Re: Kafka as a Persistent Store

You can implement the CacheStore interface to provide integration with any kind of storage: https://apacheignite.readme.io/docs/persistent-store There is no Kafka based implementation out of the box. -Val -- View this message in context:

Re: Connection problems

Lukas, Check that nodes can connect to each other (i.e. there are no network issues, no firewall or ports are opened, etc.). Another possible reason is GC - make sure that you have enough heap memory. -Val -- View this message in context:

Re: OFFHEAP_TIERED and memory fragmentation

Random means anywhere in empty memory space. When you create an entry, a new block is create for this value only. If you remove an entry, memory is released. Once removed, it can be used by any application including Ignite. Basically, the actual location where memory is allocated is defined by OS.

Re: 答复: ignite client memory issue

Shawn, It looks like you had too many asynchronous operations executed at the same time and therefore too many futures created in memory. Async approach requires more accuracy, and if everything works for you with sync operations, I would use them. -Val -- View this message in context:

Re: Running Spark app in cluster!

I would suggest to create IgniteConfiguration programmatically (use IgniteContext constructor that accepts closure instead of XML file path). However, it looks like there is a room to improve, I created a ticket: https://issues.apache.org/jira/browse/IGNITE-4593 -Val -- View this message in

Re: REST service command LOG

Sam, That's actually interesting :) I believe this command behaves this way because the purpose of the command is to fetch the Ignite log, not any arbitrary file. On the other hand, logic in GridLogCommandHandler looks weird and limited. Do you have any ideas about how it SHOULD work? My current

Re: Data Rebalancing & Transactions

Yakov, Makes sense. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-Rebalancing-Transactions-tp10092p10142.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Data Rebalancing & Transactions

Sam, NONE mode is something that should be used very accurately. It means what it means - no rebalancing is happening when topology is changing, unless you trigger the rebalancing manually. For example, if you have a cache with one backup and you lose one of the nodes, you end up having only one

Re: Ignite REST with JBOSS

Hi Sam, Ignite starts its own HTTP server for rest API, so it's definitely possible when running in JBoss as well as anywhere else. You just need to add ignite-rest-http module with dependencies to classpath and the endpoint will start automatically. If you're using Maven, add this to pom.xml:

Re: Index Maintenance During Transactions

I think Dmitry meant that indexes are updated synchronously with transaction commit. However, note that SQL queries are currently not transactional, so you can still get dirty reads in the result set. -Val -- View this message in context:

Re: Ignite in Docker

Hi Jim, Please show you AddressResolver implementation, your configuration and describe the deployment in more details (how many nodes, how addresses are assigned to them, etc). -Val -- View this message in context:

Re: Consistency Guarantees & Smart Updates with Spark Integration

Hi, 1.a. I think this depends on Spark and how it handles failover in such cases. Basically, loading data to Ignite from Spark RDD is a simple iteration through all partitions in this RDD. 1.b. You will not lose any data if you have at least one backup. 2. Can you clarify this?

Re: Running Spark app in cluster!

Hi, Can you show how you create the IgniteContext? Are you using XML or creating IgniteConfiguration in code? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Running-Spark-app-in-cluster-tp10073p10103.html Sent from the Apache Ignite Users mailing list

Re: Merging with RDBMS transaction

Hi, 1. This is correct. 2. In transactional cache a new session is created per transaction. Connection for a session is acquired from provided data source. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Merging-with-RDBMS-transaction-tp10093p10102.html

Re: Running Spark app in cluster!

Hi, Can you provide more details? How deployment looks like, what you're doing, what is result and why it's not what you expect, etc... -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Running-Spark-app-in-cluster-tp10073p10078.html Sent from the Apache

Re: How to remove large amount of data from cache

Can you try to upgrade to 1.8 and check how 'delete from ...' query performs in your case? From what I hear, this is the most appropriate solution. -Val -- View this message in context:

Re: Streaming Sliding Window question

Sounds like you can simply store all 5 latest entries as a single entry and update the collection atomically using entry processor and invoke() method (check current size within entry processor and remove oldest element if needed). Once updated, you can do the computation. Will this work for you?

Re: Re-partitioning when partition key changes

Hi, What is 'partition key' and how is it used? Can you give an example for this use case? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Re-partitioning-when-partition-key-changes-tp10031p10039.html Sent from the Apache Ignite Users mailing list archive

RE: Questions on Client Reconnect and Client Cache

Mani, 1. Specific timeout value depends on you environment network speed, etc. Basically, client will automatically reconnect to server when the latter is restarted, but it will fail to do that if timeout expires. 2. Local cache must work, I would assume you're doing something. Please prepare a

Re: Behavior of ScanQuery while updating

Hi, Scan query doesn't lock anything. It behaves like any concurrent map - if concurrent update happened on an entry that is not visited by the iterator yet, you will then get new value. What kind of locking are you looking for? It sounds like you want to block the whole cache, which is

Re: Faceted search

Mikhail, >From what I here, you can simply use SQL for this task. Is there something in particular that doesn't work for you? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Faceted-search-tp10034p10035.html Sent from the Apache Ignite Users mailing list

Re: 答复: 答复: compute SQL returned data.

Shawn, map() method is execute locally on the master node, so you can do all the checks outside the task and then execute only if needed. Will this work? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/compute-SQL-returned-data-tp9890p10016.html Sent from

Re: Affinity

Hi Tejas, I don't see anything obvious in the plan. Note that when you join, you still have to scan one of the sides, so if intermediate datasets after applying conditions are still large, performance can be not very good. Joins are applied in the order they appear in the plan, so you can go

Re: Java Service Deployment

Hi, What timestamps are you referring to? If you want to measure the latency of a particular call, surround it with timestamps and print out the duration. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Java-Service-Deployment-tp9933p10011.html Sent from

Re: AW: Rediscovery after Startup

Lukas, New node connects to the one that is already running, not other way around. Actually, for node to start it must be able to connect to one of the addresses in the IP finder, OR be able to bind to one of these addresses. So the fact that your node started means that its own address was

Re: Rediscovery after Startup

Lukas, According to the log, this node is the first one in the topology and it is successfully started, this is correct behavior. Can you clarify what is wrong? BTW, you see all these errors only because you have DEBUG logging enabled. -Val -- View this message in context:

Re: Unable to start 2 server nodes on same machine

Can you attach your configuration? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unable-to-start-2-server-nodes-on-same-machine-tp9987p1.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: 答复: compute SQL returned data.

Hi Shawn, This means what it says - ComputeTask.map() method returned no jobs, i.e. null or empty map. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/compute-SQL-returned-data-tp9890p.html Sent from the Apache Ignite Users mailing list archive at

Re: Simple Compute API for SQL returned data.

I would recommend to create a ticket with design proposal and share it on dev list. You will get much better feedback there. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Simple-Compute-API-for-SQL-returned-data-tp9962p9980.html Sent from the Apache

Re: Size of an Object

You can serialize the object and check the length of the byte array: byte[] arr = ignite.configuration().getMarshaller().marshal(new Person(10L, "first", "last")); System.out.println(arr.length); Then refer to this page to calculate the total cache capacit:

Re: Affinity

Hi Tejas, Did you check the execution plan? Are there any scans? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-tp9744p9943.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: NOT IN in ignite

Hi, The aggregation should happen on the client and you should get the correct result. Are nodes discovering each other? Can you prepare a test case that reproduces the issue? -Val -- View this message in context:

Re: Spring Boot Ignite Application - Autowire Services in IgniteCallable

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. hitendrapratap wrote > I have Spring Boot Ignite Application

Re: Spring Boot Ignite Application - Autowire Services in IgniteCallable

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. -- View this message in context:

Re: Put Vs Datastreamer

Hi Gaurav, How many nodes do you have? I think your results only possible with local deployment when there is only one server node. When network is added into the picture, streamer batching should provide big improvement. If this is not the case, please provide a test case that we can run to

Re: Cluster hung after a node killed

Sam, There is no exact date as for now. I would recommend to monitor the dev list for activity around this. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9883.html Sent from the Apache Ignite Users mailing list

Re: Affinity

The thread continues here: http://apache-ignite-users.70518.x6.nabble.com/Affinity-td9744i20.html -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-tp9744p9882.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Near cache can be used with SQL Database

The answer is here: http://apache-ignite-users.70518.x6.nabble.com/NearCache-can-be-used-through-ODBC-interface-td9859.html -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Near-cache-can-be-used-with-SQL-Database-tp9805p9881.html Sent from the Apache

Re: LoadCache Performance decreases with the size of the cache

I would recommend to use one of the non-empty constructors for QueryIndex, they all set SORTED as default. Frankly, I would remove the one that is without parameters, it doesn't make much sense and error-prone. -Val -- View this message in context:

Re: JCache and CacheManager.getCache

It is supported if you provide key and value classes in CacheConfiguration, but this is possible only in code, not in XML. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/JCache-and-CacheManager-getCache-tp9847p9853.html Sent from the Apache Ignite Users

Re: JCache and CacheManager.getCache

You don't need to provide types to get a cache. Just do this: Cache cache = cacheManager.getCache("myCache"); -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/JCache-and-CacheManager-getCache-tp9847p9851.html Sent from the Apache Ignite

Re: Old AWS SDK version, why?

This is just a version ignite-aws module was developed on, and I don't think newer versions were ever tested. However, I believe it should work with 1.11.76. Can you try it out and let us know if it does? -Val -- View this message in context:

Re: Ignite cluster

Tejas, You can send a closure to server node and iterate through local data using IgniteCache.localEntries() method. This should give you a clear picture. BTW, is this the correct thread? Looks like you posted in a wrong one by mistake. -Val -- View this message in context:

Re: Streaming Exception on client - nothing on server side

Hi, Can you create a unit test that will reproduce the issue and share it with us? It's hard to tell anything having only this trace. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-Exception-on-client-nothing-on-server-side-tp9807p9808.html

Re: Near cache can be used with SQL Database

Hi, Can you please clarify the question? What are you trying to achieve? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Near-cache-can-be-used-with-SQL-Database-tp9805p9806.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

<    2   3   4   5   6   7   8   9   10   11   >