Hello, Unique constraints are not yet implemented in Ignite and I would assume they won't be generally available soon enough.
The reasoning behind that is in general each put/insert is a distributed insert/put. There are some circumstances under which this operation might happen to be local: if cache is replicated or the constrained field is an affinity key for a cache. Otherwise it is a cluster-wide constraint check operation for each put/insert and might dramatically affect the overall performance depending on cache size and cluster size which means that the scalability is affected too. Unique field might just be a part of primary key. Best regards, Anton -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
