I vote for implementing this enhancement: having key information separated from value means either cluttering domain model with KeyValue/CacheEntry-like structures or developing an Ignite data access layer to insert key info into domain entity after getting it from Ignite.
Although both the options solve the issue, I think the right approach is to address it in Ignite rather than make all the Ignite users repeatedly deal with the issue. It is the Ignite which is a re-usable platform and not vise-versa. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
