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

hi, When I use Ignite create table DDL，can I set the db schema instead of the schema name "PUBLIC"？ -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Using a cache as an affinity co-located processing buffer in Ignite.Net

Not being able to do an initial scan of elements on the remote nodes is a bit of a problem (possibly a bug?) Something that’s occurred to me is to wrap this behaviour into an Ignite service deployed onto all of the server nodes, and use a local mode continuous query from within each service to

Re: Slow invoke call

Sorry, I do not have trace for scan query. We moved away from the earlier implementation, as of now it is not showing big latencies like earlier. Thank you for help. Thanks, -Sam -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Using a cache as an affinity co-located processing buffer in Ignite.Net

> Is the initial query also run in the context of the remote node and the remote filter? No, it is just a query (can be SQL or Scan) which allows you to get a "full picture" on the calling node: all existing data and all future data. So in your scenario it is not very useful. > return false

Re: Inconsistency reading cache from code and via REST?

Also I will check why it's not working in next case: CacheConfiguration cfg = new CacheConfiguration<>(); cfg.setIndexedTypes(String.class, String.class); cfg.setName(CACHE_NAME); IgniteCache cache =

Re: Setting Ignite System Properties

Hello! Either pass them as JVM args in the form of -DIGNITE_system_property=value or set them with System.setProperty("IGNITE_system_property", "value"); Regards, -- Ilya Kasnacheev 2018-04-23 19:30 GMT+03:00 kotamrajuyashasvi : > Hi > > I would like to know

Re: Inconsistency reading cache from code and via REST?

Hi Michael, You are trying to work with sql queries. Let me provide to you the example how you can do it: 1) Start ingnite server node 2) Start ignite client node that will create the cache and put some values: StartNode.java

Setting Ignite System Properties

Hi I would like to know how/where to set the Ignite System Properties before starting Ignite Cluster. https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteSystemProperties.html -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Inconsistency reading cache from code and via REST?

Following on from his example of a simple cache with key value pairs (now strings! IgniteCache), how would I create a sql query on the data: http://127.0.0.1:8080/ignite?cmd=qryexe=GridCacheTest=1=String=_key+%3D+1 gives: {"successStatus":1,"error":"class

Re: Failed to wait for partition map exchange

Hi ​Deepesh​, This kind of message says that some of node(s) cannot process exchange message and usually it happens when some server node crashes or some exception happens on the node. I'd better check full logs from all server nodes for the stacktrace from the beginning. Pay attention to the

Re: Using a cache as an affinity co-located processing buffer in Ignite.Net

Remote Listener is deployed on every cache node and is invoked only on a primary node for that key. In other words, for each key there is only one invocation of the remote filter, and that invocation is local to that key. So you can place your processing logic into the Remote Filter. On Mon, Apr

RE: Using a cache as an affinity co-located processing buffer in Ignite.Net

Hi Pavel, Yes, I looked at continuous queries. They appear to be oriented toward a single context being sent the newly arrived elements in the cache from all primary nodes hosting the cache involved in the query. In the use case I outlined below, I would like to have the items processed in

Re: Using a cache as an affinity co-located processing buffer in Ignite.Net

Hi Raymond, To process incoming data in a co-located fashion there is a Continuous Query feature [1]. Looks like it fits your use case quite well. [1] https://apacheignite-net.readme.io/docs/continuous-queries On Mon, Apr 23, 2018 at 7:32 AM, Raymond Wilson wrote:

Re: Failed to wait for partition map exchange

This is the complete log that is being printed in all nodes repeatedly. Regards, Deepesh On Sun, Apr 22, 2018 at 12:00 PM, begineer wrote: > Could you please paste complete log. This log is not enough. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite cache query

Thanks for your reply. Forgot to mention earlier that I am already using @QuerySqlField on each field of my Pojo class so all the fields are appearing as table columns but the hashmap doesn't. So how do i use @QuerySqlField on a hashmap so that each key of hashmap also behaves as a table