Why datastructure are not dataRegion bounded

[dhiman_nikhil]

While going through the below code, i found this issue.
Ignite ignite = Ignition.ignite();
 
// Non-colocated queue which will be distributed
// across all data nodes.
IgniteQueue queue = ignite.queue("queueName", 20, new
CollectionConfiguration());
 
// Add queue elements.
for (int i = 0; i < 20; i++)
queue.add("Value " + Integer.toString(i));
 
// Poll queue elements.
for (int i = 0; i < 20; i++)
System.out.println("Polled value: " + queue.poll());

How to make sure above code is bounded to specific data Region with
persistence on for few data structure and off for few??



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Limited set of DataStructure compared to REDIS

[dhiman_nikhil]

I see many DS not present in Ignite like zrevrangeByScore, sortedSet, etc. 
Is there a way I can get all D.S. provided by Redis in Ignite.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How data region is propagated to other nodes

[dhiman_nikhil]

Can I create data regions on All Servers dynamically?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How data region is propagated to other nodes

[dhiman_nikhil]

Can I create a data region dynamically on every node in the cluster?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How data region is propagated to other nodes

[dhiman_nikhil]

As per documentation, I can do persistence in data region only. If I wanted a
cache key to be persisted then I have to make sure that data region to be
replicated across all nodes. 

Basically, my requirement is to give multi-tenancy support[Multiple
Applications can communicate to Ignite Cluster]. To prevent conflict of
CacheKey, I will be writing an Ignite Client[Wrapper over IgniteClient
library] and passing on the limiting functionality to Services[Like they can
get CacheKey, but not been able to create it]. 

If a new Application comes and demands a CacheKey with persistence ON, we
should be able to provide it without reloading the whole nodes of Ignite
cluster.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How data region is propagated to other nodes

[dhiman_nikhil]

Server level config:
Server: Node 1  
CacheKey: "location"
DataRegion: "location"
persistence: true

Server: Node 2
CacheKey: "category"
DataRegion: "category"
persistence : false

Both belong to same cluster.
Since Data is partitioned across nodes when I start Node 1 and then Node 2,
will "location" region is also created in Node 2 since data will be
partitioned for CacheKey: "location"  ??



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/